Waiting Music

Tips for Meeting Attendees

Make sure to mute Turn off Refrain from

your microphone notifications, close replying to emails
when you are not or minimize or text messages
speaking. running apps, and during the meeting.
mute your
smartphone.
Thank you for Joining !
We will begin shortly !!
Systematic Customer Resolution Unravelling Meeting
 Quantifiable Measure of Performance Keep Teams Moving in Some Direction

Realistic Look at Health of the Organization Shows clear successes & failures
1 Velocity

2 Commitment Reliability

3 Capacity Utilization

4 Effort Estimation Variance

5 Scope Change

6 Defect Leakage

7 Backlog Health
1 Velocity
st
Unit of Velocity is Story Points

What is Velocity in Scrum?

Measure of work completed by the development team within each sprint

Sprint (2-4 Weeks) Sprint Backlog

Sprint Backlog

User Story Story Points User Story Story Points

User Story 1 5 User Story 1 5
User Story 2 7 User Story 2 7
… …
User Story N 3

Target Actual
Story Points = 15 Development + Testing + Acceptance Testing Story Points = 12
1 Velocity
st
Unit of Avg. Velocity is Story Points

What is Average Velocity in Scrum?

Average Velocity & Velocity are one and the same thing. Both are calculated in the same way as shown below.

Sprint 1 (2-4 Weeks) Actual = 29 S.P. Average Velocity of 6 Sprints =

Sprint 2 (2-4 Weeks) Actual = 34 S.P. Step 1:

29 + 34 + 10 + 25 + 30 + 28 = 156
Sprint 3 (2-4 Weeks) Actual = 10 S.P.

Sprint 4 (2-4 Weeks) Actual = 25 S.P. Step 2:

156 / 6 = 26 Story Points
Sprint 5 (2-4 Weeks) Actual = 30 S.P.

Sprint 6 (2-4 Weeks) Actual = 28 S.P.

 130 %

100 %
111 %
115 %
107 %
Velocity Trend
96 %

38 % Method 1

26 29 34 10 25 30 28

Avg.
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Velocity

130 %
115 %
111 % 107 %
96 %

Method 2
38 %

29 34 10 25 30 28

Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

 Velocity Trend
130 % Monitoring the Fluctuations
115 %
111 % 107 %
100 % 96 %

38 % Method 3

26 29 34 10 25 30 28 Step 1:
Avg.
Define Upper Limit = 40 %
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Velocity Define Lower Limit = 15 %

Step 2:
If we take 26 S.P. as average i.e. 100%
Upper Limit
Therefore,
Lower Limit
Upper Limit = 140 %
Average Velocity Lower Limit = 85 %
Velocity Trend
Step 3:
Draw Velocity Trend Bar Chart using limits
 Velocity Trend
Key Highlights

1) In Identifying team's current velocity.

2) Predicting how much scope can be delivered by a specific date.

3) Predicting a date for a fixed amount of scope to be delivered.

4) Understanding our limits while defining the amount of scope we will

commit for a sprint.
2 Commitment Reliability
nd
Unit of Commitment Reliability is Story Points

What is Commitment Reliability in Scrum?

Measure of total number of SPs Completed Vs Committed by the development team within each sprint It shows how
reliable a team is on their commitments.

Sprint 1 (2-4 Weeks) Committed = 29 S.P. Completed = 29 S.P. CR = 100%

Sprint 2 (2-4 Weeks) Committed = 34 S.P. Completed = 34 S.P. CR = 100%

Completed /
Sprint 3 (2-4 Weeks) Committed = 16 S.P. Completed = 10 S.P. CR = 62% Committed

Sprint 4 (2-4 Weeks) Committed = 30 S.P. Completed = 25 S.P. CR = 83% * 100

Sprint 5 (2-4 Weeks) Committed = 45 S.P. Completed = 30 S.P. CR = 67%

Sprint 6 (2-4 Weeks) Committed = 30 S.P. Completed = 28 S.P. CR = 93%

 Commitment Reliability Trend

120%
100 % 100 %
100% 93 %
83 %
80%
62 % 67 %
60%

40%

20%

0%
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
 Commitment Reliability Trend
Applying RAG Status

120%
100 % 100 %
100% 93 %
83 %
80% 67 %
62 % 0% – 80% = Red
60% 81% - 95% = Amber
40% 96% - 100% = Green
20%

0%
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
3 Capacity Utilization
rd
Unit of Capacity Utilization is Efforts (We will use HOURS here)

What is Capacity Utilization in Scrum?

Represent the available team capacity in hours and committed hours for each sprint, measured in effort hours.

Sprint 1 (2-4 Weeks) Available = 220 Hrs Committed = 130 Hrs CU = 59%

Sprint 2 (2-4 Weeks) Available = 240 Hrs Committed = 190 Hrs CU = 79%
Committed /
Sprint 3 (2-4 Weeks) Available = 280 Hrs Committed = 140 Hrs CU = 50% Available

Sprint 4 (2-4 Weeks) Available = 230 Hrs Committed = 200 Hrs CU = 87% * 100
Sprint 5 (2-4 Weeks) Available = 243 Hrs Committed = 221 Hrs CU = 91%

Sprint 6 (2-4 Weeks) Available = 226 Hrs Committed = 220 Hrs CU = 97%
 Capacity Utilization Trend

120%
97 %
100% 87 % 91 %
79 %
80%
59 %
60% 50 %

40%

20%

0%
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
 Capacity Utilization Trend
Applying RAG Status

120%
97 %
100% 87 % 91 %
79 %
80%
0% – 60% = Red
59 %
60% 50 % 61% - 85% = Amber
40% 86% - 100% = Green
20%

