Team Agility Assessment

1. Team Name: Team Agility Assessment Survey Survey Date: 1/16/2015
Q1 - Team Disruption Q2 - NO Over-committing- team consistently delivers to it's commitment
m 0 – Manager/Leader disrupts team - 0 m 0 – Never
m 1 – Product Owner disrupts team - 1 m 1 – Rarely
m 2 – Managers or leaders telling people what to do - 3 m 2 – Occasionally
m 3 – Have Agile Leader and Scrum roles - 5 m 3 – Often
m 4 – No one disrupting team, only Scrum roles - 10 m 4 - Very Often
m 5 - Always
Q3 - Product Owner
m 0 – No Product Owner - 0 Q4 - User Story Acceptance- PO uses "Definition of Done"
m 1 – Product Owner who doesn’t understand Scrum - 1 m 0- No user story testing at all
m 2 – Product Owner who disrupts team - 2 m 1- Test sprint follows development sprint
m 3 – Product Owner not involved with team - 2 m 2- Development and test work sequentially within the same sprint
m 4 – Backlog estimated by team before Sprint Planning (READY) - 5 m 3- Tester tests a user story as soon as it is developed, without wait time
m 5 – Release roadmap with dates based on team velocity - 8 m 4 – Team exhibits swarming behavior i.e. everyone does testing
m 6 – Product owner who motivates team - 10 m 5- All user stories are developed, tested and accepted within same sprint
Q5 - Product Backlog Q6 - Agile Specification
m 0 – No Product Backlog - 0 m 0 – No requirements - 0
m 1 – Multiple Product Backlogs - 1 m 1 – Big requirements documents - 1
m 2 – Single Product Backlog - 3 m 2 – Poor user stories - 4
m 3 – Product Backlog clearly specified and prioritized m 3 – Good requirements - 5
by ROI before Sprint Planning (READY) - 5 m 4– Good user stories - 7
m 4 – Release burndown & velocty is used for release date- 7 m 5 – Just enough, just in time specifications - 8
m 5 – Measure ROI based on revenue & cost/story point- 10 m 6– Good user stories tied to specifications as needed - 10
Q7 - Testing within the Sprint Q8 - regression testing during sprint
m 0 – No dedicated QA - 0 m 0 – Never
m 1 – Unit tested - 1 m 1 – Rarely
m 2 – Feature tested - 5 m 2 – Occasionally
m 3 – Features tested as soon as completed - 7 m 3 – Often
m 4 – Software passes acceptance testing - 8 m 4 - Very Often
m 5 – Software is deployed - 10 m 5 - Always
Page 1 of 5

2. Team Name: Team Agility Assessment Survey Survey Date: 1/16/2015
Q9 - Predictable Internal/External Release Commitment Q10 - Iterations
m 0 – Never m 0 – No iterations (e.g. waterfall/kanban team) - 0
m 1 – Rarely m 1 – Interations > 6 weeks - 1
m 2 – Occasionally m 2 – Variable length < 6 weeks - 2
m 3 – Often m 3 – Fixed iteration length 6 weeks - 3
m 4 - Very Often m 4 – Fixed iteration length 5 weeks - 4
m 5 - Always m 5 – Fixed iteration 4 weeks or less - 10
Q11 - Team has tools & skills to consistently meet DoD Q12 - Sprint Burndown Chart
m 0 – Never m 0 – No burndown chart - 0
m 1 – Rarely m 1 – Burndown chart not updated by team - 1
m 2 – Occasionally m 2 – Burndown chart in hours/days not accounting for
m 3 – Often m 3 – work in progress (partial tasks burn down) - 2
m 4 - Very Often m 4 – Burndown chart only burns down when task in done- 4
m 5 - Always m 5 – Burndown only burns down when story is done - 5
m 6 – Bonus points if team knows velocity
Q13 - Estimates m 7 – More bonus points if PO's release plan based is on known velocity
m 0 – Product Backlog not estimated - 0
m 1 – Estimates not produced by team - 1 Q14 - Lack of fully dedicated and Cross-functional team
m 2 – Estimates not produced by planning poker - 5 Scrum team is fully dedicated, with cross functional team members.
m 3 – Estimates produced by planning poker by team - 8 e.g. includes UX, architect, dev, QA, docs, release engineer, localization, etc.
m 4 – Estimate error < 10% - 10 m 0 – Never
m 1 – Rarely
Q15 - Team Behavior m 2 – Occasionally
m 0 – Tasks assigned to individuals during Sprint Planning – 0 m 3 – Often
m 1 – Team members do not have any overlap in areas of expertise – 0 m 4 - Very Often
m 2 – No emergent leadership - member as directive authority -1 m 5 - Always
m 3 – Team does not have the necessary competency- 2
m 4 – Team commits collectively to Sprint goal and backlog - 7
m 5 – Team members collectively fight impediments during the sprint - 9
m 6 – Team is in hyperproductive state - 10
Page 2 of 5

3. Survey Responses 1 2 3
Q1 - Team Disruption 4 4 4
Q2 - NO Over-committing 4 2 4
Q3 - Product Owner 4 2 4
Q4 - User Story Acceptance 3 1 4
Q5 - Product Backlog 1 1 4
Q6 - Agile Specification 2 3 4
Q7 - Testing within the Sprint 3 3 5
Q8 - regression testing during sprint 5 2 2
Q9 - Predictable Internal/External Release Commitment 3 3 3
Q10 - Iterations 2 1 4
Q11 - Team has tools & skills to consistently meet DoD 3 1 4
Q12 - Sprint Burndown Chart 1 1 4
Q13 - Estimates 3 2 4
Q14 - Lack of fully dedicated and Cross-functional
team
2 2 4
Q15 - Team Behavior 3 2 4

4. Survey Category / Area
Maturity Level
1-Forming
2-Storming
3-Norming
4-Performing
Survey Category / Area
Maturity Level
1-Forming
2-Storming
3-Norming
4-Performing
Agile Best Practices 3 PO ownership- backlog quality 2
Lead Times (TTM) Trend 2 Agile Best Practices 2
PO ownership- backlog quality 2 Delivery of value 2
PO ownership- backlog quality 2 Velocity / throughput trend 2
PO ownership- backlog quality 1 Lead Times (TTM) Trend 2
PO ownership- backlog quality 2
Agile Best Practices 2
Agile Best Practices 2
Velocity / throughput trend 2
Delivery of value 2
Agile Best Practices 2
Velocity/
throughput trend
1
Agile Best Practices 2
Agile Best Practices 2
Agile Best Practices 2

5. PO ownership-
backlog quality
Engineering- best
practices
Delivery of value-
Velocity /
throughput trend
Lead Times (TTM)
Trend
PO ownership-
backlog quality
Engineering- best
practices
Delivery of value-
Velocity /
throughput trend
Lead Times (TTM)
Trend
1-poor to 1-minimal to 1-slipping 1-down to 1-down to
4-INVEST 4-rhythmic 4- tracking 4-steady 4-steady
LEGEND: Area-specific Assessment (scale of 1 to 4)
0
1
2
3
4
PO ownership-
backlog quality
Agile Best
Practices
Delivery of value
Velocity /
throughput
trend
Lead Times
(TTM) Trend
Overall Maturity Level
Maturity Level
1-Forming
2-Storming
3-Norming
4-Performing