An agile initiative is not mainly a one-time rollout of Scrum, Kanban, SAFe, Jira, new job titles, or a different meeting calendar.
Those changes may be part of the work. But they are not the point.
The point of an agile initiative is to improve an organization’s ability to deliver valuable work, learn from feedback, respond to change, and make better decisions under uncertainty.
Treating the effort as a rollout leads to a very different set of leadership behaviors than treating it as an ongoing improvement effort.
A rollout can be managed mostly as a project: train people, rename roles, update workflow boards, schedule new meetings, and declare the rollout complete.
Improving agility cannot be managed that way. You cannot know in advance exactly what “better agile” will look like for every team, product, department, or organization. You can know what outcomes you want. You can know what problems you are trying to solve. But the exact practices, team structures, decision rules, and improvement path need to emerge as people learn.
That is why the best way to lead an agile initiative is to use agile to improve agility.
Set a goal. Choose a small improvement. Try it. Review what happened. Adjust. Repeat.
That sounds simple, but it changes the leadership stance. The goal is no longer to install agile perfectly. The goal is to make the organization measurably better at delivering value.
Start With Outcomes And A Shared Understanding Of Agile
Before beginning an agile improvement initiative, leaders should be clear about what they want agility to improve.
Useful goals might include:
- reducing time to value;
- improving customer satisfaction;
- reducing defects found after release;
- improving employee engagement;
- making planning more reliable;
- shortening feedback loops;
- helping teams respond to changing priorities without chaos.
These goals are better than “adopt agile” or “roll out Scrum.” They help leaders and teams evaluate whether the initiative is producing meaningful change.
A clear outcome also helps avoid one of the most common problems in agile initiatives: different people using the same word to mean different things.
One team may think agile means following the Scrum Guide closely. Another may think it means using Kanban. Another may think they are agile because all work is tracked in Jira. Leaders may say they want empowerment but still expect every important decision to come back up the hierarchy.
None of this is unusual. Agile is flexible, and that flexibility is part of its strength. But without a shared understanding, flexibility becomes confusion.
A leadership team should be able to answer questions such as:
- Why are we trying to become more agile?
- What business outcomes are we trying to improve?
- What decisions should move closer to teams?
- What practices do we expect teams to use consistently?
- Where do teams have freedom to adapt their way of working?
- What behaviors will leaders need to change?
- How will we know whether this initiative is helping?
A shared understanding does not mean every team works identically. It means people share enough language, principles, and expectations that teams can make local decisions without pulling the organization in conflicting directions.
Why Agile Initiatives Fail
When agile initiatives struggle, the same problems tend to show up again and again.
Seeing those patterns early gives leaders a chance to respond before skepticism hardens and the organization starts explaining the failure in unhelpful ways.
Problem: Agile Becomes Process Without Mindset
The most visible parts of agile are easy to copy: sprints, daily scrums, reviews, retrospectives, product backlogs, task boards, story points, and new roles.
Those practices can help. But they do not automatically change how an organization thinks about control, uncertainty, learning, or accountability.
A company can adopt agile meetings and still expect every decision to be approved by management. It can create product owner roles while still letting stakeholders bypass the product owner. It can ask teams to deliver iteratively while still judging them by fixed-scope, fixed-date expectations set too early.
That creates agile in name only.
The organization looks busier. It may even look more agile. But decisions are still made the old way, work still flows the old way, and teams still operate inside the old management logic.
Problem: Agile Is Delegated, Not Lived
Leaders can delegate many things. They cannot delegate the change in leadership behavior required for agile to work.
Teams can learn Scrum. Scrum Masters can be trained. Product owners can be assigned. Coaches can be hired. But many of the biggest obstacles teams face are outside the team: budgeting rules, overloaded specialists, conflicting priorities, unclear authority, too many active initiatives, or stakeholders who expect change without trade-offs.
Teams cannot solve those problems alone.
When leaders stay outside the change, the organization sends a mixed message: teams should become agile, but the surrounding system will remain mostly the same.
Teams read that signal quickly.
If leaders say they want learning but reward certainty, teams will hide uncertainty. If leaders say they want outcomes but ask only about utilization, teams will optimize for looking busy. If leaders say they want empowerment but override every uncomfortable decision, teams will wait for permission.
Teams follow what leaders do, not what leaders say.
Problem: Organizations Scale Problems Before Solving Them
Scaling agile can be useful. Scaling too soon can make things worse.
Before adding large-scale coordination structures, leaders should ask whether the organization has enough team-level success to build on:
- Can a few teams deliver valuable work?
- Can they finish within short iterations?
- Can they work with a clear product owner?
- Can they get feedback from stakeholders and customers?
- Can they improve how they work?
- Can they plan with enough reliability that the business can make good decisions?
If the answer is no, scaling often spreads dysfunction.
It adds meetings, roles, dependencies, and coordination around problems the organization has not yet solved. Weak product ownership becomes weak product ownership across more teams. Too much work in progress becomes a larger traffic jam. Unclear decision-making becomes more expensive.
It is better to build coordination around teams that are already working well than to hope a larger structure will make struggling teams successful.
Problem: Too Much Work In Progress Slows Everything Down
Many organizations think they have a speed problem, so they start more work.
More initiatives. More urgent requests. More people assigned across multiple teams. More projects moving at once.
This usually creates the opposite of speed.
When too much work is in progress, people switch constantly. Work waits. Dependencies multiply. Quality slips. Teams look busy, but less finishes. Leaders see slow progress and often respond with more pressure, which adds even more work and interruption.
Doing fewer things at once often makes the organization faster overall.
That is hard because real prioritization hurts. If saying no does not disappoint anyone, the organization probably has not really prioritized. It has only rearranged a list while continuing to overload the system.
Problem: Product Ownership Is Too Weak
Many delivery problems are really product decision problems.
The organization may have someone called a product owner, but that person may not have enough authority to make meaningful priority decisions. Stakeholders, managers, executives, architects, salespeople, and urgent customer requests may all compete for the team’s attention.
When everyone has a say and no one owns the outcome, the backlog becomes a storage place for requests instead of a strategy for delivering value.
Teams can remain very busy in that environment. They can complete many product backlog items. But they may still struggle to answer the more important question: Are we delivering the right things?
An agile initiative needs clear product ownership. That does not mean one person ignores input from others. It means someone is accountable for the final priority call, can explain trade-offs, and can give the team a stable direction.
Problem: Agile Reveals What The Organization Still Has To Solve
Agile often makes problems visible before it makes them better.
Shorter feedback loops reveal weak product choices. Sprint reviews reveal stakeholder misalignment. Retrospectives reveal teamwork issues. Forecasts reveal uncertainty. Product backlogs reveal too many priorities. Team-level work reveals organizational bottlenecks.
That visibility can feel uncomfortable. It can even make the initiative look worse for a while.
But visibility is not the problem. Visibility gives the organization a chance to improve.
When agile exposes unstable priorities, weak product ownership, slow feedback, or leadership contradictions, leaders should resist the urge to blame agile. The better response is to ask: What is this showing us that we need to fix?
Use Agile To Improve Agility
The best way to lead an agile improvement initiative is to manage the improvement effort in an agile way.
That means setting a direction, choosing a small improvement, trying it, reviewing what happened, and adapting from there. The organization does not need to know the perfect future state before it starts. It needs a clear purpose, short feedback loops, and a way to keep improving.
Mountain Goat Software calls this the Better Agile Framework. It has four parts:
- Iterate toward greater agility. Treat each improvement as an experiment and learn from what happens.
- Use improvement backlogs. Make the work of improving agility visible, prioritized, and inspectable.
- Guide rather than control the effort. Leaders create energy, remove obstacles, and set useful boundaries without turning the initiative into a compliance program.
- Supplement teams with improvement communities. Use communities to address problems that span teams, such as testing, product ownership, metrics, or cross-team collaboration.
Use the Better Agile Framework when your organization needs a lightweight way to coordinate improvement without turning the effort into a top-down program. It gives leaders, teams, and improvement communities a shared structure for deciding what to improve next and learning from each change.
Use The Five Pillars To Decide What To Improve First
Agile improvement initiatives become fragile when they focus on only one part of the system.
A team may learn new practices but lack role clarity. Leaders may say the right things but continue rewarding individual heroics. Product owners may understand agile but lack authority. Teams may improve internally while stakeholders continue disrupting sprints or demanding fixed scope without trade-offs.
The five pillars help leaders decide where to focus next:
- Mindset: Do people understand why they are being asked to work differently?
- Practices: Are teams learning and using the practices needed to deliver, inspect, and adapt?
- Roles: Are responsibilities clear enough for decisions to be made well?
- Teamwork: Are people working as a real team rather than as individuals passing work from one specialist to another?
- Outside-the-team support: Are stakeholders, managers, and surrounding functions changing how they interact with teams?
Use the five pillars as sources for improvement backlog items. When progress stalls, look across the pillars and ask which part of the system is limiting agility now.
For example, a team may have enough training and motivation but still struggle because stakeholders keep inserting urgent work during the sprint. That is not primarily a practices problem. It is an outside-the-team support problem. Another team may have a strong Scrum Master and good sprint events but still lack a product owner with authority. That is a roles problem.
The value of the five pillars is diagnostic. They help leaders avoid solving the wrong problem.
Make The Leadership Shifts That Let Agile Work
The success of an agile initiative is visible in leadership behavior.
Leaders do not need to know every detail of every agile framework. But they do need to change how they create clarity, support teams, make trade-offs, and respond to uncertainty.
Participate Visibly
Agile becomes believable when leaders show up consistently.
That does not mean attending every team meeting. It means participating where leadership context and feedback help: sprint reviews, roadmap conversations, planning discussions, product goal reviews, and retrospectives where organizational obstacles need leadership attention.
When leaders attend reviews and ask what was learned, teams prepare differently. When leaders ask about outcomes rather than only output, teams focus differently. When leaders remove obstacles, teams learn that transparency is worth the risk.
Visible participation tells the organization that agile is not the initiative of the quarter.
Empower For Real
Empowerment requires authority, time, and trust.
A product owner needs authority to make priority decisions. A Scrum Master needs enough time to help the team improve. A team needs trust when it makes a reasonable decision that is not the one a leader would have made.
Symbolic empowerment creates frustration. People are told to own decisions, then overruled whenever those decisions become uncomfortable.
Real empowerment is a structural choice. Leaders decide who owns what, give those people the conditions to do the work well, and then support them when trade-offs become difficult.
Focus The System
Leaders improve agility by helping teams finish.
That often means reducing work in progress, protecting teams from constant interruption, and making hard priority choices.
When everything is important, nothing moves well. Teams cannot be predictable when priorities change constantly, people are split across too many efforts, and urgent work is inserted without trade-offs.
Focus is not a motivational slogan. It is a leadership discipline.
Learn Sooner
Agile is a learning system.
Leaders who understand this do not demand false certainty too early. They ask what is known, what is uncertain, what the team expects to learn next, and what range of outcomes is reasonable.
That does not mean leaders stop caring about dates, budgets, or commitments. It means they use feedback to make better decisions rather than pretending every plan can be known perfectly in advance.
Better questions include:
- What do we know?
- What is still uncertain?
- What would need to be true for this plan to work?
- What options have we considered?
- What trade-offs should we discuss?
- What could we learn sooner?
- What decision do you need from me?
Leaders who ask these questions make uncertainty discussable. That is one of the most important things they can do.
Improving Agility Without Another Big Program
Many organizations are not trying agile for the first time. They are trying to make agile work better than it has so far.
They may have trained teams, introduced Scrum, hired coaches, reorganized, or adopted a scaling framework. Some of it helped. Some of it faded. Some of it left people skeptical.
That history shapes how people respond to the next agile improvement initiative.
If people have experienced previous change programs that overpromised and underdelivered, they will not automatically trust the next effort. They may wait it out. They may comply on the surface while preserving old habits underneath.
Leaders can reduce change fatigue by making the next effort smaller, more honest, and more connected to real problems.
Instead of announcing a sweeping program, leaders can say:
- Here is the business problem we need to solve.
- Here is what we believe agility can help us improve.
- Here are the first few changes we will try.
- Here is how we will know whether those changes are helping.
- Here is what leaders will change, not just what teams will change.
That approach is less dramatic. It is also more credible.
People do not need another slogan. They need evidence that this time the organization is willing to change the conditions around teams, not merely ask teams to absorb another process change.
Common Questions About Leading Agile Initiatives
Why Do Agile Initiatives Fail?
Agile initiatives fail when organizations change visible practices without changing how decisions are made. Common causes include weak leadership participation, unclear product ownership, too much work in progress, scaling too soon, poor role clarity, and expecting agile to fix problems the organization still refuses to address.
What Should Leaders Do During An Agile Initiative?
Leaders should set clear outcomes, create useful boundaries, participate visibly, remove organizational obstacles, protect focus, clarify roles, support product ownership, and create safety for teams to surface problems early. They should guide the improvement effort without controlling every team-level decision.
What Is The Better Agile Framework?
The Better Agile Framework is Mountain Goat Software’s approach for improving agility using agile itself. It encourages organizations to iterate toward greater agility, use improvement backlogs, guide rather than control the improvement effort, and supplement teams with improvement communities. This Guide introduces the framework; the full framework should be explained on its own page.
What Is An Improvement Backlog?
An improvement backlog is a prioritized list of experiments and changes intended to improve agility. Teams, improvement communities, and guiding coalitions can all use improvement backlogs to make change visible, actionable, and inspectable.
What Is A Guiding Coalition?
A guiding coalition is a small group of influential leaders who support and guide an agile improvement initiative. The coalition creates energy, communicates why change matters, removes organizational obstacles, provides resources, and helps the organization improve without turning agile into a top-down compliance program.
Should We Start Small Or Go All In?
Either can work, but both have risks. Starting small gives the organization a chance to learn before expanding. Going all in can create urgency and consistency, but it also spreads mistakes quickly. The best choice depends on the organization’s goals, urgency, leadership support, and capacity for change.
How Do We Know Whether An Agile Initiative Is Working?
Look for evidence that the organization is getting better at delivering value. Useful signs include shorter feedback loops, more reliable planning, clearer priorities, stronger product ownership, better collaboration, improved quality, higher stakeholder trust, and teams that can inspect and adapt how they work.
How Can Leaders Avoid Change Fatigue?
Avoid slogans, big-bang promises, and process theater. Focus on real problems, small improvements, visible leadership behavior, and honest feedback. Show people what will change in the system around them, not just what ceremonies they are expected to perform.
Need Help Leading An Agile Initiative?
Agile initiatives succeed when leaders create the conditions teams need to improve: clear outcomes, empowered roles, practical feedback loops, enough focus to finish, and a way to keep learning.
Mountain Goat Software helps leaders and teams improve agility without turning the effort into a heavy program. We can help you diagnose what is happening now, form a guiding coalition, create improvement backlogs, support improvement communities, and strengthen the five pillars of sustainable agile change.
Last update:
July 28th, 2026