Assessing iteration completeness

This topic describes how to use dashboards and the release plan to determine whether the team is on target to complete all the plan items that are scheduled for the current iteration.
This graphic is a workflow diagram that shows the steps that make
up the assess iteration completeness task. Click this area to get information about fixing defects and verifying Click this area to get information about querying for defects Click this area to get information about fixing defects, delivering, and building Click this area to get information about verifying fixes Click this area to get information about configuring the development dashboard Click this area to get information about configuring the release plan Click this area to get information about configuring the requirements collection

Typically, the project manager completes this task.

Before you begin

You must have created project-area dashboards for the development team and the requirements management team.

Step 1: Configure the development dashboard

In Querying for defects, you created a dashboard for the development team's project area and added development, testing, and requirements pages. In this step, you use the development and testing pages to look for outstanding work items.

  1. Navigate to the development page of the development team's project area dashboard. Add a Burndown chart. Add the Open work items widget.
  2. Review the widget to ensure that the display includes no open work items for the current iteration.
  3. Navigate to the testing page of the dashboard. Review the Defects blocking Tests widget to ensure that all defects have been resolved.
  4. Navigate to the requirements page of the dashboard. Add the Requirements Tracing widget and specify the requirements collection. Specify Implemented By as the link type to show the development plan items that are associated with the requirements.
  5. Add a second Requirements Tracing widget and specify the same requirements collection. Specify Validated By as the link type to show the test cases that are associated with the requirements.
  6. Hover over the links to the plan items and test cases in the two traceability widgets to see the status of those artifacts and verify that all development work has been completed and tested successfully.

Step 2: Configure the release plan

On the Planned Items page of the release plan, edit the Iterations view by adding the Affected by Defect and Tested by Test Case columns. Review the plan items for the current iteration to see whether the Affected by Defect column contains any entries. Review the Tested by Test Case entries to ensure that each plan item has been adequately tested.

Supporting tasks:

Step 3: Configure the requirements collection

In the requirements management application, open the requirements collection and add the Implemented by and Validated by columns. For each requirement, ensure that the corresponding plan item has been implemented and tested.

Results

You have verified that the development work required to implement the requirements in this iteration has been completed. You have also verified that all defects that the testers submitted against that development work have been fixed.

What to do next

Now that you have completed an iteration, you can publish the results. You can also begin planning the next iteration.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki