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.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
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.
Frequently asked questions
Why stack velocity by work type?
Should every task have a category?
Is technical debt separate from defects?
Tweak it with chat, export PNG/SVG, or fork it for your own use case.