Cube Long Arrow Right External Link angle-right Search Times Spinner angle-left

Agile Charts

Work Burn down

Tracks: Estimated number of hours (effort) remaining to complete the goal.

burndown.png

The work burndown chart provides you with the following information:

  • Actual Completed (solid line) — The number of estimated hours remaining until the due date. These values are calculated as all issues "Estimated hours" x "Done ration" present in that day. Chart use issue journals to track changes by dates and can't be changed behindhand.
  • Total Completed (dashed line) - The number of total estimated hours remaining until the due date ignores issue create and start date. This line used for creating Ideal burndown line to calculate correct burndown velocity.
  • Ideal (grey dashed line) — The ideal burndown. This is computed with the remaining estimates units at the version's start date. Hence, this calculation makes the guideline slope more accurate and precise. Ideal burndown based on Total cumulative hours burndown.

Issues Burn down

Tracks: Estimated number of open issues (effort) remaining to complete the goal. It shows how quickly the team is burning through user stories.

issues_burndown.png

The issues burndown chart provides you with the following information:

  • Actual Completed (dark solid line) — The number of issues remaining until the due date.
  • Total Completed (light dashed line) - The number of total issues remaining until the due date. It sums all the user stories per sprint.
  • Ideal (grey dashed line) — The ideal burndown - works as a guide for a team. It means the team is not over-committing and finished the spring backlog on time. Also it indicates no problems with capacity estimation. Such burndown is computed by calculating the exact amount of effort remaining which team need to burndown.

Cumulative flow

Tracks: Efficiency through stages in the delivery process

cumulative_flow.png

Cumulative flow chart shows how many issues are currently in each of the statuses. Probably the most important is the In progress part. If it increases or widens vertically with time, it means that there are some problems or bottlenecks along the way. This indicates delays of the project. A large increase in resolved stories may also indicate a bottleneck on testing or acceptance stage.

Tracker Cumulative flow

trackers_cumulative_flow.png

Tracker Cumulative flow chart shows how many issues there are over time in different trackers: tasks, user stories, bugs and features. It takes into consideration also closed issues.

Velocity

Velocity chart shows how many issues were created and closed over time.

velocity.png

It provides you with the following information:

  • Closed - The number of issues closed.
  • Created - The number of issues created.

Lead time

Tracks: How long an issues cycle takes from creating to closing in days. The charts shows closed issues over time, and if there are several closed issues on certain day - average lead time. Lead time for each issue is displayed only if the issue has been closed.

lean_time.png

Issues burnup

Tracks: progress towards a project completion.

created_closed.png

It provides you with the following information:

  • Closed - The number of issues closed.
  • Created - The number of issues created.
  • Ideal - Ideal burnup, works as a guideline for the team.

The project will be completed when the lines meet. This is a very powerful tool helping to understand how close the team is to the completion of the project, and similarly to burndown charts, it can also notify about any bottlenecks, e.g. when there are too many new issues comparing to issues closed.