What is throughput and how does it differ from velocity?
Tests whether you know throughput is count-based and velocity estimate-based. Define throughput as items finished per sprint regardless of size, contrast velocity's point sum, pick throughput for forecasting and keep velocity for calibration.
Tests whether you distinguish estimate-based capacity from count-based delivery and when each reduces risk. A strong answer defines throughput as items completed per unit of time without story points, notes velocity sums estimated points and invites sizing debates, and explains throughput pairs with cycle-time percentiles for probabilistic forecasts while velocity suits short-term capacity calibration. Red flag: treating throughput as velocity with points removed, missing that throughput ignores estimation and enables cross-team comparison.
Read the original → kollabe.com
- #agile
- #scrum
- #flow-metrics
- #velocity
- #throughput
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.