Zenergy Blog

Zenergy Expert Shaun Bradshaw Presents at STPCon Spring 2017

Sometimes testers fail to see the importance of their role within software development projects. Although the tester’s main goal is to identify bugs within software and report them back to developers, locating bugs ultimately carries the same weight, in the process, as the way in which they are reported. Failing to report bugs quickly enough or reporting them improperly can lead to distrust between testers and developers as well as delays in releases and increases in revenue.

Free Webinar: Should you Combine Functional and Performance Testing?

Want to complete your performance testing, test automation, and manual testing efforts in a shorter testing cycle? The traditional process splits up each distinct type of testing to occur individually with unique sets of goals and usually occurs with minimal cross-team collaboration. Because these varied types of testing have their own methods and techniques, the process can be timely and conceal problem areas until the end.

The Agile Project Manager - Please Sir, May I Have Some Help?

A seasoned director of software development was championing agile adoption at her company; it was a moderately scaled initiative, including around 100 developers, testers, project managers, BAs and the functional management surrounding them. They received some initial agile training, seemed to be energized and aligned with the methods, and were set loose to start sprinting. Six months later things were in shambles. Managers were micromanaging the sprints and adjusting team estimates...

The Agile Project Manager - Fail NOW as a Strategy

Coaching to Avoid Failure Agile Exposure The Notion of ‘Failing Forward’ Wrapping Up – But, I’m a Bit Strange… I was at a conference not long ago speaking on and sharing variousagiletopics. After one of my presentations, a young man stopped me to ask a few questions. We struck up a nice conversation that eventually discussing sprint dynamics within Scrum teams. I mentioned that I usually coach teams toward declaring their sprints a success…or (pause for meaningful effect) …a failure.

Refactoring and Technical Debt: It's Not a Choice, It's a Responsibility

A few years back I was coaching a large group of Scrum teams at an email marketing SaaS firm. The group had been practicing Scrum for over four years and had become a high-performance agile organization. Most of my efforts focused on fine-tuning from the perspective of an external set of eyes. Working with this organization and its development teams was a privilege. Refactoring vs. Technical Debt Broad vs. Narrow Consideration Stop Digging the Hole and Deeper Fill in the Hole Broadly...