Open topic with navigation

Analyzing Sprint Burn Down

Let us look at a simple scenario to understand how you can use the Work Item Burn Down iCube to analyze your sprint progress.

Jim is a Scrum Master who oversees how work items are being handled in every sprint. He may have multiple teams working on multiple projects to monitor.

As a Scrum Master, he wants to understand how teams are progressing in any given sprint. It is critical for him to know how many items were part of the initial scope, if and how many work items were added half-way through the sprint, if the teams are making expected progress in addressing the work items, and so on. Using this data, he charts a burn down graph at the end of every sprint which will help him analyze important project data such as:

• Work Items pulled in the initial sprint scope versus work items that were actually covered (initial scope vs actual cover)
• Scope changes mid-way through the sprint
• If the teams do complete work periodically
• Likelihood of work items identified as part of the current sprint being addressed
• Overall project-wise analysis of sprints

Generating the report

To analyze the sprint burn down, Jim has to login to Digital.ai Intelligence Applications and perform the following tasks in the Work Item Burn Down iCube of Create Lens:

1. From the GALLERY panel, select the desired visualization type here.
   In this example, Line Chart has been used.
2. From the DATASETS panel:
   1. Drag the Date attribute into the Rows field of the EDITOR.
   2. Drag the Remaining Work Items metrics into the Columns field.
   3. Tab across to the Filter tab of the Editor. Drag the Iteration attribute into the filter section. Select the iteration for which you want the report.

Here's an example sprint burn down displayed graphically:

Analyzing the report

Using the report, the Scrum Master can do the following:

• Compare and analyze initial scope vs actual scope.
• Team's sprint burn down.
• Analyze and plan for the remaining work items to be addressed.