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

Embracing Change

Scrum for Any Industry

Embracing Change

🕐 12 min read
The Big Question

Why do organizations resist change, and how can Scrum help teams move beyond old habits to achieve real progress?

Although scrum’s effectiveness and speed make it a natural fit in many situations, hierarchically structured organizations make it difficult. Incorporating new ideas and breaking away from old habits can be challenging. Some corporate cultures are open to change; others have more difficulty. It’s human nature to find comfort in habits, and it takes effort and energy to break them.

💡 Did You Know?

Transparency and regular feedback loops in Scrum don’t just improve products—they also build trust between stakeholders and teams, accelerating change across entire organizations.

To get people in the organization to embrace the change, you must reveal the value of the change to them. When the parties involved clearly understand what’s in it for them, they accept the changes more readily. As the parties begin to experience the benefits of early release and adaptation, the conversion will go more quickly.

To help ease your organization’s transition to scrum, we look at some specific issues in the following sections.

What habits or structures in your current organization might make embracing change difficult?

Developer challenges

In traditional, top-down management cultures, implementing scrum while maintaining the status quo won’t work. The developers can be frustrated with double work if they’re required to maintain traditional processes on top of implementing scrum. Managers can get off kilter moving forward, developing products that aren’t planned upfront and don’t provide the reams of reports and analysis they’re used to.

With scrum, organizations can ease into inspection and adaptation one sprint at a time. Getting managers to participate appropriately (as stakeholders) in the first sprint reviews may be difficult. Equally challenging is getting people to see working software as the new benchmark of success.

❌ Common Misconception

Success in software development is measured by reports, documentation, and detailed analysis delivered to management.

✅ The Reality

With Scrum, the benchmark of success is working, usable software delivered incrementally after each sprint.

Scrum is a different way of working for the team and all its stakeholders and influencers. If the organization perseveres and allows scrum time for benefits to manifest, it sees immediate, practical, and quality results. The organization discovers that it has something real to work with after each sprint and that progress accumulates logically and rapidly. Time spent writing reports and managing status has been replaced by time spent creating real, usable products. The status is clear because it’s real.

How might focusing on working software instead of reports change the way your team collaborates?

Business alignment with technology

Traditionally, the business side of an organization and software engineering are separate, and often, they’re at odds. For decades, these groups have operated as silos within the same organization:

  • The business serves the market and the shareholders and is under extreme pressure to deliver value quickly and adapt to a constantly changing marketplace.
  • The technologists want sustainable architecture and foundations with as little technical debt accumulation as possible.
Product Owner

The Scrum team member who represents the business, prioritizing work and bridging the gap between stakeholders and developers.

Scrum brings these two sides together. A representative from the business (product owner) and developers are involved together, providing feedback throughout the sprint. At the end of the sprint, the whole team collaborates with business stakeholders aligning the entire product team. You’ll never find a more beautiful alignment and facilitation of collaboration and joint ownership. Thanks to scrum, the right people are making the right decisions about the right things at the right times. Finger-pointing is no longer relevant. Progress is exposed at all times to all parties. Inspection and adaptation points exist along the way. Self-organization and self-management mean that everyone is in it together.

Scrum’s emphasis on regular sprint reviews led one organization to involve actual users in every sprint review, resulting in critical feedback and improved trust across the team and stakeholders.

“The organization discovers that it has something real to work with after each sprint and that progress accumulates logically and rapidly.”

  • Scrum replaces traditional reporting with working software as the measure of progress.
  • Frequent alignment between business and technology fosters true collaboration and joint ownership.

REAL-WORLD CHANGE

Not long ago, we provided scrum training for one of our software clients. The client was working on a research and development product involving new technology and was given a deadline by senior management to complete a comprehensive range of features.

The team initially came up with proof of concept of features and requirements fairly quickly, which won buy-in from management to proceed with the full-scale development. However, the product backlog was vague, and the team spent unbudgeted months developing a demo version for management.

The development process was slow and fraught with technical surprises. The team missed both the first release date and the next several rescheduled release dates. At this point, we trained the team and implemented the scrum framework.

