Open topic with navigation

Analyzing work items across versions

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

Joe is a Project Manager involved in planning and execution of multiple projects.

As a Project Manager, Joe wants to analyze critical work items that affect multiple versions of a software. For example, consider a software being developed in an organization and has had multiple releases. A critical bug that comes to the fore, may have gone unnoticed but, existed for a considerable amount of time. A development manager may want to analyze such bugs as fixing the bug in all affected version (even previous versions) becomes critical from cost as well as effort perspective.

Generating report

To analyze the work items in affected version, Joe has to login to N360™ and perform the following tasks in the Work Item Iteration Affected Version iCube of Create Lens:

1. From the GALLERY panel, select the desired visualization type here.
   In this example, Pie Chart has been used.
2. From the DATASETS panel:
   1. Drag the Work Item Count metric into the Angle field of the Visualization Editor.
   2. Drag the Affected Version attribute into the Color By field of the editor.
   3. Drag the Affected Version attribute into the Slice field of the editor.

Here's an example analysis displayed graphically:

Analyzing report

Using the report, the Project Manager can do the following:

• Analyze number of work items impacting a particular affected version
• Analyze a particular affected version for the number of work items that need to be addressed