“Over’s” Usefulness in Decision Making

This content is syndicated from Jim Highsmith .com by Jim Highsmith. To view the original post in full, click here.

The Agile Manifesto was written in a very deliberate style, for example, “Individuals and interactions over process and tools.” The word “over” was carefully chosen and establishes a key agile principle that many things in our world are too complex for black or white answers so we need to differentiate between what is critical and what is important.

To continue with our example, it’s not that process and tools are unimportant—there are a myriad of tools that increase the productivity of agile teams—but that in the final analysis, people are more important. Think of it this way. If you were a project manager, would you rather have the best tools and processes, but mediocre people; or talented people and so-so tools and processes? Obviously, we would pick the latter. However, that selection doesn’t make tools or process unimportant. How would you like to run a great team that had no tools? It’s just that sometimes we have to make hard decisions and having a series of “over” value statements can help.

Software development reflects the business world today—complex, uncertain, fast, risky, volatile. These traits dictate that development efforts have to be adaptable, customized, and evolutionary. There isn’t a single correct practice or method for every project. However, this doesn’t mean that anything goes—that there aren’t preferences. While we have to be adaptable, we also have to make decisions, and ultimately decisions reflect higher and lower priorities and we need to give people guidelines for their decisions.

What if the Agile Manifesto had been written?

“We believe the following are the most important:

  • Individuals and interactions

  • Working software

  • Customer collaboration

  • Responding to change”

While these would have established importance, they would not have been as effective as decision making guidelines. Even with using the term “over,” people still misinterpret the Manifesto as singularly focusing on the first parts of the statements.

In a world of complexity, this use of “over” statements can be beneficial in decision making because this type of statement does two things: (1) it clearly establishes what has highest priority, and (2) it establishes that the second part of the statement identifies something important also, just not the most important. The very fact that “processes and tools” resides in the Manifesto statement establishes them as important.

Another example of using over statements would be in evaluating project performance–what’s more important, predictability or adaptability? Write the statement one way “adaptability over predictability” provides us one guideline, while reversing them shows another. However, by including both we also establish that both are important and need to be considered in our decision making.

One of the most difficult things team members, managers, executives—everyone really—do is make decisions. Guidelines, some criteria for making decisions, are very valuable. But for the most part they can’t be black or white—they can’t be statements like “in all cases this is the most important.” There needs to be nuance that allows for complexity, uncertainty, etc. Using “over” statements as guidelines is one way to improve your team and organization’s decision making.


Leave a Reply

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

five × one =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”



To explore how we can help you, please get in touch