Open topic with navigation

Analyzing work items across iterations

Let us look at a simple scenario to understand how you can use the Work Item Iteration iCube to analyze your work items.

John is a Scrum Master who does the iteration planning, manages the scrum process, and ensures timely delivery.

As a Scrum Master, he would like to analyze if and how many work items have had multiple iterations, and which of his team members are handling the highest amount of spill overs. Work Items ideally should be broken down to sub-tasks that can be completed in one iteration and ideally, should not spill over multiple iterations. Work Items spilling over multiple iterations would mean that iteration planning was not done in an effective way. Analyzing this would help John in planning and allocating tasks and resources better. Analyzing the work items in an iteration enables him to:

• Break work items into sub-tasks that can be handled in a single iteration
• Branch out time consuming tasks and allocate multiple resources to handle the task
• Plan work items in a more effective manner

Generating the report

To analyze high priority work items assigned to a user that have spilled across multiple iterations, John has to login to N360™ and perform the following tasks in the Work Item Iteration iCube of Create Lens:

1. From the GALLERY panel, select the desired visualization type here.
   In this example, Bar Chart has been used.
2. From the DATASETS panel:
   1. Drag the Priority attribute into the Rows field of the EDITOR.
   2. Drag the Work Item attribute into the Rows field.
   3. Drag the Priority attribute into the Color By field.
   4. Drag the Iteration Count metric into the Columns field.

3. In the FILTER tab of the EDITOR,
   1. Drag and drop the Priority attribute and check Blocker, Critical and Major.
   2. Drag and drop the Resolved By attribute and enter the name of the employee.

Here's an example analysis displayed graphically:

Analyzing the report

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

• Analyze work items that have spilled across multiple iterations to brainstorm on the reasons for spill over.
• Create sub tasks for similar work items in the future iterations such that spill over is mitigated.