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

Scrum for Any Industry

Curriculum

  • 4 Sections
  • 15 Lessons
  • Lifetime
Expand all sectionsCollapse all sections
  • Software Development
    4
    • 1.1
      Scrum and Software Development: A Natural Fit
      10 mins
    • 1.2
      Software Flexibility and Refactoring
      10 mins
    • 1.3
      Embracing Change
      10 mins
    • 1.4
      Scrum Applications in Software
      10 mins
  • Tangible Goods Production
    5
    • 2.1
      The Fall of Waterfall
      10 mins
    • 2.2
      Construction
      10 mins
    • 2.3
      Scrum in Home Building
      10 mins
    • 2.4
      Manufacturing
      10 mins
    • 2.5
      Hardware Development
      10 mins
  • Services
    4
    • 3.1
      Health Care and Scrum
      10 mins
    • 3.2
      A Worldwide Pandemic
      10 mins
    • 3.3
      Education and Scrum
      10 mins
    • 3.4
      Military and Law Enforcement
      10 mins
  • Publishing: A Shifting Landscape
    2
    • 4.1
      A Changing Landscape in Publishing
      10 mins
    • 4.2
      News Media and Scrum
      10 mins

Scrum and Software Development: A Natural Fit

Scrum For Any Industry

Scrum and Software Development: A Natural Fit

🕐 12 min read
The Big Question

Why has scrum become the go-to framework for creative and complex software development, and how does it overcome the shortcomings of traditional project management?

Imagine a world where brilliant ideas can be brought to life rapidly, where change is embraced—and where feedback, learning, and improvement are built into the very heartbeat of your work. This is the world scrum enables, especially in the creative, ever-evolving field of software development.

Software development is creative in nature. The sky isn’t even the limit, as ideas, concepts, and reality go way beyond that now. Necessarily, the design solutions employed often are as creative as the products they serve.

Given its empirical nature, scrum fits this environment perfectly. Scrum doesn’t tell you how to do anything. It simply lets you see clearly (that is, exposes) what you’re doing and assess from there.

A huge variety of languages, tools, methods, and platforms exist to solve these complex problems. Scrum doesn’t tell you which ones to use. Rather, this framework lets teams self-manage to decide which ways are best for their circumstances. Scrum does this through unfettered transparency, frequent inspection, and immediate adaptation.

How do you think transparency, inspection, and adaptation can influence the outcome of a software development project?

The very nature of scrum allows you to find solutions every day, in every sprint, and with every release. Both the product and the process are nurtured for creativity and excellence.

💡 Did You Know?

Scrum’s roots are in software, but its core principles—transparency, inspection, and adaptation—can be applied to a wide range of industries, from marketing to manufacturing.

Traditional project management methods and frameworks are predicated on accurately predicting the future. They’re linear and sequential. They act as waterfall. (You can read about waterfall approaches in Agile Project Management For Dummies, Third Edition, by Mark C. Layton, Steven J. Ostermiller, and Dean Kynaston [published by John Wiley & Sons, Inc.].) What’s important to understand is that technology and design needs have far outgrown this change-averse framework.

Waterfall Project Management

A traditional, linear approach to project management where each phase (such as requirements, design, development, and testing) must be completed before the next begins, making change difficult once the process is underway.

Waterfall project management entails progressively maturing a set package of requirements in different stages. One stage is completed before moving on to the next, such as designing all requirements for the entire product before doing any development and completing all development work before doing comprehensive testing, which is left to the end. With scrum, these phases are cycled repeatedly throughout product development so that a continuous circle of design, development, testing, integration, and feedback is achieved each day, sprint, and release.

❌ Common Misconception

Testing should be left until the end of the software development cycle, after all features have been built.

✅ The Reality

Scrum encourages frequent, ongoing testing throughout development, enabling teams to adapt based on real feedback and catch issues early.

What challenges might arise when testing is only performed at the end of a project?

As products became more complex, the natural boundaries of waterfall became abundantly clear. Multiple phases and long delays existed before coding even began. Early performance was no indicator of later performance because each phase’s tasks were fundamentally different. Code testing was loaded toward the end of development when the team had the least amount of time or money. Customers didn’t interact with the product until it was too late to incorporate their feedback. Product development was delayed or never completed, and often, they came up short.

The very system [waterfall] he’s mistakenly credited with inventing is the same system he warned us about.

Scrum emerged from the need to find better ways to build software. Keep in mind, however, that the scrum framework can be applied to any product development in which you can encapsulate the work and prioritize an item against other items.

