Professional Documents
Culture Documents
Agile Team Workbook Setup: P1 Art 1 I'm An ART Grasshoppers 7/2/2018 0
Agile Team Workbook Setup: P1 Art 1 I'm An ART Grasshoppers 7/2/2018 0
Agile Team Workbook Setup: P1 Art 1 I'm An ART Grasshoppers 7/2/2018 0
If using SAFe® remember that new teams use the 8 point rule to establish a forecasting velocity for PI Planning.
a.) 8 story points per development team member per iteration.
b.) Remove 1 point from capacity per day per developer of the iteration of non-productive time planned up to 8
points.
c.) The velocity is the same for all forecast iterations for PI Planning.
d.) Capacity for each iteration is the forecast velocity minus non-productive time (velocity minus non-productive
time).
e.) e.g. 8 devers = 8*8=64 velocity. Check out the blogagility.com velocipacity tool to learn the math.
f.) Once a new team completes their first iteration that velocity outcome becomes part of the teams velocity
(averaged over previous 3-5 iterations).
Setup your metrics workbook to get started.
@ 2018 Blogagility.com
SAFe® and Scaled Agile Framework are registered trademarks of Scaled Agile, Inc.
PI Planning - Team Iteration Metrics
Forecast + Actuals P1
Functionality Iteration 1.1 Iteration 1.2 Iteration 1.3 Iteration 1.4 Iteration 1.5
Team Velocity (forecast plan): 65 65 65 65 65
New Team Velocity Forecast from PI Planning (8pt 56.0 56.0 56.0 56.0 56.0
rule):
Non-productive efforts forecast (1pt per dev/day): 3.0 1.0 0.0 8.0 10.0
Capacity for PI Planning iterations: 62.0 64.0 65.0 57.0 55.0
Load: 57.0 41.0 61.0 50.0 54.0
Plan efficiency: 88% 63% 94% 77% 83% Team Feature Dev Predictability Measure
Load efficiency: 92% 64% 94% 88% 98%
Iteration Velocity (actual output): 160%
50 49 70 44 56
Team Velocity (actual/experiential): 59 54 56 54 57 140%
Team Feature Development Predictability
Measure (% Stories plan achieved) 140%
80% 100%
80% 56%
80% 92%
80% 94%
80% 120%
NoFill
Band 20% 20% 20% 20% 20%
100%
Understanding Work Flow
# User Stories planned 12 15 14 12 15 80%
# User Stories accepted (done) 18 15 8 11 14
60%
% of user stories accepted 150% 100% 57% 92% 93%
# of user stories not accepted (not achieved within 40%
-6 0 6 1 1
the iteration)
# of user stories pushed (rescheduled in next 20%
iteration)
0%
# of user stories not accepted (deferred to later 1 2 3 4 5
iteration)
# of user stories not accepted (deleted from
backlog)
# of user stories added during iteration (should be
0)
# Enabler Stories planned 3 1 2 1 1
# Enabler Stories accepted (done) 3 1 1 1 1
# of enabler stories new/changed during execution
# Total Story Points Planned (Load) 57 41 61 50 54
# Total Story Points Accepted (done) 50 49 70 44 56
Planned story points efficiency (80-100% target): 88% 120% 115% 88% 104%
# User Story Points Planned 36 29 36 40 36
# User Story Points Accepted (done) 32 34 45 36 32
# Enabler Story Points Planned 21 12 25 10 18
# Enabler Story Points Accepted (done) 18 15 25 8 24
# Story Points Unfinished 7 -8 -9 6 -2
# Features Planned
# Features Delivered and Accepted (done)
# of features new/changed during execution
# of features pushed (rescheduled to later
iteration)
# of features not accepted by PM
(quality/NFR/does not meet requirement)
# of features not accepted by PM (deleted from
backlog)
# of features added (pulled) by the team during
the iteration (execution) [should be 0]
Built-in Quality (create charts for the measures your team is using)
# hours pair work/mob programming
% Unit tests code coverage?
# of priority one (high) defects
# of severity one (very) defects
Total # of defects
Defect count at start of iteration
Defect count at end of iteration
# of recovery automation enhancements
(DEVOPS)
# of deployments to all environments
# of releases to production
# of releases to end users
Calculated change lead time
Calculated change failure rate
Calculated Mean Time to Recover (MTTR)
# of new unit test cases
# of new manual test cases
# of new integration test cases
# of new system test cases
# of new acceptance test cases
# of tests automated
# of manual tests
Total # of tests
Total % of tests automated
# of new behavior driven development tests
# of Refactors
Total Story Point Planned vs. Achieved User Story Point Plan vs. Achieved Enabler Story Point Plan vs. Achieved
80 50 30
70 45
40 25
60
35
20
50 30
40 25 15
30 20
15 10
20
10
5
10 5
0 0 0
Iteration 1.1 Iteration 1.2 Iteration 1.3 Iteration 1.4 Iteration 1.5 Iteration 1.1 Iteration 1.2 Iteration 1.3 Iteration 1.4 Iteration 1.5 Iteration 1.1 Iteration 1.2 Iteration 1.3 Iteration 1.4 Iteration 1.5
# Total Story Points Planned (Load) # Total Story Points Accepted (done) # User Story Points Planned # User Story Points Accepted (done) # Enabler Story Points Planned # Enabler Story Points Accepted (done)
70
60
50
40 Product Backlog
Sprint Backlog (# stories)
In-progress
30 Review
Done-DoD
20
10
0
7/2/2018 7/3/2018 7/5/2018 7/6/2018 7/9/2018 7/10/2018 7/11/2018 7/12/2018 7/13/2018 7/16/2018
45
50
45 40
40 35
35
30
30
Product Backlog 25
Sprint Backlog (# stories)
25
In-progress
20
Review
20 Done-DoD
15
15
10
10
5 5
0 0
7/17/2018 7/18/2018 7/19/2018 7/20/2018 7/23/2018 7/24/2018 7/25/2018 7/26/2018 7/27/2018 7/30/2018 7/31/2018 8
45 45
40 40
35 35
30 30
25 Product Backlog 25
Sprint Backlog (# stories)
In-progress
20 Review 20
Done-DoD
15 15
10 10
5 5
0 0
7/31/2018 8/1/2018 8/2/2018 8/3/2018 8/6/2018 8/7/2018 8/8/2018 8/9/2018 8/10/2018 8/13/2018 8/14/2018 8/15/2018
45
40
35
30
Product Backlog
Sprint Backlog (# stories)25
In-progress
Review
20
Done-DoD
15
10
0
15/2018 8/16/2018 8/17/2018 8/20/2018 8/21/2018 8/22/2018 8/23/2018 8/24/2018 8/27/2018
8/28/2018 8/29/2018 8/30/2018 8/
Product Backlog
Sprint Backlog (# stories)
In-progress
Review
Done-DoD
Actual Plan
tual Plan
Burn-down
Burn-down
Burn-down
Burn-down