Skip to main content

Peter's 5 Question Agility Assessment

What does it mean to have an “Agile Mindset?” This assessment is intended to help you reflect on your level of agility. You can download the questionnaire and give assess yourself, your team, your organization, or even your customers!

Last week, I argued that the Agile Manifesto defines the Agile mindest. If your attitudes and values are aligned with the Manifesto, then you can claim to have the Agile mindset. This post is the short form: the conclusions without the reasoning, plus the questionnaire. For more explanation on why I chosen these questions, see Five Simple Questions To Determine If You Have the Agile Mindset.

You can download the questionnaire in PDF format.

The Manifesto for Agile doing what we do

We are uncovering better ways of doing what we do, by doing it and helping others to do the same. Through this work, we have come to value:

    Individuals and interactions over processes and tools
    Customer visible value over comprehensive documentation
    Customer collaboration over contract negotiation
    Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.
– The Agile Manifesto, www.agilemanifesto.org, as paraphrased by Peter Stevens

What is the Agile Mindset?

Someone who has the Agile mindset is in alignment with the first sentence of the Agile Manifesto: The Agile Mindset is a learning mindset.

Someone with an Agile mindset knows what they do, besides making money! What value do you bring value to those whom you value? Someone with an Agile mindset is uncovering betters ways to do what they do, both by doing it, and by helping others to do the same. This is about advancing the state of your art, having time to improve your skills and technology, and learning and sharing beyond your own four walls.

Someone with an Agile mindset knows what they value. The have reflected on the Values and Principles of the Agile Manifesto and found their own beliefs to be largely in harmony with those expressed in the Manifesto. Values are a guide to decision making, so their decisions will be aligned with the Agile Manifesto as well. Perhaps they have additional values. Perhaps they have reason to disagree with one or more of the values in their context. The less relevant you consider the Agile values, the more you should question yourself on whether you really have the mindset!

Finally someone with an Agile mindset knows why they value what they value. Values are not to be blindly followed. You may value other things beyond the 4 values expressed in the Agile Manifesto.

Peter's 5 Questions

  1. What do you do for those whom you value? The answer must contain a verb and is not “making money
  2. Are you uncovering better ways of doing what you do, by doing it?
  3. Are you uncovering better ways of doing what you do, by helping others to do the same?
  4. Have you reflected on the values and principles of the Agile Manifesto and what they mean for you?
  5. Can you concisely explain your values and why you value them?

Use of this Assessment

Peter's 5 Question Agile Assessment should inspire you to reflect on your level of Agility. It is not about any particular practice nor does not give you a score. It intended to help you reflect on your values and principles, and to give you something to think about on the road to becoming Agile.

Downloading and Using the Assessment

You can download and use Peter's 5 Question Assessment. It is licensed under a Creative Commons Share Alike Attribution 4.0 License.

Comments

Dave McNulla said…
I am always surprised at how many people in scrum couldn't even remember the values of agile.
Peter said…
Hi Dave,

Most people do know the values. Certainly the Scrum Trainers do. My point is that most people overlook the first sentence. "We are uncovering better ways... by doing it and helping others to do the same."

I believe we in the Agile community need to pay much more attention to this point, because this is both what we are about and what we have in common with many other frameworks that don't identify themselves as "Agile."

Cheers,
Peter

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …