Showing 8 Result(s)

The Productivity Paradox: Why Adding More Developers Slows Down Your Delivery

Despite expanding an engineering team and investing in advanced tools, delivery timelines worsened due to a misleading focus on individual productivity over system productivity. Increasing developer numbers led to communication overhead, dependency conflicts, and context switching. Shifting to flow-centric metrics improved collaboration and sustainable productivity, enabling faster, higher-quality delivery.

Two software engineers looking at graph

Velocity: How to interpret it to improve your agile team productivity. 1 of 3: Flavours of Velocity

Velocity is a commonly used metric in agile teams. It is a great metric due to its apparent simplicity. However, I often see teams drawing the wrong conclusions for the metric, which results in decreased productivity. 
This post is the beginning of a three-part series to convey my understanding of how to make sense of the information that velocity, as a metric, can provide to an agile team. And use this information to improve the team’s productivity.