Metrics to measure effectiveness of Sprint Review.

1. SCALING AGILE: SAI
APRIL: 2016
1

2. 2

3. THE STORY : UK FINANCIAL INVESTMENT ADVISORY
• Total assets now exceeding £8 bn
• Extensive coverage of the investment and tax wrapper market
• Integrated fund supermarket, stockbroking and cash management
solutions
• 3 vendors working on same application.
• Globally distributed teams.
• Scrum of Scrum.
Enhance existing OCS (Online Client Setup) application which interacts with legacy system with new business capabilities
with integrations to a 3rd party application
Business Model

4. 4
All scrum ceremonies religiously
followed in project.
 Proper well-defined and scoped
Sprint backlog.
 Sprint refinement and grooming
session.
 Sprint Demo & refinement.
 Devop’s environment to support
quicker and faster deliverables .
 Working product delivered, signed
off and accepted by product owner.
Approach Followed
Initial 10 sprints, everything seems to be
in accordance with client expectations.
 No major concerns had been
highlighted by client.
 Client was happy with the
deliverables and velocity.
 Product was getting released to
UAT environment on time.
 Product owner also being happy with
the working product available at its
disposal.
Results till Sprint 10

5. INGREDIENTS FOR GOOD SPRINT REVIEW
5
Working software is the primary measure of progress.
Hence a few key factors need to be focused during a Sprint Demo, like:
 Focus on Sprint Goal.
 Keep acceptance criteria in mind.
 Cover all user stories completed.
 Team to give demo of working product, scrum master only moderates the
session.
 Provide code quality metrics overview towards end of demo.

6. THE SMOKE THAT ROSE
In CSAT survey, client raise concerns
about the delivered product.
Quality of code written by our team
was questioned.
Architectural stability was
questioned by client. Overall
technical competency of our team
was under surveillance .
Annual CSAT Survey Annual CSAT Survey
Account
Retrospection
Need to capture sprint review
effectiveness objectively.

7. HUNGRY TRAVELERS
Annual CSAT Survey
How Satisfied they are ?
Were They really
Satisfied ??

8. MEASURE SPRINT EFFECTIVENESS
Annual CSAT Survey
SAI = (∑ (User story rating * Number
of Story Points) / Total Story Points in
current sprint.)
% of Stories rated 4&5 = (Number of
user stories rated 4&5) / Total
number of user stories.
 Ask PO to rate user stories on
scale of 1-5 during Sprint Demo.
 5 representing highly satisfied
customer.
Sprint Acceptance Index (SAI)
SD-Cube = Cumulative demo
comments weightage / Number of
story points delivered.
 Capture all the comments
provided by PO during demo.
 Categorize these comments into 4
types and assign weightage..
Sprint Demo Defect Density (SD-Cube)
Comment Type Weightage
Change Request 0.5
Defect-Minor 1
Defect-Major 2
Defect-Critical 3

9. 9
 Higher SAI: More satisfied customer is with product Demo
 Lower the value of SD-Cube more bug free software had been available to go live
environment.
 Help us in stabilizing the trend how are we performing sprint wise.
 Provide an actual measure which helps us in capturing our grey areas in product
where we may to focus more.
KEY SUCCESS FACTORS

10. THANK YOU
10