<ul><li>Stakeholders focusing on perfecting the velocity is enough to make everyone in the engineering team question the validity of the story points.</li><li>Many teams are getting away from velocity and counting the throughput by reporting on sprint throughput.</li><li>The immediate challenge measuring throughput requires the team to split up the work into similar smaller chunks.</li><li>Working in a Work Based Stream creates a problem whereby the team’s goals during the sprint change from delivering outcomes to focusing on completing a number of backlog items instead.</li><li>It is not advisable to mention the team’s internal metrics that don't represent progress externally in a correct way.</li><li>Neither Velocity nor Throughput is a better alternative to each other; they are both just different ways to track the volume of work the team was able to get done in a given time period.</li><li>A different concept of measuring software development progress, referred to as the GPS of software delivery.</li></ul>

Velocity and Throughput are full of Sh*t!

Discover more