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

The Fall of Waterfall

Scrum for Any Industry

The Fall of Waterfall

🕐 12 min read
The Big Question

Can Scrum—a framework born in software—really transform how we build physical products in industries like manufacturing and consumer electronics?

In today’s fast-moving world, product development is racing ahead—not just in software, but in every industry. How can teams keep up, adapt quickly, and deliver what customers want, especially when building tangible goods?

💡 Did You Know?

Apple, a company famous for its hardware, now releases next-generation products multiple times each year—something unimaginable in the old era of slow, linear development cycles.

Product development is occurring at accelerating speeds, and it’s not only the software sector that’s seeing fundamental shifts in what’s developed and how long it takes. Long-term manual manufacturing activities are changing, too. Development cycles in most industries are shorter and faster because of the time and cost savings accrued through technology. Companies such as Apple, whose products are certainly tangible, release next-generation, cutting-edge products multiple times a year.

Have you noticed any products from industries outside software that have started releasing new versions much more frequently?

Some argue that the scrum framework can’t be applied to physical products, saying, “We can’t be building the tenth floor when we realize that we need to make a change on the fifth floor!” Sometimes, they’re right.

❌ Common Misconception

Scrum can’t work for physical product development because you can’t change things after they’re built.

✅ The Reality

While some late changes are too costly, Scrum helps all teams—software or physical—make smarter decisions based on reality, not endless rework.

Why do you think people resist applying agile methods like Scrum to physical or manufacturing projects?

In real-world manufacturing, teams often use Scrum to manage design phases, prototyping, and even production—even if not every aspect is as flexible as in software.

People make objections like that one all the time in software development as well. A change in design may be so costly that it can’t be realistically implemented, and other options must be considered, including moving forward with no change. Maybe a different database would be preferred, but it’s too costly, so the product owner decides to nix the idea and keep going as is.

Scrum is about exposing reality and making good decisions based on empirical evidence, not about swapping out requirements at a customer’s every whim. Whether the industry is developing software, or manufacturing planes, trains, or automobiles, the scrum foundation applies: organizing a scrum team with appropriate roles, holding frequent inspection and adaptation points, and forcing decisions to happen at the last responsible moment (that is, planning at different levels of detail for the right things at the right time).

Scrum Team

A small, cross-functional group with clear roles (Product Owner, Scrum Master, Developers) responsible for delivering value through iterative work.

Last Responsible Moment

The latest point in time when a decision can be made without negatively affecting the outcome, enabling flexibility and better-informed choices.

Remember icon
REMEMBER

The product owner filters out the business prioritization noise from all the stakeholders so that the developers spend their time on only the highest-priority requirements. Product owners and developers work as a team to implement the solutions to problems presented by the product owner. When everyone works toward the same goals, finger-pointing is reduced, and accountability is shared.

Major car manufacturers now adopt agile teams to shorten design cycles, allowing for more customer feedback and better adaptation to market trends—even when building physical vehicles.

Want to go deeper? The science behind shorter development cycles

Technological advances like rapid prototyping, 3D printing, and sophisticated supply chain management have enabled industries outside of software to reduce cycle times. This makes iterative frameworks like Scrum increasingly viable, even in manufacturing and hardware design.

Engaged customers are more satisfied customers who end up getting what they want. With scrum, feedback loops are regular, consistent, and as frequent as possible, so customers get what they want at the cost they’re willing to pay for it, which keeps customers involved and developers on track. Impediments can be identified and resolved early, and accountability is taken on by those who do the work and those who make decisions, including customers.

How do regular feedback loops with customers help avoid costly late-stage changes?

⏱ 5 minutes
Activity: Spot the Impediments

Think of a recent project (work, school, or personal) where changes were needed late in the process. What obstacles prevented those changes from happening earlier?

  1. List at least three obstacles that slowed decision-making or blocked changes.
  2. For each, suggest how an agile approach like Scrum could have helped surface and address the obstacle sooner.

Scrum is about exposing reality and making good decisions based on empirical evidence, not about swapping out requirements at a customer’s every whim.

  • Product development cycles are accelerating across all industries.
  • Scrum can help teams—even in manufacturing—respond to change and deliver value, when applied thoughtfully.

Think about a time when a project you were involved in faced a costly change late in the process. How could frequent inspection, adaptation, and engaging the right stakeholders earlier have changed the outcome?

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

What is the primary role of the Product Owner in Scrum?

Tap to reveal
Answer

The Product Owner prioritizes requirements by filtering business input, ensuring the team focuses on the highest-value work.

Flashcard

What does “last responsible moment” mean in Scrum?

Tap to reveal
Answer

It means making decisions only when they must be made, keeping options open and incorporating the latest information.

Flashcard

How does Scrum help reduce finger-pointing on teams?

Tap to reveal
Answer

By fostering shared accountability and clear roles, Scrum encourages teams to work toward common goals rather than blaming individuals.

Key Takeaway

Scrum’s iterative, evidence-driven approach can accelerate development and improve outcomes for both software and physical products—even in industries traditionally bound by rigid processes.

Key Takeaway

Frequent feedback loops and late-stage decision making (“last responsible moment”) help teams adapt quickly, minimize waste, and deliver higher customer satisfaction.

SHIFT

The Shift

  • Scrum principles can be adapted to accelerate development cycles even for physical products, not just software.
  • Making decisions at the last responsible moment allows teams to respond to real conditions and data, not assumptions.
  • Shared accountability and regular customer engagement drive better outcomes and reduce costly mistakes.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Scrum Applications in Software
Prev
Construction
Next

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

Modal title

Main Content