How Agile Are You? (The Survey!)


feature photo

As Kelly Waters explained in his recent blog post about Agile101, one of our challenges as a management team has been Agile Programme Management i.e how to manage an overall portfolio of work when all of the teams are doing Agile.

One of the seven principles of Programme Management is “Learning from Experience”, a principle that sits at the heart of the Agile manifesto.  Agile teams use Retrospectives to discuss ‘the following points:

  1. What went well in the previous sprint?
  2. What went badly in the previous sprint?
  3. What will we do differently next time?

I originally learned of the original How Agile Are You survey when Kelly joined our company in late 2008. Kelly was inspired by Nokia measuring the Agility of their teams via a 9 criteria assessment so he took this concept one step further… actually he took it 33 steps further and introduced a 42 point criteria – .

These 42 questions range from ”is the team empowered to make decisions” to “automated unit testing is implemented where appropriate”.

We started off by asking every member of the department to complete the survey. I then collated the results and ranked each criteria by perceived level of compliance i.e. there were a couple of criteria that everyone felt we complied with but opinion was divided in the majority of cases (to varying degrees).  In a few instances, there was a unanimous agreement that we did not meet the criteria. Interesting.

We then used the survey results to drive our monthly Programme Level Retrospectives for a time. This helped to add focus to the sessions – we knew where we were under performing and we had a very clear idea for where we wanted to be.

Every month, we reviewed the results and discussed our performance in the five lowest-ranking areas. We brainstormed ways to improve this performance and shared notes on the progress we were making. After this session, each team would choose one or more criteria to focus on over the coming month.  They also committed to a number of objectives that we would use to measure their success in the following Retrospective. Each team made different commitments – it was up to them where they wanted to focus.

After a few months, we saw a huge improvement in our adoption of Agile working practices and of the team’s understanding of Agile in general. It was a great learning experience.


Subscribe to the to be notified when I upload new Articles, Videos, Templates and Tips!

Download How Agile Are You Survey & Plot Team Results on a Graph

Related Articles:

Share this!
  • Print
  • PDF
  • del.icio.us
  • Digg
  • DZone
  • Reddit
  • Technorati
  • StumbleUpon

3 Responses to “How Agile Are You? (The Survey!)”

  1. Hi Dan – You’re welcome!

    I’m not sure I agree that it is essential (or viable in a lot of cases) to have a customer involved in sprint planning. That is if by ‘customer’ you mean the end user of the product e.g. a visitor to a website if your website is your product.

    The only people required to attend a sprint planning meeting are the Product Manager, a Product Owner(s) if possible/appropriate (e.g. you’re discussing multiple products within the session and the Product Manager is less familiar with certain aspects) and the Scrum Team. In some situations, the Product Manager may even leave after presenting the backlog and agreeing the Sprint Objectives – at this point it’s up to the Scrum Team to figure out the specifics of their Sprint delivery strategy.

    I’ve written a blog post about how to run a Sprint Planning session - check it out and let me know if you do things differently.

    Hope that makes sense,

    Tara

  2. Dan Loomis says:

    Thanks for sharing the Agile survey in excel. Shouldn’t one of the questions that determines “Agileness” be whether your customer is involved in sprint planning?

  3. Dan Loomis says:

    Makes perfect sense. I run our sprint planning as you’ve indicated in your blog. In some resources that I’ve read about Agile it talks about incorporating your customer into your sprints. That might just be a misunderstanding of “customer” on my end. The backlog is sufficient in our case. Thanks for helping.