Mastering Agile transformation: A leader’s guide to process improvement

Agile transformation aims to enhance an organization’s ability to rapidly respond to changing requirements and improve its ways of working. It applies the Agile principles of adaptability and efficiency to teamwork, collaboration, processes and measurement to breathe new life into the businesses by creating an environment that embraces creativity and innovation, empowering employees and reducing unnecessary layers of management.

Samant Kumar is an Agile program manager and coach as well as member of the PEX Network Advisory Board. We sat down with him to delve into the topic of Agile transformation and its potential to drive meaningful process improvements.

PEX Network: You have an extensive background in Agile transformation and process enhancement. Can you briefly describe your journey and experience in Agile transformation? What first drew you to the Agile methodology and how has your understanding evolved over the years?

Samant Kumar: My journey began at IBM and eventually led me to Capgemini, where I witnessed firsthand the changing needs in project management. When Agile appeared about 15 years ago, it immediately grabbed my attention. The promise of agility (or being agile, if you prefer) is that teams can be more flexible, collaborate better and, above all, deliver faster. It’s not just about delivering more software or delivering it more efficiently; we’re also supposed to be delivering better software, using some of the most cutting-edge technologies, in many instances. We do this not by relying on some new set of tools or some new kind of magic. We do it by actually working with customers and other stakeholders to understand their needs better.

PEX Network: Agile is often seen as a shift in mindset. In your experience, what are the most important principles of Agile that should guide organizations when embarking on a process improvement journey?

SK: You’re absolutely right – Agile is a mindset. In my experience, some of the most vital principles are:

1. Customer collaboration over contract negotiation: Continuous engagement with customers ensures that the product being developed meets their needs and that there’s a clear understanding between the team and the customer about what is being built.
2. Responding to change over following a plan: Plans and roadmaps are important. But Agile encourages flexibility in the face of shifting customer needs and/or market dynamics.
3. Simplicity – the art of maximizing the amount of work not done: Agile teams, together with their customers, need to ensure that they are focusing on delivering the right work and that work is not being done in vain.
4. Building a sustainable pace: In Agile, work environments are supposedly sustainable over the long run. The work is expected to be performed at a high productivity level and in a way that teams perform at their best, not just occasionally, but all the time.

PEX Network: Agile transformation is known for its challenges. What are some common obstacles organizations face when transitioning to Agile and how can they overcome them?

SK: Embracing Agile can be a transformative journey for any company, but the path isn’t always smooth. The most common obstacles companies face include a reluctance to change by employees, who often find Agile too different from traditional project management. This reluctance can be overcome by creating a clear communication plan that unambiguously sets expectations and using the plan to educate the workforce about the dangers that Agile is meant to avert.

Also important is creating a "safe" environment where the Agile "way to work" is modeled and emulated by management. Leadership must be clear not only in setting the vision but in modeling Agile behaviors to a point that the teams are best able to execute what is now expected of them. Leadership might not use Agile methods themselves, but if they are not able to provide a vision that is in some way different from what went before and if they behave as they did before, then there is no reason to think that the same old misalignments between leaders and teams won’t continue during an Agile transformation.

Agile frameworks and processes require a deep understanding of their principles and an even deeper appreciation of why they should be used in the first place.

PEX Network: Successful Agile transformation depends heavily on the teams driving it. What are the key characteristics of high-performing Agile teams and how can organizations cultivate these traits to ensure successful transformation?

SK: High-performing Agile teams display a set of vital traits:

• They are collaborative: These teams don’t just communicate well – they work extremely well together. They solve problems together and work well with their stakeholder and subject matter expert (SME) partners.
• They have the courage to make the tough, important decisions: They exhibit good judgment and make sense of complex or ambiguous situations within the time frame allotted to them.
• They complete the work they plan for: These teams pledge to meet their sprint commitments no matter what, without compromising the quality of their work.
• They take serious responsibility for the work they do: They make quality a habit. They don’t cut corners.
• They understand the business context and value of the product they are developing: They make decisions and trade-offs based on that understanding. For organizations that want to see these elements in their teams, much of the work must be done at the outset. Teams must be trained in Agile. The work environment must encourage teams to be bold in their autonomy and self-management, to cross the line from just taking orders to actually making decisions, and for all team members to be invested in the work and its outcome.

