Leave a comment

Noting Special Events in Retrospectives, to Capture Sources of Technical Debt

By Paul Cooper, Senior Performance Test Engineer

A fundamental expectation for a high performing Agile team is to have clear requirements to begin building the product(s) with sprints and validating demos. The Agile approach supports the philosophy and the reality as long as the integrity of the requirements remain clear and well thought through. What happens when requirements run amok? Continue reading


Leave a comment

Increasing Velocity of Agile Teams

by Benjamin Frech, Senior Software Engineer

Ben-FrechIncreasing a team’s productivity is a ubiquitous goal. But, how do you achieve that goal?

To many, it may be tempting to use velocity as a measure of productivity, but the value of a story point can vary significantly over time. Once you get past counterproductive answers like, “let’s inflate all our story points by 50%,” you’re left with options that can actually increase your team’s productivity or, at least, facilitate collaboration between team members.

In my experience, the top two methods of truly increasing productivity involve creating a comfortable work environment, and addressing technical debt and developer concerns. Continue reading