Software sprint capacity stacked bar graph
This stacked bar graph shows how Orbit team's planned story-point capacity is divided across features, bugs and platform work in four sprints. The full height of each bar is the total commitment, while the segments reveal what type of work consumes it. That makes it easier to spot a sprint that appears full but is dominated by maintenance, or a sprint with too little capacity reserved for reliability work. Story points are team-specific estimates, so compare them across this stable team rather than treating them as hours. Use the graph during planning and retrospectives to make trade-offs visible. It gives teams a concrete starting point for reviewing assumptions, data quality and next steps together.
Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.
Scenario
A software team balances planned sprint work.
Key decisions
- Show totals: Stack work types to see committed capacity.
- Protect maintenance: Keep bugs and platform work visible.
- Compare periods: Review changes across sprints.
When to reuse this
Use when category totals and their composition both matter.
Frequently asked questions
What does each stacked segment represent?
Why stack instead of group bars?
Can story points be compared across teams?
More project-management examples
Try the diagram makers.
Tweak it with chat, export PNG/SVG, or fork it for your own use case.