UNITED WAY STL ACADEMY
  • Courses
  • Log In
  • Join Free
  • Home
  • Courses
  • Scrum Essentials

Getting Started with Scrum

Curriculum

  • 2 Sections
  • 10 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • The Basics of Scrum
    4
    • 1.1
      The Bird’s-Eye Basics
      10 mins
    • 1.2
      The Feedback Feast
      10 mins
    • 1.3
      Agile Roots
      10 mins
    • 1.4
      The Five Scrum Values
      10 mins
  • The First Steps
    6
    • 2.1
      Getting Your Scrum On
      10 mins
    • 2.2
      The Power in the Product Owner
      10 mins
    • 2.3
      Why Product Owners Love Scrum
      10 mins
    • 2.4
      The Company Goal and Strategy: Part 1
      10 mins
    • 2.5
      The Scrum Master
      10 mins
    • 2.6
      Common Roles Outside Scrum
      10 mins

Agile Roots

Getting Started with Scrum

Agile Roots

🕐 12 min read
The Big Question

What makes agile approaches like Scrum so effective in environments where change is constant and customer needs evolve rapidly?

To truly understand Scrum, you need to explore the broader world of agile techniques. Scrum isn’t an island—it belongs to a family of approaches grounded in the core values and principles of agility.

💡 Did You Know?

The Agile Manifesto was created in 2001 by 17 software and project management experts during a ski retreat in Utah. Their goal was simple: uncover better ways of developing software and helping others do it, too.

Agile is a descriptor of approaches that align with the values of the Agile Manifesto and the 12 Agile Principles. Scrum is one agile approach.

Tip icon
TIP

For a thorough look at agile techniques, see Agile Project Management For Dummies, Third Edition, by Mark Layton, Steve Ostermiller, and Dean Kynaston (John Wiley & Sons, Inc.).

Three Pillars of Improvement

The empirical process control model sits securely on three pillars, which are common to agile techniques, including scrum:

  • Transparency
  • Inspection
  • Adaptation
Empirical Process Control

A model for managing work based on observation, experience, and experimentation, rather than rigid plans.

Transparency

One distinguishing feature of agile techniques, in general, and scrum, in particular, is transparency. When channels of communication are clear and accessible, information is radiated broadly. Everyone involved knows what’s been done, what’s being worked on, what’s left to work on, and any impediments blocking the way. Right from the start, you produce real results that are validated and approved or sent back for adjustments. Now, the lag time between the start date and usable results is days rather than months.

Transparency isn’t just about seeing results quickly. Everyone needs to look through the same lens. A framework (such as scrum) is shared, along with an agreed-on definition of done. Both observers and participants can see what’s being accomplished and interpret the results in a common language.

Why is it important for everyone on a Scrum team to share the same definition of “done” for their work?

Inspection

As you discover in the following chapters, goals and outcomes are broken into the smallest actionable chunks possible (product backlog items commonly captured as user stories). Goals are set within fixed-length iterations called sprints. As each item is accomplished, it’s inspected to make sure that it works and does what the customer wants.

These inspections are done by people closest to the job — those who do the work and those who represent the customer. This process eliminates the time lag required for an outside person to complete this task, and it also means that any adjustments can be made quickly because the required knowledge is at hand.

In a software development company using Scrum, team members and product owners review each increment at the end of every sprint, enabling immediate feedback and rapid course correction if the product isn’t meeting customer expectations.

Adaptation

If the inspection shows inaccuracies and/or inefficiencies — that is, if the feature or desired outcomes don’t work right — an adaptation needs to be made. The adaptation should be made as soon as possible and before moving to the next actionable item on the to-do list. In other words, when you move on, you know everything behind you is functioning properly.

Scrum allows inspections and adaptations to be accomplished immediately at the team and product or service levels through sprint reviews, sprint retrospectives, and the daily scrum.

How does rapid adaptation after inspection help teams avoid wasting effort on features or solutions that don’t work?

Want to go deeper? The science behind feedback loops in Scrum

Frequent feedback loops are a key to learning and improvement in complex systems. In Scrum, short iterations (sprints) and regular inspection points create opportunities for teams to learn quickly from their work and adapt before small issues become large problems. This empirical approach has roots in scientific method and lean manufacturing, where rapid cycles of hypothesis, experiment, and observation drive progress.

