What happens when an organization chooses to acknowledge—or ignore—the problems that Scrum brings to light?
Scrum is not a magic wand—it doesn’t make your problems disappear. Instead, it shines a light on the cracks in your processes, policies, and organizational structures, pushing teams and leaders to confront reality rather than hide from it.
Many organizations that adopt Scrum for the first time are surprised at how quickly it reveals issues that have been festering beneath the surface—sometimes for years.
Scrum won’t solve any problems for you, but it will expose them. Scrum will expose weaknesses and gaps in process, policies, organizational structures, skill sets, accountabilities, artifacts, meeting effectiveness, transparency, and myriad other topics. What you decide to do with what is exposed is up to you. Scrum provides an iterative inspection and adapts the framework for addressing items as they’re exposed.
Your organization is perfectly engineered to get the results you are getting today. If you want to get better results, you are going to have to change things. Scrum will show you what needs to change. Make those changes.
Think about a time when a process or policy at your workplace made it hard to deliver results. Would it have been helpful if everyone could see and talk about the issue openly?
At a large software company, the first few sprints using Scrum revealed bottlenecks in code review—something everyone sensed but no one had openly addressed. By escalating the issue, the team was able to work with leadership to adjust workloads and ultimately improve delivery speed.
Scrum’s cadence of regular events—such as Sprint Reviews and Retrospectives—forces teams to inspect their work and processes frequently. This transparency uncovers issues that might otherwise remain hidden in traditional project management, where status updates can mask deeper challenges.
Scrum teams should address what is exposed on their own when they have control over the exposed issue. When they don’t have control over the exposed issue, there should be a path for escalating those items to those in the organization who own the status quo and who can affect change to support scrum teams getting better and better at delivering customer value. An effective way to resolve escalated items exposed by scrum is to use the agile transition team discussed in the next module.
The cornerstone of Scrum where teams regularly examine their work and processes, then adjust to improve outcomes.
A defined route for raising issues beyond the team’s control to individuals or groups that have the power to make organizational changes.
How can your team ensure that issues revealed by Scrum are not just acknowledged, but actually acted upon?
Scrum will automatically fix all our organizational problems if we just follow the process.
Scrum exposes problems, but it’s up to you and your organization to take action and make the necessary changes.
Take a moment to identify issues Scrum has surfaced in your team or organization.
- List 2–3 problems or inefficiencies Scrum has helped make visible.
- For each, note whether your team can solve it independently or if it needs to be escalated.
- Discuss with your team how to address at least one of these issues in your next Retrospective.
What are some common barriers that prevent organizations from acting on the issues uncovered by Scrum?
What does Scrum do with organizational problems?
Tap to revealScrum exposes weaknesses, gaps, and problems, but does not solve them; action is required from the organization.
What is the role of an escalation path in Scrum?
Tap to revealIt allows teams to elevate problems they cannot solve themselves to those who can change the status quo.
What is the main benefit of Scrum’s iterative inspection?
Tap to revealIt provides regular opportunities to identify and address issues, driving continuous improvement.
Describe a real or imagined scenario where your team identified a recurring issue thanks to Scrum. What steps could be taken to ensure this issue is addressed effectively?
Practitioners often find that the visibility Scrum brings can be uncomfortable at first—but this discomfort is a sign that your organization is ready to grow.
- Scrum exposes, but does not solve, organizational problems.
- Teams should address what they can, and escalate what they cannot control.
- An effective escalation path helps teams achieve continuous improvement.
Scrum is a framework for exposing reality—not fixing it; meaningful improvement comes from taking action on what is revealed.
Your organization is perfectly engineered to get the results you are getting today. If you want to get better results, you are going to have to change things.
What is the primary role of Scrum in addressing organizational weaknesses?
If you want different results, you must be willing to confront and change the realities Scrum reveals.
The Shift
- Scrum exposes real problems in processes, policies, and structures—but cannot fix them for you.
- Improvement only happens when teams and organizations act on what has been revealed, not just acknowledge it.
- Establishing clear escalation paths ensures that issues beyond the team’s control are addressed for sustained progress.