Scrum vs. Agile.

Defining Agile and Scrum

So you’re interested in Scrum? Maybe the topic came up during lunch. Or you learned about it at a conference. But then you also hear people use the term Agile, and they seem related but different. You don’t feel confident entering the conversation because you don’t know when to use which word.

This post will lay out the difference between Scrum and Agile and throw in a couple of related terms like Kanban and Lean. Afterward, you should feel comfortable jumping into the discussion and maybe digging deeper to learn more.

If you’re practicing Scrum, you’re working in an Agile way.

Agile

When people say “agile,” they usually refer to it as a mindset. Sometimes they may be referring to the movement across industries to adopt the principles of Agile, but then they’ll likely say, “agile movement.” 

Let’s take a quick look at the history of agile for some context.

The Agile Manifesto

Many agile ideas were birthed out of the software industry in the 1990s. The waterfall approach was the dominant project management perspective, and it depended on meticulous pre-planning to set the schedule, scope, and cost before proceeding. The manufacturing and construction industries significantly influenced the waterfall approach, but it needed to adapt to work for developing software.

The challenge was that the software development environment was unstable. The technology was rapidly improving, changing both the constraints on a project and what was even considered possible. A new methodology was needed to allow for more flexible and responsive software development. Instead of avoiding or mitigating change, they needed to embrace it.

Enter the Manifesto for Agile Software Development in 2001. It’s the Agile movement’s founding document and thus an excellent place to start understanding what Agile is all about. It’s composed of four values and 12 principles.

It describes what will be true when you’re following Agile. It doesn’t nail down the specifics of how you will do it.

Instead of avoiding or mitigating change, they needed to embrace it.

Take a minute and read through the manifesto. Even if you include all the principles, it’s only 262 words long. The manifesto itself was written to address the software industry 20 years ago though it still has meaningful applications for us today. It served as an impetus for change that has grown into the agile movement.

Defining Agile

ag·ile
/ˈajəl/
adjective
Able to move quickly and easily.

This is the standard definition for agile from the Oxford dictionary. Agile as a mindset includes values and principles that allow a team to move quickly and adjust at speed and scale.

A few core concepts of Agile:

• A focus on people, conversations, and collaboration.
• Flexibility, iteration, and adaptation.
• Regularly delivering value to customers.
• Trust and empowerment within the team.

Built from values and principles, Agile is a broad umbrella for a new way of working. It describes what will be true when you’re following Agile, and it doesn’t nail down the specifics of how you will do it.

Scrum

Interestingly Scrum’s origin predates Agile’s. Scrum was initially used as a term related to project management in 1986 by Hirotaka Takeuchi and Ikujiro Nonaka in their paper “New New Product Development Game” In the Harvard Business Review. The first recorded Scrum project came a little later in 1993 from Jeff Sutherland.

Scrum is a framework for how to organize people and work in an agile way. Essential to Scrum are the three pillars of empiricism:

• Transparency. How does this make things more visible?
• Inspection. Where does this create space to evaluate?
• Adaptation. When does this encourage growth?

Understanding these pillars and the five values of Scrum will provide a foundation that will guide you in what to do and why to do it.

While also based on principles and values, it is more explicit in what things to do. If you want more specifics on Scrum, check out the rest of my What is Scrum? Guide.

Scrum and Agile as partners

Thankfully we don’t need to choose between Agile or Scrum; they work together. Agile is more of a mindset guiding how we can work, and Scrum is a specific expression of that mindset. If you’re practicing Scrum, you’re working in an Agile way. 

People often first discover Scrum, begin implementing it, and then realize there’s a lot more to being Agile. It’s helpful to understand the difference because there may be other Agile practices that fit your needs better than Scrum.

How to choose what’s right for your team?

If you’re not currently using any agile approaches and are looking to try it out, I suggest starting with Kanban. It’s the simplest and doesn’t require a change to the structure of your team, and it will likely help you identify areas where agile approaches can help you. Kanban is also great if you have a process with many distinct steps.

Scrum and lean are both excellent approaches to use on a given team. While Nexus and SAFe are helpful when you want to scale to a larger organization.

Hopefully, this post provided some context to some of the Agile-related terms and practices you hear mentioned and provided paths for you to continue learning and growing.

If you want to learn more about Scrum in general, check out my What is Scrum? A Guide for Everyday People to Learn Scrum. If you have more questions, please feel free to reach out on LinkedIn.

Still not sure about your next step with Scrum? I offer a couple of free coaching sessions each month. You can signup for a free 30-minute coaching session, and we can work together to identify a good next step for you.