CapTech Agile Maturity Measurement Template

A B C D E F G H I J K L M N O
1

2 Performance Measurement (Do-ing Agile)

3

od
od

eri
eri

P
P
4

us
nt

v io
rre
Cu

Pre
5 Predictability 4 2 Metric Descriptions
Assess predictability with velocity trends over time. A velocity that fluctuates wildly may reflect a team that is changing, work that is unpredictable, or sizing and
6 On-Time Delivery 4 3 Predictability
estimation consistancy issues.
On-time is often measured in context of expectations, i.e. what will be delivered. To measure and have visibility into what is being delivered, you can either look at
7 Time-to-Value 4 2 On-Time Delivery
burndown or burnup. Specifically focus on commitment versus actual delivery variance.

8 Product Quality 4 2 Time-to-Value Aka Cycle Time. This measurement should look at the cycle time of you primary development processes.

Predictability
9 Business Value 3 3 Product Quality Measure the rate of delivery of working software with quality. Example metrics include number of defects and build health

10 Business Customer Satisfaction 3 1 5 Business Value Apply a business value score to the features to be delivered to measure value.
Productivity On-Time Delivery
4 Customer/user satisfaction includes looking at relevant scoring statistics for your business. Example include Net Promoter score, sales figures, number of support calls
11 Productivity 4 4 Business Customer Satisfaction
3 vs. number of features delivered in a time period, or usage statistics of product capabilities.

12 2 Productivity Measure outcomes, not output. Look at burnup for a product or business value. Example: burnup of count of stories or features over time
1
13 Use the table above to enter the
"current period" score for each facet. 0
14 You can also enter a baseline or Alternate Chart Styles
15 previously measured score in the
16 "previous period" column. Business Customer Satisfaction Time-to-Value 5 4
17 Productivity
The current data displayed is for 4
4
18 example only. Business Customer 1
19 3 Satisfaction 3

20 2 3
Business Value
3
21 1
Business Value Product Quality
22
Want to know how to measure your 2
Product Quality
progress against each of these facets? 0 4
23 Take a look at the next 2 worksheets for
ity er
y ue ity ue on ity
24 example measurement forumlas and b il iv al al al ct
i
tiv Time-to-Value
2
ta el -V u sV a uc
4
background information. ic eD to tQ es isf
25 ed e- uc Sa
t od
Pr i m m od sin Pr 3
26 Don't forget, you should adjust this as -T Ti Pr Bu er On-Time Delivery
On t om 4
needed to work for your Agile Journey! us
27
sC Predictability
2
es 4
28 sin
29 Bu 0 1 2 3 4 5

30

31 Transformation Measurement (Being Agile)

32
od
od

eri
eri

33
P
ct P

us
v io
rre

Pre
Cu

34 Stakeholder Engagement 3 2 Metric Descriptions

35 Employee Satisfaction 3 2 Stakeholder Engagement Measurement of the satisfaction and involvement of stakeholders

36 Communication 3 2 Employee Satisfaction Measurement of the satisfaction of agile team members and leaders

1 Stakeholder Engagement www.captechconsulting.com Agile Maturity Metrics

Role Clarity Employee Satisfaction

5

4
 CapTech Agile Maturity Measurement Template

A B C D E F G H I J K L M N O
37 Planning Effectiveness 3 2 Communication Ceremonies, information flow, information radiation, agile practices, clear understanding and communication

38 Ceremonies & Processes 3 1 Stakeholder Engagement

Planning Effectiveness Focus on long term planning (PI/BRP) and measure volitility and accuracy against change drivers