0%
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Capacity Utilization- Factors
4 th Effort Estimation Variance
Unit of Effort Estimation Variance is Efforts (We will use HOURS here)

What is Effort Estimation Variance in Scrum?

Estimation Variation represents the comparison of the effort that was planned (Estimated Hours) among the actual efforts
(Spent Hours) with in a sprint.
Over-Estimation
Sprint 1 (2-4 Weeks) Estimated = 130 Hrs Actual = 40 Hrs Variance = 69% E -A/
E
Sprint 2 (2-4 Weeks) Estimated = 190 Hrs Actual = 190 Hrs Variance = 0%
* 100
Sprint 3 (2-4 Weeks) Estimated = 140 Hrs Actual = 200 Hrs Variance = 43%

Sprint 4 (2-4 Weeks) Estimated = 200 Hrs Actual = 189 Hrs Variance = 6% Under-
Estimation
A-E/
Sprint 5 (2-4 Weeks) Estimated = 221 Hrs Actual = 178 Hrs Variance = 19% E
Sprint 6 (2-4 Weeks) Estimated = 220 Hrs Actual = 215 Hrs Variance = 2%
* 100
 Effort Estimation Variance Trend
Hours

250

200

150

100

50

Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

Estimated Actual Over-Estimated Under-Estimated

 5 th Scope Change
Unit of Scope Change is Story Points

What is Scope Change in Scrum?

Product Backlog Items added/removed from Sprint Scope/backlog during a sprint.

Sprint 1 (2-4 Weeks) Committed = 29 S.P. Added = 0 S.P. Removed = 10 S.P. SC = 34%

Sprint 2 (2-4 Weeks) Committed = 34 S.P. Added = 0 S.P. Removed = 0 S.P. SC = 0% Decreased Scope

Committed = 16 S.P. Added = 23 S.P. Removed = 0 S.P. SC = 144% (R / C) * 100

Sprint 3 (2-4 Weeks)

Sprint 4 (2-4 Weeks) Committed = 30 S.P. Added = 0 S.P. Removed = 15 S.P. SC = 50% Increased Scope

Sprint 5 (2-4 Weeks) Committed = 45 S.P. Added = 0 S.P. Removed = 0 S.P. SC = 0% (A / C) * 100

Sprint 6 (2-4 Weeks) Committed = 30 S.P. Added = 0 S.P. Removed = 0 S.P. SC = 0%

 Scope Change Trend
144%

0%

34%

50%

Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6

Estimated % Decrease in Scope % Increase in Scope

 6 th Defect Leakage
Unit of Defect Leakage is Number of Defects (Defect Count)

What is Defect Leakage in Scrum?

Total number of defects detected after Sprint Closure.

Defects During Sprint Defects Post Sprint

(DDS) (DPS)
Defect Leakage
Sprint 1 (2-4 Weeks) Defects = 20 Defects = 1 DL = 5%
(DPS / DDS) * 100
Sprint 2 (2-4 Weeks) Defects = 10 Defects = 0 DL = 0%

Sprint 3 (2-4 Weeks) Defects = 30 Defects = 4 DL = 13%

Sprint 4 (2-4 Weeks) Defects = 5 Defects = 1 DL = 20%

Sprint 5 (2-4 Weeks) Defects = 12 Defects = 4 DL = 33%

Sprint 6 (2-4 Weeks) Defects = 22 Defects = 6 DL = 27%

 Defect Leakage Trend
Applying RAG Status

40% 33 % 17% – 100% = Red

27 %
30% 6% - 16% = Amber
20 %
20% 0% - 5% = Green
13 %
10% 5%
0%
0%
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
 Defect Leakage Reasons
Environmental Dependency Test Not Run

Configuration Related Issues Data Dependency

Test Case Success Criteria Unclear Code Changes after testing

No Test Case/Coverage Requirements Missing/Changed

7 th Backlog Health
Unit of Scope Change is Story Points

What is Backlog Health in Scrum?

Total Story Points available in Product Backlog compared with Average Velocity.
52

Average Velocity (AV) = 26 S.P. 26 78

1 * AV 2 * AV

Product Backlog (AV) = 20 S.P.

< AV 3 * AV >>

Health Slab:
Less than Average Velocity
 52

Average Velocity (AV) = 26 S.P. 26 78

1 * AV 2 * AV

Product Backlog (AV) = 34 S.P.

< AV 3 * AV >>

Health Slab:
Meets Average Velocity

52

Average Velocity (AV) = 26 S.P. 26 78

1 * AV 2 * AV

Product Backlog (AV) = 60 S.P.

< AV 3 * AV >>

Health Slab:
Meets twice of Average Velocity
 52

Average Velocity (AV) = 26 S.P. 26 78

1 * AV 2 * AV

Product Backlog (AV) = 100 S.P.

< AV 3 * AV >>

Health Slab:
Meets thrice or more of Average Velocity
Why Backlog Refinement?

Flexibility Ability to Evolve a Plan

Prompt Debates Prioritization

Characteristics of Good Backlog

Detailed appropriately Estimated

Emergent Emergent
 .

Backlog Refinement
Includes:
Adding detail to high-priority backlog items for greater comprehension

Improving and reviewing estimates

Removing items that are no longer relevant to the product

Adding items based on new stakeholder feedback

Making adjustments based on the most recent bug fixes

Prioritizing items that bring customer value

Ordering backlog items to deliver the most impact over the next sprint
 Thank You
For Your Attention !

Drop your opinions/suggestions to me at: For further queries/clarifications do call me at:

akash.duhoon@thepsi.com 9990640034