Tag: velocity

Steve Garnett from Ripple Rock (an IT consulting company that assists customers in improving their software development capabilities) is one of many who has experienced Technical Debt on a project he worked on in the past. His new blog post captures a common problem: you know the Technical Debt is there, you know that it’s going to be difficult to fix… so how do you convince management that you need the time and resources to deal with it?
Prioritizing Your Technical Debt
This interview will focus on the ground-level steps that should be taken in order to help IT teams deal with their Technical Debt in a pragmatic and efficient way, while working in a fast-paced Agile environment.
Pragmatic Ways for Your IT Team to Deal with Technical Debt

One of the oldest conversations on record is the discussion of how to measure effective software development. One of the most used, most abused and least understood metric is “velocity.” Think Corvettes versus Volkswagens.

Just to keep terms straight, velocity is the sum of the estimates of delivered/accepted features per iteration. Velocity can be measured in the same units as feature estimates, whether this is story points, days, ideal days or hours.

The Speed of Diligence