Why does Agile focus on values and principles rather than a prescribed set of steps?

TL;DR

Agile focuses on values and principles instead of fixed steps because software development is complex work with unpredictable challenges, so no set process can guarantee success. Teams must adapt, experiment, and continuously learn, using values like commitment, courage, focus, openness, and respect as guides. Development managers should foster a culture that supports flexibility and ongoing improvement rather than relying on rigid procedures.

23 January 2023
Written by Martin Hinshelwood
5 minute read
Subscribe

Agile exists to address the idea that no predetermined set of steps will lead to a predefined outcome. The problem has never been solved, nor has the solution ever been created, so you don’t know what you don’t know. No formula is going to guarantee a desired outcome.

Why does Agile focus on values and principles rather than a prescribed set of steps?

Complicated versus Complex work.

In complicated work, such as civil engineering, we can apply a set of best practices and be relatively certain that a desired outcome will be achieved. We need a bridge, know the best way to build that bridge, and we bring experienced bridge builders in to build a new one.

Problem solved. There may be slight differences in variables, such as cost, time, and materials, but they will most likely be within a tolerance we can accept and plan for.

Even though the work is hard and complicated, a team of people has performed the work many times before. It can solve every problem and develop every solution with almost 100% certainty before you even start the project.

So, in complicated work, it is hard if you don’t have the knowledge but it becomes very simple and straightforward when you do possess that knowledge and skill.

Complex work lives in the domain of problems that have never been solved before, products and services and solutions that have never existed before, and deep uncertainty about how to do the work even when you have a team of deeply experienced, skilled, and knowledgeable people.

A team of subject matter experts, in possession of all the knowledge and skills available, are still not guaranteed to solve the problem or create the solution you want. They won’t know the answer, the process, or have a predefined set of steps until they have created the solution or built the product.

Only then will they know, with certainty, how to do the work.

That is complex work.

Continuous Complexity.

As we make advances in the work we do and understand more about some of the work, we can shift work that was in a complex environment into a complicated environment. We had to apply significant effort (energy) in order to achieve this. 

We can take what we have done and create automation using everything we learned in the complex work to replicate success for the work that is no longer complex. This automation, or production line, allows you to create a repeatable and consistent outcome. In software that the production line may take the form of an automated build and deployment.

We never solve the exact same problem again in software engineering and other creative work.

The code that solved the previous problem won’t work on the next one; we design a new solution and must write code or develop a creative solution that has never been tried or written before.

It is continuous complex work.

In this scenario, we can use the framework and empirical process control as a guide to creating the solution or solving the complex problem, but we can’t create a production line for the complete work.

There are no best practices; there are only emergent practices.

We start with the best thing we can do right now, using what we have learned up until that point, but in a few hours, we may make a discovery or breakthrough that means we need to explore a whole new line of discovery or invent a whole new set of practices.

It’s a world of surprises.

Some of these are pleasant surprises that help us evolve, and others are nasty surprises where we discover that what we are doing isn’t working, nor will it work in the future. We must return to the drawing board and pursue a new line of reasoning, experimentation, and discovery.

Values and Principles

In this world, values guide how we do the work. A great example of that are scrum values.

  1. Commitment

  2. Courage

  3. Focus

  4. Openness

  5. Respect

These are our guardrails, and these are the behaviours, practices, and mindset that governs how we navigate volatility, uncertainty, complexity, and ambiguity.

We can’t use a prescribed set of steps because they don’t exist.

Agile and Scrum provide the tools and help develop the culture that allows a team or organization to adapt to any set of circumstances, both positive and negative.

A framework that allows an organization to frequently inspect what they are doing, adapt based on what they have learned, and use the process of discovery and experimentation to help them continuously improve. ​

About NKD Agility

Naked Agility is an #agile consultancy that specializes in #scrumtraining, #agilecoaching and #agileconsulting to help teams evolve, integrate, and continuously improve.

We recognize the positive impact that a happy AND inspired workforce can have on customer experience, and we actively help organizations to tap into the power of creative, collaborative, and high-performing teams that is unique to #agile and #scrum environments.

If you are interested in #agiletraining, visit https://nkdagility.com/training/

If you have identified the need for #agilecoaching and #agileconsulting, visit https://nkdagility.com/agile-consulting-coaching/

We would love to work with you.

#scrum #agile #scrumteam #agileprojectmanagement #agileproductdevelopment #projectmanagement #productdevelopment #agilecoach #agileconsultant #agiletraining #scrumtraining #scrumorg

Smart Classifications

Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.

Subscribe

What to read next

Video Product Development

Navigating Complexity: Why Agile Practices Are Essential for Modern Product Development

Explains how agile practices help teams manage complexity, adapt to change, and deliver value faster in modern product development, compared …

Watch video
Video Product Development

Why Agile Success Lies in Principles, Not Tools: A Shift in Focus

Agile success depends on core principles like adaptability and collaboration, not just tools or frameworks. Focusing on principles leads to …

Watch video
Video Product Development

If you could teach just one thing about Scrum, what would it be?

The most important aspect of Scrum is empiricism, using transparency, inspection, and adaptation to navigate complexity and drive effective …

Watch video
Video Product Development

Redefining Agile’s Core: Beyond Rituals and Procedures

Explores how Agile’s true value lies in delivering outcomes and adapting to change, not just following rituals or procedures, and highlights …

Watch video
Video Product Development Leadership

Unlocking Agile’s Core: Questioning to Create Value

Explores how questioning, continuous improvement, and team empowerment drive Agile success, helping organisations adapt quickly, spot …

Watch video
Article Scrum Product Development

Pragmatism crushes Dogma in the wild

Explores how practical use of Scrum fosters adaptability and resilience in teams, highlighting the value of flexibility over rigid rules in …

Read article