AGILE

Velocity by Work Type

A stacked velocity chart adds work mix to the usual completed-points trend. Here, each sprint total is divided into product stories, defects, and technical debt. That breakdown can reveal a change that a single total would hide: for example, the team may complete the same number of points while spending more capacity on defects. Use the categories consistently and keep them simple enough that an item belongs in one place. This is a discussion aid, not a productivity score. A higher defect share may reflect a release period, a reporting change, or necessary quality work. Review the context with the team before drawing conclusions from the bars.

UPDATED 2026-09-25
TYPEBar
EXAMPLEVelocity by Work Type
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

Reviewing sprint work mix

Key decisions

  • Total: Keep the stack tied to completed points.
  • Categories: Separate product work from defects and debt.
  • Interpretation: Investigate shifts in mix before changing commitments.

When to reuse this

Use this chart in a retrospective when the composition of completed work matters as much as the total.

FAQ

Frequently asked questions

Why stack velocity by work type?01
It shows how the completed total is composed, which can reveal changes in capacity allocation.
Should every task have a category?02
Yes, if work-type totals are used. Define a small set of mutually understood categories first.
Is technical debt separate from defects?03
Usually. Technical debt is improvement work on maintainability, while defects are problems in existing behavior.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.