Velocity by Work Type Chart

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.

種類 棒グラフエンジン echarts-bar更新日 2026/9/24

依頼内容

“Create a stacked velocity chart for Sprints 31 to 36 with completed product-story, defect, and technical-debt points of 18/4/3, 16/5/4, 14/7/3, 17/4/5, 15/6/4, and 16/5/3.”

次はこちらAdd an operations work category.Change Sprint 33 defects to five points.

この図に含まれるもの

図の背後にある意思決定を読み解く。

01Total

Keep the stack tied to completed points.

02Categories

Separate product work from defects and debt.

03Interpretation

Investigate shifts in mix before changing commitments.

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

棒グラフのテンプレートをすべて見る →

よくある質問

Why stack velocity by work type?

It shows how the completed total is composed, which can reveal changes in capacity allocation.

Should every task have a category?

Yes, if work-type totals are used. Define a small set of mutually understood categories first.

Is technical debt separate from defects?

Usually. Technical debt is improvement work on maintainability, while defects are problems in existing behavior.