Skip to main content

A List of Agility Tests

How many forms of Agility are there?  I know my friend's dog is a champion at doggy-Agility.  That form of Agility is well know (in the dog community) and it is all about the test.

For the purpose of this list I'm referring to the software development philosophy of Agility (as in Scrum, XP, Lean, etc.).  Since there is only one definition of Agile in the software community - the Agile Manifesto and it's 12 principles; it would appear to be easy to know what Agility meant.  Alas, it is more elusive than a simple Webster's dictionary definition.  There are too many personal and subjective measures.

But is a subjective experience beyond the ability to measure?  No, it is not.  The nature of an Olympic Platform Dive is a subjective event.  Yet it is measured and scored to a high degree of precession and accuracy to determine the winner in an event.  This is the process of moving the subjective beyond the laypersons personal feelings and into the realm of expert opinion.

Every assessment tool used for measure has aspects of reliability and validity.  Do the instruments (surveys) you are using have these aspects quantified?  If not then they are just ad-hoc hunches and in my opinion you are much better off not subjecting a team to them.  Because this form of directive, will prove to the team that you do not believe in good scientific process (after all you have suggested they use an arbitrary instrument of little validity to measure them).  You have also suspended your belief in the Agile Manifesto's "individuals and interaction over processes and tools" by choosing to use a tool when an interaction with the group would achieve the same results.  Results - what results?

What is the expected outcome of an Agility Assessment?  What results are you after?  Most of the companies I've dealt with wish to assess teams agility in hopes of identifying where to concentrate interventions.  Interventions are then designed to address areas in the team's performance where some action is desired to improve that dimension of Agility.  In so many cases one could just as easily ask the team - where do you wish to improve your Agility.  Wow - with just that one question and response (dialogue) not only have you identified a gap but there is an implicit "readiness to change", because they have identified the area for improvement rather than having been told.

List of Agility Assessment Tools
Ben Linders has a list of over 50 agile assessments - doesn't the magnitude of that list prove a point?  There are more agile assessments than there are principle of agile - surely someone is gilding the lily.

For Kanban:
By some measures the light-weight Agile processes have very few rules (about 9 for Scrum).  So how could a test of the process be larger than the process itself e.g. if Scrum only has 9 rules, then a test of scrum would be 9 questions about those rules.

Which Agile Process Should You Choose? a comparative study of Agile processes


Do you know of others - if so please add a comment.

See Also:

Assessments are not evil, however, I believe that if one choses to consume the teams time in performing an assessment then it should be a valid and reliable measure of what you wish to measure. Of all the assessments above I would argue that as of this date (May, 2011) none have been validated. The Nokia test has expert validity (Sutherland) to strongly suggest that it may be valid, however, it's reliability may be questioned as the data that Sutherland sites typically comes from himself (is there a bias conflict within that expert/validation and reliability claim?). My recommendation is the Comparative Agility survey. Rumor has it that Rubin & Cohn are interested in studying the surveys psychometrics (validity & reliability). This survey is very well executed and allows one to compare their relative score to their own over time (longitudinal study) and to other in their industry sector. With over 2400 surveys collected it may be the only large database of Agility surveys in a public domain. Why not chose to support the community by adding your team's assessment to this resource?

Here is a blog post for results of the Comparative Agility Survey on a very agile team I work with back in 2009.
4 comments

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…