Summary

Is Agile Fragile? Examining the State of Agile in Today's Project Management Landscape

In this episode of the PM Cowboy podcast, Mark interviews Roy Schilling, an Enterprise Transformation Coach, to delve into the current state of Agile methodologies. They discuss the evolution of Agile, its successes, its failures, and whether it's truly living up to its potential in today's complex project environments. This is a must-listen for project management leaders navigating the ever-changing world of Agile.

Roy Schilling's Agile Journey: From Developer to Transformation Coach

Roy shares his journey from a software developer to an Enterprise Transformation Coach, highlighting his experiences in the heavily regulated and traditionally rigid banking sector. He emphasizes the frustration of witnessing monumental project failures due to organizational challenges and a lack of leadership. This led him to explore Agile as a better way, focusing on empowerment, respect, and people-centric approaches.

The Passion Behind Agile: Empowerment and Respect

Roy underscores the importance of passion in the Agile space. He highlights that Agile is not just about delivering projects but about making a real difference by empowering people and treating them with respect. He emphasizes that true Agile transformation requires a shift in mindset and a commitment to creating a positive and collaborative work environment.

Key Drivers of Project Failure: Clarity, Leadership, and Expectations

The discussion explores common reasons for project failures, including:

• Lack of Clarity: A lack of understanding of what success looks like and why the project is even being undertaken.
• Poor Requirements: Inadequate understanding and management of project requirements.
• Unrealistic Expectations: Setting unrealistic deadlines and expectations.
• Poor Leadership: A lack of support and guidance from leadership to remove obstacles.

The Spotify Model: A Cautionary Tale of Agile Hype

The podcast addresses the hype surrounding the Spotify model, acknowledging its initial success as a revolutionary approach with tribes and squads. However, it emphasizes that the model worked well for Spotify at a specific point in time as a small, agile startup. It's crucial to recognize that the Spotify model is not a one-size-fits-all solution and that even Spotify itself has evolved beyond it. Applying it blindly to different contexts, especially in traditional organizations like banks, is often a mistake.

Disciplined Agile: Scaling Agile for Complex Projects

The conversation transitions to Disciplined Agile (DA), a scaling technique designed to address the challenges of implementing Agile in larger, more complex organizations. DA aims to coordinate multiple teams and maintain a systemic view, incorporating program and portfolio management principles. Roy explains that DA, along with other scaling frameworks like SAFe and LeSS, helps organizations avoid creating new silos when expanding Agile beyond individual teams.

Way of Working (WoW): A Double-Edged Sword

The hosts discuss the concept of "Way of Working" (WoW) introduced in Disciplined Agile, where teams self-organize and define their preferred Agile approach. While philosophically appealing, they caution against allowing teams to choose their WoW without proper guidance and knowledge. In larger organizations, a lack of standardization can lead to chaos and inefficiency. The key is to strike a balance between team autonomy and organizational alignment, creating a minimum viable process that ensures synergy and consistency.

Scrum vs. Kanban: Choosing the Right Tool for the Job

The podcast clarifies the differences between Scrum and Kanban, emphasizing that they are both tools in the Agile toolbox. Scrum is batch-oriented, using time-boxed sprints, while Kanban focuses on continuous flow and visualizing the workflow to identify bottlenecks and improve efficiency. The choice between Scrum and Kanban depends on the specific context and the volatility of requirements. Kanban is often more suitable for situations with high volatility and ad-hoc work, while Scrum is better for projects with more predictable requirements.

The Importance of Team Stability and Dedicated Resources

The discussion highlights the importance of building stable, high-performing teams and minimizing team turnover. Keeping teams together allows them to develop trust, share knowledge, and improve their performance over time. The hosts also explore the idea of creating dedicated resource pools or SWAT teams to address specialized skills or projects that don't fit neatly into traditional team structures. This can help organizations optimize resource utilization and improve project outcomes.

The Power of Lean Thinking: Eliminating Waste and Maximizing Value

The podcast emphasizes the importance of Lean thinking in project management and portfolio management. Lean focuses on eliminating waste, maximizing value, and continuously improving processes. The hosts discuss various forms of waste, including waiting, Reinventing the wheel, and smoke and mirrors (politics and dishonesty). They advocate for a Lean portfolio approach, viewing projects as investments and prioritizing those that deliver the greatest value.

Conclusion: Agile as a Journey, Not a Destination

The conversation wraps up by emphasizing that Agile is an iterative journey, not a fixed destination. Organizations must continuously adapt and evolve their Agile practices to meet their specific needs and challenges. The true power of Agile lies in its ability to visualize problems, empower teams, and drive continuous improvement. Project management leaders must embrace a flexible and adaptive mindset to navigate the complexities of the modern project landscape and achieve lasting success.

Key Takeaways:

• Agile is not a one-size-fits-all solution; it requires adaptation and tailoring to specific contexts.
• Leadership plays a crucial role in Agile success by providing support, removing obstacles, and fostering a culture of empowerment.
• Team stability and dedicated resources can significantly improve project outcomes.
• Lean thinking is essential for eliminating waste and maximizing value in project and portfolio management.
• Embrace Agile as a journey of continuous improvement, not a fixed methodology.