One Agile Manifesto

Scrum is a framework, not a by-the-numbers methodology. You still need to think and make choices. Part of the scrum framework’s benefit is that it is intentionally incomplete. It allows you to make the best decisions based on the reality in which you find yourself.

In 2001, 17 software and project experts agreed on the four values their experiments and approaches had in common. These values are known as the Manifesto for Agile Software Development (commonly referred to as the Agile Manifesto):

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

  • Individuals and interactions more than processes and tools
  • Working software more than comprehensive documentation
  • Customer collaboration more than contract negotiation
  • Responding to change more than following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Agile Manifesto © 2001: Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas

Even though the Agile Manifesto and principles were written by and for software experts, the values remain valid for whatever scrum project you embark upon. For example, the Global Positioning System (GPS) was designed by and for the military, but that doesn’t mean that you can’t benefit from it when you drive to a new part of town.

Tip icon
TIP

For more information on the Agile Manifesto and its authors, visit http://agilemanifesto.org.

Agile Manifesto

A foundational declaration of four values and twelve principles that define the Agile approach to software development.

❌ Common Misconception

Agile means having no plan and just improvising as you go.

✅ The Reality

Agile values responding to change over following a rigid plan, but it relies on structured frameworks (like Scrum) with clear roles, events, and artifacts to guide progress and adaptation.

Twelve Agile Principles

The Agile Manifesto’s authors also agreed on 12 Agile principles. You can use these principles to make sure your approach is true to agile values:

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for a shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. Face-to-face conversation is the most efficient and effective method of conveying information to and within a development team.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity — the art of maximizing the amount of work not done — is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, and then tunes and adjusts its behavior accordingly.

Which Agile principle do you think is most challenging for organizations to practice consistently, and why?

Remember icon
REMEMBER

The Agile principles aren’t just for software—they offer a mindset for delivering value and adapting to change in any project or industry.

  • You can name and describe the three pillars of improvement in agile frameworks.
  • You understand the four core values and twelve principles of the Agile Manifesto.
⏱ 5 minutes
Activity: Spot the Pillars

Read the scenario below and identify where the pillars of Transparency, Inspection, and Adaptation are applied:

  1. A team holds a daily meeting where everyone shares what they’re working on and any obstacles.
  2. At the end of each sprint, the team demonstrates completed work to stakeholders and asks for feedback.
  3. Based on the feedback, the team quickly updates their process for the next sprint.

Many organizations outside of software—including marketing, manufacturing, and education—use Agile principles to increase flexibility and deliver value faster.

Flashcard

What are the three pillars of improvement in Scrum?

Tap to reveal
Answer

Transparency, Inspection, and Adaptation.

Flashcard

What is the Agile Manifesto?

Tap to reveal
Answer

A set of four values and twelve principles that guide agile software development and project management.

Flashcard

What does “responding to change over following a plan” mean in Agile?

Tap to reveal
Answer

It means teams should adapt quickly as new information emerges, instead of rigidly sticking to initial plans.

Think about a time when you or your team had to quickly adapt to unexpected changes. How would applying the three pillars of Scrum—Transparency, Inspection, and Adaptation—have helped in that situation?

0 words Take your time — depth matters more than length
+50 XP

Which of the following is NOT one of the three pillars of improvement in agile techniques?

Review the “Three Pillars of Improvement” section above to find the answer.
Key Takeaway

Scrum’s foundation in Agile values, empirical process control, and the three pillars of transparency, inspection, and adaptation empowers teams to deliver real value in rapidly changing environments.

Key Takeaway

The Agile Manifesto’s four values and twelve principles remain relevant and powerful, guiding teams to prioritize people, collaboration, working solutions, and adaptability over rigid processes.

“While there is value in the items on the right, we value the items on the left more.”

SHIFT

The Shift

  • Scrum is built on agile values and the principles of empirical process control.
  • The three pillars—transparency, inspection, and adaptation—drive continuous improvement and rapid response to change.
  • The Agile Manifesto’s values and principles provide a flexible, human-centered foundation for project success in any domain.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

The Feedback Feast
Prev
The Five Scrum Values
Next

© 2026 United Way STL Academy | Powered by Sejal Learning Systems.

Modal title

Main Content