Scrum

An agile framework that enables teams to self-manage, prioritize work, and adapt quickly through transparency, frequent inspection, and iterative development cycles called sprints.

WINSTON ROYCE HAD IT RIGHT

In a strange quirk of history, the man mistakenly attributed with introducing the waterfall framework to large software projects emphasized the basic agile and scrum principles: inspect and adapt.

Winston Royce was a computer scientist and a director of the Lockheed Software Technology Center who published a paper titled “Managing the Development of Large Software Systems.” He described several methodologies, including waterfall and an early iteration of agile, as shown in this figure.

Schematic illustration of the game-development process with scrum.
Royce’s paper compared traditional waterfall with iterative development—an idea at the heart of scrum.

Royce clearly warned about the pitfalls later to be endured with waterfall. Strangely, the very system he’s mistakenly credited with inventing is the same system he warned us about. He wrote:

“The testing phase which occurs at the end of the development cycle is the first event for which timing, storage, input/output transfers, etc., are experienced as distinguished from analyzed … . Yet if these phenomena fail to satisfy the various external constraints, then invariably a major redesign is required. A simple octal patch or redo of some isolated code will not fix these kinds of difficulties. The required design changes are likely to be so disruptive that the software requirements upon which the design is based and which provides the rationale for everything are violated.”

Royce said leaving testing as a separate phase at the end was “risky and invited failure.” He suggested an iterative approach that used frequent testing and adapted based on the results. Every step linked back to the previous one.

Many leading technology companies, such as Google and Spotify, attribute their rapid innovation and ability to respond to change to frameworks like scrum. These organizations rely on iterative cycles, frequent feedback, and empowered teams to stay ahead in dynamic markets.

Can you think of a time when early feedback would have changed the outcome of a project you worked on or observed?

Want to go deeper? The science behind empirical process control in Scrum

Empirical process control is the foundation of scrum. Unlike defined process control (which relies on step-by-step plans and predictions), empirical control is based on observation, experimentation, and adaptation. This approach is crucial in environments where complexity and uncertainty make prediction nearly impossible—such as software development.

Scrum’s pillars—transparency, inspection, and adaptation—ensure that teams are always learning from real outcomes, not just theoretical plans. This continuous feedback loop allows for rapid improvements in both product and process.

⏱ 5 minutes
Activity: Waterfall vs. Scrum Mapping

Compare the phases of waterfall project management to scrum’s iterative cycles.

  1. List out the typical stages in traditional waterfall (requirements, design, development, testing, deployment).
  2. Now, map how these stages are handled in scrum within each sprint.
  3. Reflect: What advantages do you notice with scrum’s repeated cycles?

Practitioners often note that scrum empowers teams to respond to change without derailing entire projects, making it particularly effective for fast-paced industries where customer needs and technology evolve rapidly.

Think about a project or assignment where changes occurred late in the process. How might scrum’s emphasis on transparency, inspection, and adaptation have altered the outcome?

0 words Take your time — depth matters more than length
Flashcard

What are the three pillars of scrum?

Tap to reveal
Answer

Transparency, inspection, and adaptation.

Flashcard

Define waterfall project management.

Tap to reveal
Answer

A linear, sequential approach where each phase must be completed before moving to the next; changes are difficult once the process has started.

Flashcard

How does scrum handle changing requirements?

Tap to reveal
Answer

Scrum welcomes changing requirements by using short sprints, frequent feedback, and iterative improvements.

+50 XP

What is a key reason waterfall project management often fails with complex software products?

Review the section on waterfall project management above to find the answer.
  • Scrum enables teams to self-manage and adapt quickly through its core principles.
  • Traditional waterfall approaches struggle with the complexity and unpredictability of modern software development.
Key Takeaway

Scrum’s iterative, transparent, and adaptive approach makes it exceptionally well-suited for the creative and unpredictable nature of software development.

Key Takeaway

Unlike waterfall, scrum empowers teams to inspect results frequently and adapt quickly, reducing the risk of late project failures.

In your own words, explain how scrum addresses the limitations of traditional waterfall project management.

0 words
SHIFT

The Shift

  • Scrum fosters creativity and rapid adaptation by emphasizing transparency, inspection, and adaptation.
  • Traditional waterfall methods struggle with complexity and late-stage changes, while scrum thrives in unpredictable environments.
  • Empirical process control and iterative development help scrum teams deliver better products and respond to feedback quickly.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Software Flexibility and Refactoring
Next

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

Modal title

Main Content