If you’ve ever heard “Our velocity dropped” and “Our throughput is up” in the same meeting — you’re not alone. These two metrics often get mixed together, compared incorrectly, or used in ways that create bad incentives.
Some teams “do Kanban” by moving sticky notes across columns. Other teams use Kanban to deliver faster, reduce chaos, and make work predictable.
The difference is maturity — not the tool.
A bottleneck is the one point in a process that limits the speed of everything else.
When work piles up in front of a single step, deadlines slip, stress rises, and teams start “working harder” without actually getting more done.
If you’ve ever heard someone say “We do Agile, so we use Kanban,” you’re not alone.
Kanban and Agile are closely related—but they’re not the same thing. One is a specific method. The other is a broader mindset and family of approaches.
Estimation is one of the most argued-about topics in Agile — and for good reason.
If you estimate in hours, you risk turning planning into time tracking and micromanagement. If you estimate in story points, you risk confusion, inconsistency, and “points inflation” if the team doesn’t understand what points are actually for.
So which one should you use?
Be the first to know about our biggest and best sales. We'll never send more than one email a month.