PEX Network: Agile transformations often require a shift in leadership style. What does effective Agile leadership look like and how does it differ from traditional management approaches?

SK: Agile leadership fundamentally embraces the principles of servant leadership, contrasting sharply with the command-and-control model that characterizes traditional management. Servant leaders in Agile environments are less concerned with directing the effort of their teams and more interested in empowering their teams to make decisions, remove obstacles to effective work, and create work processes that enable sustainable and resilient development. This is the core of Agile: collaboration, work ownership and the engagement of stakeholders (including leaders) in the process being improved.

Agile leaders lead by example, enabling and serving teams, providing guidance (rather than micromanagement), facilitating improvement and creating the conditions necessary for teams to work better and smarter.

PEX Network: How can Agile be aligned with broader organizational goals and strategies? What role does leadership play in ensuring that Agile initiatives contribute to overall business success?

SK: Agile shouldn't be a standalone effort; it must sync with the broader strategic aims of the organization. It’s up to the leaders to ensure that Agile efforts are geared toward delivering some kind of business value. This means that an organization’s strategic goals must be translated into something that Agile teams can understand as specific, measurable objectives. Doing this aligns cross-functional teams and allows for tracking. Within an Agile initiative, the leadership sets the vision and facilitates collaboration across teams and departments.

PEX Network: What metrics or indicators do you use to assess the success of an Agile transformation, especially in terms of process improvement?

SK: Several important metrics can gauge the success of an Agile transformation:

1. Velocity: This indicates how much work the team accomplishes during each iteration. Patterns and bottlenecks become visible when you track velocity over multiple iterations.
2. Lead time: This is the duration from the request for a feature to its delivery, for example when the customer can actually use it. It is a fundamental process improvement objective to deliver features to production quickly.
3. Customer satisfaction: Keeping a pulse on how satisfied your customers are with the product you deliver is of paramount importance. Immediate and continuous feedback is a staple of Agile.
4. Team engagement: Last but definitely not least, you need to measure team engagement. A highly engaged team is a productive team, and long-term success in Agile is not likely without it. These are some basic measures that not only evaluate the efficacy of Agile and its principles but also provide a measure of continuous improvement.

PEX Network: Resistance to change is often a significant hurdle during Agile transformation. What strategies do you recommend for managing resistance and ensuring buy-in from stakeholders?

SK: Resistance is a normal part of change, but there are effective ways to manage it. Communicate clearly, as letting stakeholders know why you’re transforming and what the benefits are is crucial. That is especially true when you’re moving to Agile. Also, train and educate: making sure that both leaders and teams have access to proper training is essential. Leaders need to be able to align the organization and teams need to have enough of a shared understanding to be able to pull off the work.

Also, use small teams to pilot Agile. Small teams working in development, IT or other parts of your organization can demonstrate the value that Agile brings throughout the enterprise. Lastly, bring stakeholders in early. Identify the people in your organization who might be resistant to change and reach out to them. Get their input on the transformation and address their concerns upfront.

PEX Network: In your experience, which tools or techniques have been most effective in supporting Agile process improvement, and how do you decide which tools are right for a particular organization?

SK: Tools that boost teamwork and clarity are vital for Agile transformations. Many popular tools help teams work better together and stay clear-headed about what they’re doing. Here are some of my current favorites:

• Jira and confluence: These are often used in tandem by large teams for task management and project documentation.
• Miro or MURAL: Working on a virtual whiteboard with a distributed team can be surprisingly effective. Both these tools allow real-time collaboration.
• Retrospective tools: Collecting feedback from your team after a sprint or project can yield surprising insights about what to improve. FunRetro is a tool that allows you to do this easily and remotely. What tools your team ends up using will depend on the size and nature of your organization, the complexity of the project you’re working on and the specific needs of your team. The goal is to choose tools that support the Agile principles of transparency, collaboration and iterative improvement.

PEX Network: How can organizations scale Agile beyond IT to impact other departments and processes?

SK: Scaling Agile effectively means changing the organizational mindset. It isn’t just for IT anymore – executives and managers need to lead their companies toward a more holistic and comprehensive Agile transformation. Agile is being used not just in product development but also in HR, marketing and finance processes. A growing number of large enterprises in various industries are looking to models like SAFe (the Scaled Agile Framework) for guidance on how to implement Agile at scale. These models take Agile beyond the team level, aligning a large group of teams to work toward a common purpose.

PEX Network: After the initial transformation, how can organizations ensure the sustainability of Agile practices?

SK: Agile transformation is a journey that demands sustained focus. To truly embed Agile ways of working in an organization, you need a lot more than just a one-time boot camp or an initial rollout project to get started. The actual working practices that Agile teams employ are continuously evolving. They’re always finding new, lightweight ways to solve problems and do things better. To keep up with those changes, your teams need to see what other Agile teams are doing and get trained in the latest set of techniques. The same goes for the roles that people play on Agile teams. You can’t just assume that people will know what to do without the appropriate training and that they’ll stay current on what Agile teams are doing without ongoing investments in skill development.

PEX Network: Can you share an example of a successful Agile transformation you’ve led or been a part of? What were the key strategies that contributed to its success?

SK: At IBM and Capgemini, I was part of highly successful transformations that involved integrating Agile practices within multiple teams. We achieved this success through several key strategies. Firstly, we started small, piloting Agile in a few central teams. From there, we were able to demonstrate value via quick wins. Secondly, we communicated clearly and invested in real training for people at all levels. Finally, we had strong, visible, active support from our leadership, which made a huge difference in driving culture change.

PEX Network: Agile emphasizes continuous learning. How do you encourage a culture of learning within an organization and what role does mentorship play in this process?

SK: In Agile, the idea of continuous learning is essential. I foster this environment by encouraging a growth mindset, where errors aren’t just forgiven, they’re embraced as necessary steps toward understanding. Our regular cadence of training sessions, the knowledge osmosis that happens when our teams sit together, even in a virtual space and the deep well of external resources available to our industry, such as webinars and conferences, all work to keep Agile learning fresh in our minds. Perhaps most of all, mentorship, that old but effective model of personalized guidance, serves as a strong backbone to direct the next generation of Agile leaders on their journey.

PEX Network: Agile methodologies continue to evolve. Where do you see the future of Agile in process improvement and how should organizations prepare for these changes?

SK: Agile’s future is set to emphasize business agility even more, allowing entire organizations to quickly adapt to the myriad changes happening in today’s world. It’s not just IT or software development that needs to be agile anymore; all departments must be prepared to pivot when necessary. The future will likely see more integration of artificial intelligence (AI) and automation into Agile processes. Teams may use AI for greater assistance in certain tasks and automation can help even more with streamlining work.

PEX Network: What advice would you give to executives and senior leaders who are considering or currently overseeing an Agile transformation in their organizations?

SK: Embrace the process of transformation. Think of it as a marathon, not a sprint. It’s going to take a while and you’ll need more than just a good system in place. It requires commitment from the whole organization. Leadership must have a clear vision and they must create an environment of trust and empowerment for the teams that are doing the work. The teams, in turn, have to embrace the same values that the leaders are espousing and that the organization is basing its vision on: flexibility, collaboration and improvement.

All Access: Process Mining and Process Intelligence 2025

Join us at All Access: Process Mining and Process Intelligence 2025 to discuss how you can transform insights into actions and implement smarter processes through intelligent mining.

Register Now