Software Sprint Capacity Stacked Bar Graph

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.

Tipo Gráfico de barrasMecanismo echarts-barAtualizado 24/09/2026

A solicitação

“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.”

Depois, tenteAdd a fourth stack for discovery work.Change Sprint 24 feature capacity to 26 story points.

O que há neste desenho

Entenda as decisões por trás dele.

01Show totals

Stack work types to see committed capacity.

02Protect maintenance

Keep bugs and platform work visible.

03Compare periods

Review changes across sprints.

Use when category totals and their composition both matter.

Ver todos os modelos de gráfico de barras →

Perguntas frequentes

Dúvidas comuns

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.