Trying to define a comprehensive CMMI like Agile Maturity Model?
If you're running all Scrum meetings but cannot deliver every sprint, you're not agile at all, if you don't follow any Scrum format but you're delivering small features every couple of weeks you're still Agile - deliver the highest value in the shortest time.
User Story Cycle Time - one universal Agile maturity measurement you might be able to use in your Organization cross different teams.
4. PAGE:
Team culture and environment
Common challenges for Scrum teams
4
Backlog refinement and User Stories
Agileplanningandestimation
Cross-functionalteams
Engineeringpractices
......
5. There could be 100 REASONS a Sprint fails,
but only 1 RESULT
PAGE: 5
Sprint Burn Down Chart - remaining feature incomplete
Day$1$ Day$2$ Day$3$ Day$4$ Day$5$ Day$6$ Day$7$ Day$8$ Day$9$ Day$10$
6. There also could be 100 REASONS a Sprint succeeds,
but only 1 RESULT as well
PAGE: 6
Sprint Burn Down Chart - remaining feature incomplete
Day$1$ Day$2$ Day$3$ Day$4$ Day$5$ Day$6$ Day$7$ Day$8$ Day$9$ Day$10$
7. The ultimate benefit/goal for Agile/Scrum is to
Deliver the HIGHEST value in the SHORTEST time
PAGE: 7
• You are NOT really Agile even if you have all Scrum meetings but cannot deliver;
• You ARE really Agile if you don’t have any Scrum activities but deliver small user
stories every couple of days
8. The traditional focus on the PRODUCT cycle time
PAGE: 8
Requirement Design Implementation Deployment
Kick-off Go-live
Product cycle time
Could be multiple years
9. The Agile focus on the STORY cycle time
PAGE: 9
Day$1$ Day$2$ Day$3$ Day$4$ Day$5$ Day$6$ Day$7$ Day$8$ Day$9$ Day$10$
Priority
Feature 1
Feature 2
Feature 4
Feature 5
Could be few days
10. Our target should be:
Deliver some pieces of real products to our end-
users every a few days
(DevOps)
PAGE: 10
11. So to the engineering team:
The SHORTER TIME we use to deliver 1 USER STORY,
the more AGILITY/MATURITY we have
PAGE: 11
12. It comes out one universal measurement
to the Agile maturity cross different teams:
The Story Cycle Time
PAGE: 12
13. Cycle time/wait time for one story
PAGE: 13
Vision
Enter PB Meet DoR Meet DoD
Go To Market
Release
Wait Time 1 Wait Time 2 Wait Time 3
Ready To Start DONE!
14. PAGE:
Story cycle time
= Average # of days for one Scrum team to deliver one user story
from meeting DoR to DoD.
Definition
14
Vision
Enter PB Meet DoR Meet DoD
Go To Market
Release
Wait Time 1 Wait Time 2 Wait Time 3
Ready To Start DONE!
Aka, Wait time 2
15. PAGE:
Extend Feature Cycle Time to other roles:
15
Vision
Enter PB Meet DoR Meet DoD
Go To Market
Release
Wait Time 1 Wait Time 2 Wait Time 3
Ready To Start DONE!
Product
Owner:
• Cycle
1me
=
average
#
of
days
to
deliver
one
user
story
from
vision
to
market
• (Wait
Time
1
+
2
+
3)
DevOps
(Engineering
Team
+
Cloud
Service):
• Cycle
1me
=
average
#
of
days
to
deliver
one
user
story
from
mee1ng
DoR
to
market
• (Wait
Time
2
+
3)
16. PAGE:
Simple and Clear
Benefit of using this metric
16
Covers all comprehensive factors to make it shorter
Focus on the final goal, not the process
Removedtheteamdifferences
Doable-easytocollectdata
17. PAGE:
• We focus on the outcome, leave the “how” to the team
• Individuals and interactions over processes and tools - we don’t need
another CMMI
Why not a comprehensive “Maturity Model”?
17
18. It doesn’t mean we’re against other measurement
Let the team study why they fail, find the
improvement areas by their own, and decide their
own goals to shorten the feature cycle time!
PAGE: 18
19. A quick quiz:
Team A: cycle time = 7 days
Team B: cycle time = 3 days
You’re a PO to start a new project, which team will you choose?
PAGE: 19
20. PAGE:
DoD environment - deploy feature to that sandbox every sprint
Next steps - suggestions
20
Communicate with the US teams
Start to collect the data of feature cycle time