ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
dd/mm/yyyyAGILE HEALTH CHECK v0.1
2
Current RAG StatusPrevious RAG StatusInitial RAG Status
3
ExpectationFurther info
4
Product Ownership
5
Authority to represent Business and prioritise Product BacklogBusiness person able / empowered to prioritise backlog?RAG
6
Ability to form product backlog items, including acceptance criteriaSkills/ ability / knowledge to write effective user stories? Criteria articulated sufficiently to start time-boxed deliveryGGG
7
Daily review of deliverables, including ongoing reviewBusiness "pull" on deliverablesGGG
8
Participation in team eventsGGG
9
Increments will be delivered into Production-Quality environment at least every 2 monthsi.e. releasing into an environment which is of use to business. Or is additional testing required before releasing to live?GGG
10
Teamwork
11
Anticipation and removal of impedimentsAbility and / or authorisation to remove impedimentsGGG
12
Clarity of team boundaryAre roles & responsibilities clearly defined? Clear who forms part of the team?GGG
13
Availability of team membersOther commitments? Part time hours? WFH?GGG
14
Participation in team eventsGGG
15
Internal collaborationAre team working well together?GGG
16
Cross FunctionalIs cross-skilling required? Plans in place to address gaps?GGG
17
Ownership of processe.g. Are Dev team wholly responsible for estimating size of work? Do Dev team own their planned Backlog?GGG
18
Estimation is comprehensive and consistent, and velocity is stableEveryone takes full part in estimating and consider everything involved in completing that piece of work (e.g. length of time test runs may take)GGG
19
Events
20
Timebox planningAre these meetings happening? Are they effective?GGG
21
Timebox reviewAre these meetings happening? Are they effective?GGG
22
Timebox retrospectiveAre these meetings happening? Are they effective?GGG
23
Daily standup (time boxed to 15 minutes)Are these meetings happening? Are they effective?GGG
24
Backlog refinementAre these meetings happening? Are they effective?GGG
25
Product & Technical Debt
26
Is timebox burn rate acceptable?Are visual boards/ TFS showing throughput of user stories? On track to deliver MVP?GGG
27
Backlog is adequately populated, and sizedIncl. acceptance criteria, defects, new backlog items. Is backlog at a sufficient level of detail to start work from?GGG
28
Definition of Done is release-readyincl. testing, code review feedback is actionedGGG
29
Increments are valuableAre increments useful to the business? How will they be released?GGG
30
Scope flexes to control riskRatio of Musts / Shoulds / Coulds (ideally max 60% Musts)GGG
31
Technical Debt is being managedAccumulation of a backlog of technical inefficiencies that need to be serviced in the future e.g. defects, lack of refactoring. Level of debt? Are projects talking about a "hardening" sprint (not good Agile practice - what if project is stopped early?). Is debt 'cascading' and increasing in size ?GGG
32
Service Introduction engagedGGG
33
Financial Controls, Security and Data Conversion assessedGGG
34
Tooling
35
Ability to use agile toolse.g. knowledge / use of TFS, Test toolsGGG
36
Automated testing in placeGGG
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100