Lesson 3.1: Prepare for a sprint shutdown
In this lesson, you update a dashboard with widgets that help guide the iteration toward closure. During a shutdown, you focus on closing new development and improving the quality of the planned features.
About this task
In this lesson, you learn how to complete these tasks:
- Determine which dashboard widgets and queries to use to stabilize a sprint.
- Review a plan by using traceability views.
- Approve the build at the end of a sprint.
Exploring widgets
About this task
Procedure
- On the Dashboard General page, view
the Open Stories widget.
Note: There are several open stories that apply to the entire release. In this lesson, you are interested only in stories that are open for the current iteration.
Exploring planning
About this task
Procedure
On the dashboard, click the Planning tab. On the Planning page, explore these widgets:
- The Current Plans widget shows how much of sprint 2 is complete.
- The Open Stories widget shows that sprint 2 has several open stories, which is normal because you are at the start of the sprint.
- The Open Impediment widget lists the impediment issues that the scrum master needs to address now or in the next release
- The Resolved for Current Iteration widget describes completed work items, but does not describe what work items remain.
Exploring development
About this task
Procedure
On the dashboard, click the Development tab. On the Development page, explore these
widgets:
- On the Open Stories (current iteration) widget, view all the unassigned stories that, as scrum master, you must assign. You can also view all of Marco's open work items.
- On the Open Work Items (current iteration), Severity widget, view all the stories that you must close before you can declare this sprint complete.
Exploring testing
About this task
Procedure
On the dashboard, click the Testing tab. On the Testing page, explore these widgets:
- The Defects blocking Tests widget is empty. This widget applies to the entire release, and not just the current sprint. As a scrum master, regularly check this widget, and keep it empty.
- The Defects affecting Tests (current iteration) widget is also empty. This widget applies to the current sprint. On this widget, keep the number of defects low.
- On the Stories tested successfully widget, view the story that you completed in an earlier lesson. Use this widget to ensure that all stories for the sprint are tested successfully.
Exploring requirements
About this task
Procedure
On the dashboard, click the Requirements tab. On the Requirements page, explore these
widgets:
- As scrum master, work toward closing the requirements on the Open Requirement Change Requests widget.
- Use the Defects affecting Requirements widget to prioritize and triage defects.
- Work toward keeping the Open Impact Analysis Tasks widget empty.
Exploring reports
About this task
Procedure
On the dashboard, click the Trends tab. On the Trends page, view the Sprint burndown
chart. Ideally, this chart moves downward to 0, following the planned
line.
Exploring stabilization
About this task
Procedure
On the dashboard, click the Stabilization tab. On the Stabilization page, explore these
widgets:
- The Open High Severity Defects widget lists defects to resolve before closing the sprint. Work toward keeping this widget empty.
- The Defects affecting Tests (current iteration) widget is empty, which is the goal. This widget applies to the current sprint. As the project moves from sprint to sprint, keep the defects in this widget low.
Adding a widget
About this task
Procedure
- In the upper right corner, click the Close icon to close the widget palette.
Configuring a widget
About this task
Procedure
- Click OK.
The query runs, and the widget is configured. Throughout the sprint, your goal is to triage these defects. During stabilization, your goal is to keep this widget empty of results.
Organizing widgets
About this task
Procedure
- Save the dashboard.
Lesson checkpoint
In this lesson, you learned how to complete these
tasks:
- Determine which dashboard widgets and queries to use to stabilize a sprint.
- Review a plan by using traceability views.
- Approve the build at the end of a sprint.