Post on 21-Jan-2016
Project measurement techniques vs concept
of maturity capsule
Cezary OrłowskiGrzegorz Paciorkiewicz
March 2014
Version 1.1
Agenda
2
Current state of Software Project
Management – risk assessment
Maturity Capsule approach – method
of risk assessment
Verification of Maturity Capsule
approach Scrum Maturity Capsule
Failures in Software Project
3
Current state of Software Project Management
How to evaluate risk?
4
Maturity Capsule approach
Agile as a way of risk reduction
Agile vs Waterfall
Scrum Maturity Capsule
Scrum Maturity Capsule
Client
ProviderOrganization
ScrumMaster
Product Owner
Dev. Team
Very small
Small
Medium
High
Very high
Very small
Very small
Small
Small
Medium
Medium
HighVery high
High
(Provider)
(Client)
(Organization)
Very high
Wider context
6
Scrum Maturity Capsule
Normalized Velocity reveals Truth
Typical vs Normalized Velocity
1
2
34
56
7
7
Scrum Maturity Capsule
Dev. Team Maturity represents predictability
> 40% Very small [1]
30% - 40% Small [2]
20% -30% Medium [3]
10% - 20% High [4]
< 10% Very high [5]
Development Team Maturity
8
Scrum Maturity Capsule
Development Team predictability can be used for evaluation of PO estimation
Development Team Maturity
?
Very small
Small
Medium
High
Very high
9
Scrum Maturity Capsule
Yes or No questions can be insufficient approach
YES
NO
or
Don’t know
Hard to say
Not sure
Customer and Organization Maturity
10
Scrum Maturity Capsule
Product Owner does not really understood what the customer wants and needs.
Strongly Disagree [1]
Disagree [2]
Neutral [3]
Agree [4]Strongly Agree [5]
Investigation Questionnaire
11
Scrum Maturity Capsule
Customer Maturity (based on Product Owner role) Understanding of Sprint Scope and Goal (Process
of Planning) Quality Delivered to Customer (Process of
Review)
Investigation Questionnaires
Organization Maturity (based on ScrumMaster role) Scrum Team's Adherence to Scrum Rules Retrospective Process Improvement Engineering culture
Development Team Maturity Team velocity Team Enthusiasm
12
Scrum Maturity Capsule
Gathered Data
Product Owner and ScrumMaster maturity in linguistic scale
Product Owner Maturity
ScrumMaster Maturity
Very small
Small
Medium
High
Very high
13
Recommended to use bimonthly time periods for gathering data (not fewer than once in quarter)
Scrum Maturity Capsule
sampled once a month
Scrum Maturity Capsule
Very small
Small
Medium
High
Very high
Scrum Maturity Capsule
SMC - Verification
14
Scrum Maturity Capsule
Conclusions
A successful case Maturity Capsule adaptation in Scrum
Transparency increased on Scrum Team and
Scrum of Scrum level
High Development Team Maturity does not
guarantees project successfulness
SMC helps determining risk area
Overview The Scrum Core Elements
15
Grzegorz Paciorkiewicz (Intel Gdansk Poland)
grzegorz.m.paciorkiewicz@intel.com
Cezary Orłowski (IBM Center on Advanced Studies in
Campus)
cezary.orlowski@zie.pg.gda.pl
Questions?
Overview The Scrum Core Elements
16
Thank You