39 Tooling 4 4 Ceremonies & Processes Process improvements, impediment mgmt, dependency mgmt, consistancy of process, effectivity and practice of standard ceremonies
Role Clarity Employee Satisfaction
5
40 Visualizing the work 5 4 Tooling Effectiveness and satisfaction with the agile tools (both dev and planning/mgmt tools)
4
41 Budget & Finance 1 2 Visualizing the work Visibility / Transparency
3
42 Team Stability 1 1 Budget & Finance Measure stewardship of investment, comparing investment over time to business value
Team Stability Communication
2
43 Role Clarity 4 3 Team Stability Measurement of turnover and longevity of the agile delivery teams, project based teams would score low
1
44
0
45 Use the table above to enter the Alternate Chart Styles
46 "current period" score for each facet.
You can also enter a baseline or 6 3
47 previously measured score in the Role Clarity 4
"previous period" column. Budget & Finance Planning Effectiveness
48 5 1
Team Stability 1
49 The current data displayed is for example
2
50 only. 4 Budget & Finance 1
51 Visualizing the work 4
3 5
52
Visualizing the work Ceremonies & Processes 4
Tooling 4
53 2
54 Ceremonies & Processes 1
Tooling 3
1
55 2
Planning Effectiveness 3
56 0
Communication 2
57 t
on n s s g rk e ty 3
en tio es se lin nc ili ity
em cti ica en es o o
na lar
58 ag fa tiv oc To e w
Fi tab 2
g tis u n c r th S eC Employee Satisfaction
En Sa m fe P g
et
& am ol 3
59 er ee m Ef & zin Te R
ld oy Co g ies ali dg 2
in on Bu Stakeholder Engagement
60 eho m
pl
a nn m isu 3
ak E l r e V
P
61 St Ce 0 1 2 3 4 5 6
62

2 www.captechconsulting.com Agile Maturity Metrics

Performance Measurement (Do-ing Agile)

Metric/Facet Measurement Type Facet Description

Predictability Quantatative Velocity Trend

On-Time Delivery Quantatative Commitment Stability

Time-to-Value Quantatative Cycle Time

Product Quality Quantatative Quality / Defects

 Value delivered to business
Business Value Quantative, Subjective
customers

Process and relationship

Business Customer Satisfaction Subjective Satisfaction of internal
customers

Productivity Quantative Cumulative Story delivery

Logical Description

Can we accurately predict the amount of work we can delivery

in an iteration

(Normalized Change in Velocity over previous X sprints)

Can we consistantly commit to and complete work in an

iteration

How long do our combined delivery processes take to deliver

valueable product

How many substantive development defects do we discover

after completion of the development iteration
Are we delivering consistant business value to our internal
customers

Do we have good working relationships with our internal

customers, and are we meeting their needs and expectations
consistantly

Measurement based on the Count of stories delivered over time

within the sample period
Calculation

(Recent Velocity / Average Velocity) -1

RV: AVG Velocity of Previous X Sprints (3)

AV: AVG Velocity of Previous Y Sprints (6+)

Variable: length of sample period

(Delivered Commitments / Total Commitments) -1

DC: # Commitments delivered in target iteration

TC: # Commitments planned in target iteration

Variable: length of sample period

AVG (Start Date - Delivery Date)

SD: Commitment
DD: Delivery to target environment

Variable: length of sample period

Variable: measuring feature time-to-value is recommended, however Story time-to-

value is still valuable and is often an easier metric to begin with

(Low + 2(Medium) + 3(High)) / Delivered Points

Low: Low severity defects in release/iteration

Medium: Medium severity defects in release/iteration
High: High severity defects in release/iteration
Delivered Points: Story points in release/iteration

Variable: Multiple for defect severity

(Recent BV / Average BV) -1

RV: AVG BV of Previous X iterations

AV: AVG BV of Previous Y iterations

Variable: length of sample period

Survey (Average, level of satisfaction)

Survey Topics, scale of 1-5:

Working Relationship
Product Quality
Speed of Delivery
Flexibility with change
Consistency and Predictability

(Recent Features Delivered / Average Features Delivered) -1

RFD: AVG # of Features delivered in Previous Iteration

AFD: AVG # of Features delivered in Previous X Iterations

Variable: length of Average Features Delivered sample period

Example Initial Measurement Scale

<= 10% Variation: 5

<= 20% Variation: 4
<= 30% Variation: 3
<= 40% Variation: 2
<= 50% Variation: 1

<= 20% Variation: 5

<= 30% Variation: 4
<= 40% Variation: 3
<= 50% Variation: 2
<= 60% Variation: 1

<= Ideal Release Cadence: 5

<= IRC + 5 business days: 4
<= IRC + 10 business days: 3
<= IRC + 15 business days: 2
<= IRC + 20 business days: 1

<= 5% Defect Rate: 5

