Scaling Agile practices across an organization can be challenging, but it’s not impossible. We asked industry experts to share one piece of advice they would give to an organization struggling to scale agile practices beyond a single team. Discover strategies focused on breaking silos, fostering collaboration, and aligning mindsets to achieve effective Agile adoption.
- Break Team Silos for Organic Agile Adoption
- Experiment with Cross-Team Practices for Effective Scaling
- Cultivate Agile Culture Instead of Enforcing Processes
- Invest in Dedicated Coaching and Cross-Team Collaboration
- Align Mindsets Across All Organizational Levels
- Foster Collaboration Culture for Successful Agile Scaling
- Set Clear Goals and Encourage Continuous Improvement
Break Team Silos for Organic Agile Adoption
The single most important and valuable piece of advice that I have for teams struggling with organization-wide agile adoption is this: Break your team silos.
In the early years of Agile’s popularity, only core tech teams worked on Agile principles. Then one day, we realized that our design teams were also planning website updates in a sprint-like fashion. There were weekly rollouts and reviews instead of how they used to plan everything months in advance earlier.
We were surprised by this but soon realized that a QA had suggested the structured way of working. Seeing its benefits, the design team agreed. There was no need for governance or authority to drive this adoption.
That’s when we figured that when team members interact, information and ideas also flow. So, don’t let your teams operate in silos. Strategically swap team members between projects, and you won’t just transfer skills but processes, ways of thinking, and information. It may feel disruptive at first because people need to adjust to new teammates, but it’s far more effective than enforcing governance from the top.
Pratik Mistry
Evp – Technology Consulting, Radixweb
Experiment with Cross-Team Practices for Effective Scaling
My advice would be: don’t rush into scaling. Make sure your teams are truly ready for it and that strong leadership is in place to support them. Having the right tools for cross-team transparency is also critical. From there, experiment, try different approaches, learn quickly, and don’t hesitate to drop ceremonies that don’t add value. Scaling agile is about adapting practices to the real dependencies and needs of your teams and product. There’s no fixed template.
For our projects, we tested a variety of practices — Product Owner rotations, shared Product Owners, joint Scrum of Scrums, combined Demo and Retrospective sessions, and more. None was perfect, but each proved effective in different contexts and scenarios. What often worked was combined Demo and Retrospective sessions. Bringing everyone together created a shared sense of progress and gave stakeholders one clear view of the product. Just as importantly, it sparked cross-team learning; ideas from one team often inspired improvements in another. The key is to keep those sessions focused and well-facilitated so they don’t become too long or drift into status-reporting.
We also experimented a lot with rotating and sharing Product Owners. Rotations broadened perspectives but hurt consistency in decision-making. And a single PO juggling multiple backlogs often struggled with prioritization, which slowed decision-making and left some teams waiting for clarification. Unless the teams are very small and tightly aligned, shared PO introduces more friction than it resolves.
Alex Ramasheuski
Architecture and Solutions Director, ScienceSoft
Cultivate Scaling Agile Culture Instead of Enforcing Processes
If you’re struggling to scale Agile beyond one team, here’s my advice: stop treating Agile as a process to roll out and start treating it as a culture to grow. Many organizations get stuck because they copy and paste rituals — stand-ups, sprints, retrospectives — without actually aligning leadership, product, and engineering around the same mindset. This approach is like planting seeds in concrete and wondering why nothing grows.
What worked for us was starting with transparency at the leadership level. Instead of mandating “we’re all Agile now,” we opened up cross-team demos and shared roadmaps so everyone could see how their work fit into the bigger picture. Once people saw the value — less finger-pointing, faster feedback, clearer priorities — adoption spread naturally. Agile scaled not because we forced it, but because teams saw it made their lives easier.
So if you’re struggling, zoom out: focus less on policing process and more on creating the conditions where Agile feels like oxygen instead of homework. That’s when it sticks.
Daniel Haiem
CEO, App Makers LA
Invest in Dedicated Coaching and Cross-Team Collaboration
Based on our experience, investing in dedicated agile coaching is crucial when scaling agile practices across multiple teams. When we faced resistance to adopting agile beyond our initial team, we found that having skilled coaches who could tailor the approach to each team’s unique dynamics made a significant difference.
Additionally, we established regular cross-team retrospectives focused specifically on collaboration patterns, which helped break down silos between departments. Recognizing and celebrating small wins along the way helped demonstrate the tangible benefits of agile to skeptical stakeholders and built momentum for broader organizational adoption.
George Fironov
Co-Founder & CEO, Talmatic
Align Mindsets Across All Organizational Levels
I would advise a company that is having trouble scaling agile practices to put more emphasis on mindset alignment at all organizational levels rather than tools and frameworks. In our instance, we discovered that scaling was unsuccessful when leadership saw agile as merely “a process for developers” as opposed to a cultural change that affects communication, prioritization, and decision-making.
Investing in cross-functional alignment workshops prior to extending agile beyond the pilot team proved to be effective for us. We convened leadership, operations, and product stakeholders to establish common objectives and develop a common language around agility. As a result, when several teams implemented agile practices, they were working toward the same business goals and not in separate silos.
Everyone, from executives to delivery teams, understood how their work fit into the larger picture, which led to quicker decision-making and fewer bottlenecks. The goal of scaling agile shifted from adding ceremonies to developing organizational agility overall.
Oleh Stupak
CEO & Co-Founder, Mgroup Shopify Agency
Foster Collaboration Culture for Successful Agile Scaling
If I had only one piece of advice for an organization that has been struggling to scale agile practices beyond one team, it would be to focus on developing a culture of collaboration and alignment instead of simply replicating practices to scale. It is easy to see the immediate value in agile when it is only one team; faster iterations or improved flow of work. However, scaling agile practices across multiple teams means creating shared understanding and acceptance of agile within the organization.
To do this, it is essential to ensure that clear, consistent, and relevant communication is established between teams while involving stakeholders (e.g., product owners, managers, and team leads) in understanding their role in supporting agile both individually and collectively. Introducing agile champions at every level of the organization can help with accountability for teams, hold their teams accountable, and provide experience and mentorship. As an organization scales, it will be important to maintain its core and foundational values, principles, and practices of agile: iterative improvement, fluidity of work, and collaboration.
One area where we were successful within our organization was putting together cross-team ceremonies (like routine syncs and retrospectives) to create transparency and continuous feedback loops. We also took the time to educate leadership on the value of agile as more than just for a development team; ensuring that all departments are aligning around outcomes gives everyone a chance to make faster data-informed decisions. This helped us break down silos and created a common sense of ownership for the agility of the organization. In scaling, it’s less about “doing it right” or following the framework perfectly and more about being nimble and adaptable to what works for your structure.
Sergio Oliveira
Director of Development, DesignRush
Set Clear Goals and Encourage Continuous Improvement
When using agile in many teams, it’s essential to have clear goals that everyone understands. This helps all teams work toward the same things. What helped us was letting team leaders work together to plan and organize, but still letting each team make its own decisions.
This way, teams stayed flexible and creative and focused on the company goals. Always encouraging teams to improve a little every day kept the process moving forward.
Paul Raphael
Founder // AI Marketing Specialist, Benwil Marketing Agency
