The Agile Score Sheet for your project

	A	B	C	D	E	F	G	H	I
1

2
3		Don't know		Completely disagree				Completely Agree
4		N/A		1	2	3	4	5
5	The Start - Waterfall
6	I spend my days preparing a project plan		4				x		NOTE: the score
7	I have many meetings about Architecture and Requirements		2		x				should be your
8	I spend many days editing in Word, Powerpoint and/or MS Project		3			x			average score, not
9	The start phase is long (weeks or months) and ends in a "gate meeting" where the project plan and requirements will be approved		4				x		counting the N/A
10	No one in the team is writing code for this project at this time		5					x
11	The team doesn't exist yet, or has only project/product managers and tech leads/architects in it		2		x
12	If a prototype is being developed it is a throw-away and done by a subcontractor		1	x
13								Your waterfall score?	21
14	The Start - Linear Iterative (e.g. RUP)			1	2	3	4	5
15	This project phase has a name that has something to do with "start" or "concepting"
16	This project phase ends with a "gate meeting" where we approve the project plan and possibly a requirements list
17	Some people in the project are already coding, but most teams are not working for this project yet
18	Teams are being added to the project as they become available
19	Requirements are collected in the form of Use Cases, but not a list of detailed individual requirements
20	Many use cases will be changed during the project execution/implementation phase
21								Your Linear Iterative score?
22	The Start - Agile			1	2	3	4	5
23	This is a short phase where a proposal for a project is presented and approved
24	Teams are allocated to the project immediately after the project approval
25	Teams start designing and coding immediately
26	The project plan is basically a target release date plus a backlog of high-level features to be implemented
27	The project is divided into short timeboxes called increments/sprints/iterations (short <= 3 weeks)
28	The teams demonstrate working software at the end of each increment
29	The teams talk about releasing software from day 1
30	Each team includes all necessary skills to implement, test and release a feature (no separate testing teams)
31	Requirements are reviewed for every increment and acceptance criteria defined to ensure common understanding
32	Sometimes the requirements and acceptance tests are updated during the short increments
33								Your Agile score?
34	The Middle of the Project
35	The Middle - Waterfall			1	2	3	4	5
36	We don't have any explicit coordination between teams, especially at the integration level						x
37	We have a plan to follow that everyone must report against
38	Teams in the project work on specific components and share specifications when needed
39	Teams develop their components in their own branch and integrate only when they pass the quality gate for submission
40	The project has pre-defined synchronization points between teams where code should be integrated								NOTE: the score
41	When needed teams schedule "integration camps" or "code fests" where people come together to make the product work								should be your
42	Some teams are doing overtime because they are behind the plan								average score, not
43	When the schedule pressure increases the teams are pushed to work faster								counting the N/A
44	No one remembers the endless months we spent arguing over the project plan before the project started
45								Your waterfall score?
46	The Middle - Linear Iterative (e.g. RUP)			1	2	3	4	5
47	The teams meet regularly (every few weeks) to integrate their code
48	We have scheduled "integration camps" or "bug/code fests" to weed out the integration bugs and integrate the code
49	There is a very detailed "code line" policy in the company/project to prevent teams from messing up the code in the Version Control System
50	Project Managers are worried about branches and code-merging milestones
51	The project iterations are about 2-3 months long
52	The integration of code from different teams happens normally only at the end of each 2-3 month iteration
53	Some teams demonstrate their work to some stakeholders
54	I've heard that some teams hold some meetings they call "retrospectives"
55	The project management team has held some meetings they call "project retrospectives"
56								Your Linear Iterative score?
57	The Middle - Agile			1	2	3	4	5
58	The project teams have started to gel, they work well together
59	The project has started to gain momentum, there's a feeling of "just rolling"
60	The project teams demonstrate regularly that they have accomplished
61	Many teams hold retrospectives at the end of every sprint/iteration
62	Some teams have stopped holding retrospectives because "they have nothing else to improve"
63	There's a Product Owner (or more) and the Product Manager is mostly meeting customers
64	The Product Owner is always available to the teams, and in some cases it is a team member
65	The Product Owner is working regularly with the Product Manager
66								Your Agile score?
67	The End of the Project
68	The End - Waterfall			1	2	3	4	5
69	In this phase we have the "code complete" or "code freeze" gate
70	The testing teams are assigned to the project mostly after this "code complete/freeze" gate
71	The test teams are not experts in the product and they may be testing other products as well						x
72	The project typically runs out of time before we understand the quality level
73	The project is delayed because the desired quality level is not reached								NOTE: the score
74	Many bugs are still found, but the rate of fixing them is at the same level or slightly above the rate of finding them								should be your
75	Management increases the pressure for teams to "fix more bugs" or "work harder" (or "smarter")						x		average score, not
76	Overtime is used regularly to help speed up the project								counting the N/A
77	There's a clear increase the the number or motivational emails and speeches by "managers"
78	The business imperative takes precedence and is the main decision driver for the release date
79								Your waterfall score?
80	The End - Linear Iterative (e.g. RUP)			1	2	3	4	5
81	Teams are still developing their code in their isolated version control systems or branches
82	The "vertical" projects have reached "feature complete" and are mostly fighting with code-merge problems
83	At this point we have a "test and fix" phase that is quite hectic
84	At this point the testing is focused on "complex use cases" (i.e. Integration of all components in the system)
85	Most bugs are found at the end of the project and we see a steep rise in the number of open bugs
86	We have a sophisticated statistical model based on historical data that tells us when we are likely to release based on the bug count
87	The business imperative takes precedence and is the main decision driver for the release date
88	This phase has a pre-set length based on historical data from other projects
89								Your Linear Iterative score?
90	The End - Agile			1	2	3	4	5
91	Teams are still busy developing new features
92	There is no "feature complete" or "code freeze" gate in the project
93	The open bug list is short and constantly prioritized
94	Teams pro-actively follow the list of open bugs and some teams start the sprints/iterations with bug fixing
95	There's a clear pressure to add more features at the end of the project (instead of only test and fix)
96	The test code is as highly regarded as the production code
97	There's a large ammount of test code that is delivered with the production code
98	Teams are confident that they can make changes in the software up to the last minute without any risks of breaking something critical
99								Your Agile score?
100