<= 8% Defect Rate: 4
<= 10% Defect Rate: 3
<= 15% Defect Rate: 2
<= 20% Defect Rate: 1
<= 10% Decrease: 5
<= 20% Decrease: 4
<= 30% Decrease: 3
<= 40% Decrease: 2
<= 50% Decrease 1

Straight Conversion (1-5 Scale Average)

<= 10% Variation: 5

<= 20% Variation: 4
<= 30% Variation: 3
<= 40% Variation: 2
<= 50% Variation: 1
Why Use this Metric?

This metric helps teams become stable in their performance. This will encourage
managing risks and dependencies ahead of the sprints, and not over committing
within the sprint. Set goal for recent velocity to be within 20% of average. We
also want to see a reduction in the standard deviation of the velocity over time.

This metric highlights change (good/bad) between actual delivery and

expectations or commitments. On-time is frequently measured in context of
expectations, i.e. what will be delivered. To measure and have visibility into what
is being delivered, you can either look at burndown or burnup. Specifically focus
on commitment versus actual delivery variance.

This metric helps us determine whether we are optimizing our processes to get
out to market as quickly as possible. Note that the ideal release cadence is a
shifting measurement based on our planned release cycles. As the organization
matures, look to refine the ideal release candence and decrease processes which
length the time from development to delivery.

This metric provides insight to the number and severity of defects introduced into
each release. This should help us focus on high quality code delivery, which is
critical for successful agile teams.
This metric provides a view into the average business value (as determined by the
product owners) delivered by a team. As an effort nears completion or begins to
move from an innovation to an enhancement and support model, expect BV to
shrink. This is a good indication that it is time to look into realignment.

This metric provides insight in the relationship and success of our collaboration
between delivery and business leadership. If this score is low, it signals that we
have opportunities for improvement in our core processes between, specifially
from the team to external forces and business customers.

This metric provides insight into the outcome based productivity of our teams,
with features as the measurement unit. If the number of features delivered is
decreasing, this signals that we should look both at the feature refinement and
definition process, and impediments or processes which could be interfering with
overall productivity.
Transformation Measurement (Being Agile)

Metric/Facet Measurement Type Facet Description

Stakeholder Engagement Subjective N/A

Employee Satisfaction Subjective N/A

Communication Subjective N/A

Planning Effectiveness Subjective N/A

Ceremonies & Processes Subjective N/A

Tooling Subjective N/A

Visualizing the work Subjective N/A

Budget & Finance Subjective N/A

Team Stability Subjective N/A

Role Clarity Subjective N/A

Logical Description

Do the Stakeholders understand and have a voice in our agile

processes? include feedback from stakeholders and their points of
contact at the Program and Team levels.

Measure satisfaction and retention risk relative to the team

members performing within our agile delivery processes.

Is communication appropriate, timely, and complete; Measure

perception from multiple levels, executive level through team
member.

Are the planning processes providing the right level of details

(not too much, or too little), and is that time well spent.

Are fundamental processes successful at the team and program

level

Are our available tools sufficient and beneficail, are there

specific areas for potential improvement.

Visibility into the roadmap and shared understanding of the work

Is the budgeting and budget management process sufficient, are
there areas for improvement, and is the value delivered
commiserate with the investment made

Are teams persistent or are they prone to change

Do the players all understand their roles, and do those they work
with understand who to go to
Calculation

Survey - Executive, Portfolio, Program

Survey - Program, Team

Survey - Executive, Portfolio, Program, Team (ALL)

Survey - Portfolio, Program, Team

Survey - Portfolio, Program, Team

Survey - Portfolio, Program, Team

Survey - Portfolio, Program, Team

Survey - Executive, Portfolio, Program

Survey - Portfolio, Program, Team

Survey - Executive, Portfolio, Program, Team (ALL)

Example Initial Measurement Scale

Straight Conversion (1-5 Scale Average)

Variable: Weight the Executive and Village Scores

Straight Conversion (1-5 Scale Average)

Variable: Weight the Team Scores

Straight Conversion (1-5 Scale Average)

Straight Conversion (1-5 Scale Average)

Straight Conversion (1-5 Scale Average)

Straight Conversion (1-5 Scale Average)

Straight Conversion (1-5 Scale Average)

Straight Conversion (1-5 Scale Average)

Variable: Weight the Executive Scores

Straight Conversion (1-5 Scale Average)

Straight Conversion (1-5 Scale Average)