At first, the entire product team held on to traditional practices (upfront design, fixed scope and schedules, and renaming waterfall artifacts and events as scrum). But it pushed ahead, held consistent sprint reviews with stakeholders, and survived a series of tough, uncomfortable conversations about missed deadlines and how the aspects of scrum could help resolve these challenges.

The transparency in scrum began to shine through after a few sprint reviews, clarification of roles (especially getting a dedicated and fully trained product owner), and the removal of some impediments. Walls were broken down between the scrum team, stakeholders, and customers (actual users were involved in every sprint review); communication improved; and the product development was replanned with a proper product goal, roadmap, and product backlog. A release schedule was re-created based on the team’s new velocity and product backlog estimates. Long story short, from that point, it took months, not years, to release the minimum viable product (MVP). The new product development plan was based on priority, customer feedback, and empirical data (such as velocity).

During initial sprint reviews, the team identified a key stakeholder (a customer who would be using the product) who hadn’t been attending the sprint reviews. She was invited, and her involvement provided crucial feedback on the product. As the other stakeholders observed the scrum team’s willingness and speed in inspecting and adapting, trust skyrocketed, and ownership and collaboration (including stakeholders) improved amazingly.

  • In the end, the product much more accurately reflected what the customer wanted.
  • Extra features were removed from the product backlog (something that a stakeholder and the product owner decided, not the developers).
  • An MVP was released in full working order.

The stakeholders were fully engaged and involved with training users on the software. In fact, stakeholders ended up collaborating with the product owner on every aspect of the rollout.

When was the last time your team adjusted plans based on real feedback instead of sticking to the original schedule?

Upfront engineering

The propensity of development managers, project managers, and developers to plan everything has deep roots:

  • Most schools still teach upfront engineering. Fresh out of class, engineers plan first and develop second.
  • Waterfall enforces the “plan all and then develop all” mindset. This process is built around completing one phase, such as designing, before moving to the next, such as developing. In waterfall, upfront engineering is part of the foundation on which everything else rests.
Waterfall Model

A traditional project management approach where each phase (requirements, design, development, testing) is completed before the next begins, with little room for adaptation.

Want to go deeper? The science behind breaking habits in organizations

Research in organizational behavior shows that change is often resisted not just due to process, but because of psychological safety—people fear uncertainty and losing their established roles. Scrum’s transparency and frequent feedback help reduce anxiety by making progress and outcomes visible, building trust and willingness to adapt.

⏱ 5 minutes
Activity: Identify Your Change Barriers

Think about your organization or a team you’ve worked on. What are the biggest habits or structures that resist change?

  1. List three organizational habits or processes that feel resistant to change.
  2. For each, write down one way Scrum could help shift that habit.
  3. Discuss with a peer or reflect on which habit would be easiest and hardest to shift—and why.

What’s one specific change you wish your organization would make—and what benefit could you highlight to help others embrace it?

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

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

Tap to reveal
Answer

The Product Owner represents the business, prioritizes the product backlog, and ensures the team delivers value to stakeholders.

Flashcard

What does Scrum use as the main benchmark of progress?

Tap to reveal
Answer

Scrum measures progress by delivering working, usable software after each sprint, not by reports or documentation.

Flashcard

How does Scrum help break down silos between business and technology teams?

Tap to reveal
Answer

Scrum fosters continuous feedback, shared sprint reviews, and joint ownership, aligning business and development through collaboration.

+50 XP

According to Scrum, what is the most accurate indicator of progress on a project?

Review the “Developer challenges” and “Business alignment with technology” sections above to find the answer.
Key Takeaway

Scrum succeeds in driving organizational change by making progress visible, aligning business and technology, and fostering continuous inspection and adaptation.

Key Takeaway

Embracing Scrum means shifting from comfort with established habits to a focus on real, working outcomes and collaborative improvement.

What practical steps can you take to reveal the value of change to others in your organization?

0 words
SHIFT

The Shift

  • Scrum accelerates change by making progress visible and engaging everyone in adaptation.
  • Real collaboration between business and technology leads to better products and happier teams.
  • Embracing change means letting go of outdated habits and focusing on delivering real, usable outcomes.
End of lesson Ready for the next lesson?
Continue to next lesson  →

Leave a Reply Cancel reply

Software Flexibility and Refactoring
Prev
Scrum Applications in Software
Next

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

Modal title

Main Content