“Create a stacked bar graph for Orbit team sprint capacity in Sprints 21 to 24, stacking features at 26, 24, 30 and 22 story points, bugs at 8, 10, 7 and 9, and platform work at 6, 8, 5 and 10.”
Read the decisions behind it.
Stack work types to see committed capacity.
Keep bugs and platform work visible.
Review changes across sprints.
Use when category totals and their composition both matter.
Other examples in this family.
Common questions
What does each stacked segment represent?
It represents the contribution of one work type to the sprint's total planned capacity.
Why stack instead of group bars?
Stacking makes the total capacity and its mix visible in one bar.
Can story points be compared across teams?
Usually not directly; they are relative estimates calibrated within a team.