Self Assessment Tool for Transitioning to Agile

Over on agileconnection, a user asked about a self-assessment tool for measuring agile maturity. That's not exactly the right question, because agile transition is a journey, not a destination. But, I can understand why he asked the question. I tried to be helpful. I supplied a set of questions to ask. Maybe you can go over there and add more to my list.

I still think the best question is this:

What benefit will you gain from learning this answer?

In any case, here are some questions I supplied to get the questioner (or you) started:

  1. If you are doing iterations, are they four weeks or less? The answer should be yes. Many of us like one or two week iterations. Why? Because you get feedback more often rather than less often. And, you get to see working software.
  2. Do you have demos at the end of each and every iteration? The answer should be yes. Why? To get the feedback from the customer/Product Owner.
  3. Do you get every item in the backlog to done at the end of every iteration? The answer should be yes. For many teams on their journey, the answer is “not yet.” This does not make you bad, it makes you “on your journey.” You want to discover why.
  4. Do you perform retrospectives at the end of each iteration to learn and inspect/adapt to improve your team's agile process?
  5. Do you look at your work in process and monitor that?
  6. If you use iterations, do you measure your velocity with a burn up chart and make sure it does not look like a hockey stick?
  7. If you are using kanban, do you measure your cycle time? Are you happy with your cycle time? (Did I just use a word that did not make sense to you 🙂
  8. Do you measure cumulative flow? (You want to make sure you do not have a lot of work in progress. It does not matter if you use iterations or kanban. This Matters to a team. It matters a lot.)

Gentle readers, do you have feedback for me on these questions?

I wrote Agile is Not for Everyone because I don't believe in these assessments for agile maturity. However, just because I don't believe in them is not going to make them go away. Maybe I can be more helpful.

15 thoughts on “Self Assessment Tool for Transitioning to Agile”

  1. Michael Abugow

    I would also add:

    1) Are your teams empowered to make the right decision?
    2) Do your managers know when to get out of the way of the team?

  2. I’ve seen these anti-patterns too many times to not ask these questions during the same situation you highlight above.

  3. Pingback: Becoming Agile and Lean | Ben Linders

  4. Great list of questions, thanks Johanna!

    A while ago I wrote a blog post about becoming agile and lean, in which I refer to several self assessments tools and readiness checks. I’ve added a link to this blog post.

    Readiness checks don’t tell you if you are ready for Agile or Lean, my opinion is that everybody is ready. It is a matter of knowing where you are now (that’s where self assessments and readiness checks can help), and daring to take a next small step in continuous improvement.

    1. Ben, I am so glad you included your link in your reply. Thank you for including my post in your article.

      Yes, we agree it is a journey! And, you do have to know why you are doing this. If you don’t know why, you don’t know what path to take.

  5. Pingback: Great Resources | Upskilling 4 Testers

      1. There is a positive correlation between trust and performance of agile teams what factors according to you affects trust in agile teams ?

        1. I have not measured the “correlation” of trust and team performance. In my experience (empirical data), I have seen trust be a key factor in any team’s performance. If team members trust each other, they will work on getting features across the board. If they don’t trust each other, they work for themselves, destroying teamwork.

          I recommend you read Hackman’s article and book. Start here: I found it quite enlightening.

          Trust does not occur without a great environment. Leadership creates the environment, which allows the team to work together and build trust.

          1. Thanks Johanna , I really appreciate your good work you are doing for agile fraternity. I will definitely go through this article and get back to you soon

  6. Pingback: Becoming Agile and Lean

  7. Thanks Johanna,

    Good useful article.

    I also ask teams, do they have team capacity mechanism in place to meet their sprint planned velocity. Most of the time, team commit the velocity without considering their available capacity as a whole(i.e. who all are available throughout the sprint and what % of time they are available, any planned vacations, holidays during sprint etc.).

    There should right amount of supply (Capacity) to meet the right amount of Demand (Velocity) per sprint. Matured teams use it to become more predicable and high performance

    1. Aniket, thanks. I like your ideas of capacity and demand. I’ve also been working with teams to measure their cycle time. In my experience (which is not anyone else’s!), when teams count stories and measure the rough time it takes to complete a story, they are more likely to create stories of roughly the same size. And, they realize they can complete stories in about the same time. Assuming most of the team is available.

      I’ve been asking teams to swarm and mob much more often, which also evens out their throughput.

Leave a Comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: