Is Agility a business parameter that can be measured or is it a state that can only be sensed? If Agility means flexibility, nimbleness and adaptability, then how can those things be measured?
This article provides a simple survey to evaluate your team or organizations’ maturity. While the approach may not be entirely objective or accurate, it provides a reasonably good range of your agility across ten core areas. Give it a go.
Rate your organizational agility.
How are projects generally structured?
They are unstructured
According to systems development lifecycle (SDLC) phases of Requirements, Analysis, Design, Development, Testing and Roll-out
Structured according to technology stacks – Database, Application layer, front-end etc.
As discrete and independent components that are integrated later
Iterative and Incrementally structured around product features
How are project teams generally structured?
As one large team for the entire product / application.
As separate teams structured according to functions or phases such as Business Analysis, Development, Testing, etc.
As separate teams structured according to technologies or work-type such as Front-end, Back-end, Functional, Technical, etc.
As separate teams from customer organization and vendor organization with a common product focus
As a single cross-functional team of 10-12 members (or multiple small teams) working on a set of common product backlog
How are project teams generally located?
Distributed across continents
Distributed across the country
Distributed across offices in the same city
Distributed across rooms in one building
Co-located in one room
The Project teams mostly communicate through
Face to face conversations
How accessible are end users of the applications / products to Project teams
Don’t know who the end users are
End users are rarely accessible
End users are accessible only during the requirements phase
End users are accessible regularly
End users work closely with the project team, everyday
How is the project planned?
Not much planning
Detailed up-front planning
Activity based planning
Just enough planning
Adaptive and continuously planned
What is the attitude and ability to accept changes to project requirements?
Changes to requirements are not welcome after they have been “signed-off”
Changes to requirements are resisted during development
Changes are negotiated and only incorporated with an approved change request
Changes are accepted and incorporated within 4 weeks
Changes to requirements are welcomed and incorporated in the next cycle (Wait time is about 2 weeks at the most)
What is the approach to testing?
Ad hoc testing
How frequently do projects release software intothe production environment?
Once a year or longer
Once every six months
Once every three months
Once every month
At least every two weeks or earlier
How is project progress generally measured?
Verbal updates to stakeholders
Through formal status reports to stakeholders
Through demos to stakeholders
Through limited trials to users
Through working software every two weeks or earlier
Give yourself 1 point for 1), 2 points for 2), 3 points for 3), 4 points for 4) and 5 points for 5)
Add up all your points
Ok, what’s your score?
Interpreting the score
10-20 Poor Agility – Thanks for doing the survey – Unlicensed driver on the Agile Journey?
20-30 Average Agility – Your organization is still thinking about agility – Learner driver on the Agile journey?
30-40 Good Agility - Your organization is not bad at all. Provisional license on the Agile journey?
40-50 High Agility - Your organization is Agile – Full and unconditional license on the Agile journey?