ScrumWorks Pro Best Practice Guide:

Size: px

Start display at page:

Download "ScrumWorks Pro Best Practice Guide:"

Alice Lawson
6 years ago
Views:

1 ScrumWorks Pro Best Practice Guide: Release Schedule Forecasting using the ScrumWorks Pro s Enhanced Burndown Chart

2 Enhanced Burndown Chart

3 Pre-requisites General understanding of Product Backlog, Backlog Effort, and Backlog Estimation. Best Practice Guide: Backlog Estimation

4 Elements of Forecasting Schedule Velocity: rate of team progress Changes to Project Scope Effort changes due to Re-estimation

5 Velocity Measure of a team s rate of progress per iteration Calculation: Sum of Backlog Effort completed per Sprint by Team(s) An empirical metric: based on real, observed progress Velocity can be used to derive duration and extrapolate schedule Release Burndown charts show team s rate of progress and the rate of scope creep against the schedule.

6 Changes to Project Scope Projects are dynamic and scope changes are normal Common reasons for scope change: Changing business needs Feedback driven change Bug reports The rate of scope change is a factor in forecasting release schedule

7 Re-estimation Re-estimation happens when: Team learns more about an item Team realizes they know less than previously thought Instability due to high risk or uncertainty Re-estimation must be taken into account when forecasting release schedule

8 Putting it Together Enhanced Burndown Chart: Separate trend lines Velocity trend line Trends the rate of change (due to scope changes and re-estimation) Intersection of velocity and rate of change trend lines represents completion forecast

9 Bars represents total effort outstanding each sprint Work completed by the team lower height of the bar Work added due to scope change or re-estimation is added below the bar, in negative territory

10 Red line represents team s velocity trend Blue line represents the rate of change due to scope changes and re-estimation. Change due to team s progress is tracked separately from other changes.

11 Intersection of these two trendlines is the forecasted completion date Empirical forecast of schedule Note: for multiple teams, overlapping sprints are aggregated to create a cumulative burndown

12 Diverging lines Indicates product scope is growing faster than team(s) can complete work Reality

13 Enhanced Burndown in ScrumWorks Pro: Reports menu Select Enhanced Product Burndown Select desired releases for inclusion (typically just one or two) Click Build Chart If lines converge, Forecast completion is enabled

14 Troubleshooting Mark items Done Marking items Done is how team(s) get credit for work in terms of velocity Typically done by Product Owner during the review meeting. We forgot the estimate, now our data looks strange You may need to back-date your estimates so they better reflect reality. Do this through the History tab on the backlog item editor.

15 Summary Forecasting schedule in ScrumWorks Pro involves: Velocity - the rate of team progress Changes to the Project Scope Re-estimation of existing items Enhanced burndown chart trends work completed by team separately from other changes Intersection of trend lines gives schedule forecast Parallel and diverging trend lines are red flags

SAFE REPORTING GUIDELINES for CLM 6.0.3

SAFE REPORTING GUIDELINES for CLM 6.0.3 Deploying the SAFe reports in your CLM JRS 6.0.3 environment Abstract This document describes how to import the SAFe reports delivered via archive files published