Quantifying the Benefits of Agile for Better Transformation Results

Summary

This video script reflects on the evolution of agile practices over the past 23 years, highlighting the challenges of scaling agile in larger organizations with complex dependencies. It critiques the shift from agile principles to prescriptive frameworks like Scrum and SAFe, emphasizing the importance of proactive dependency management and orchestration. The script explores the tension between agile as a cultural ethos and as a rigid process, arguing that while agile is necessary, it is insufficient to solve the broader challenges organizations face. The speaker advocates for a more adaptable approach that balances agile's cultural roots with pragmatic frameworks.

Takeaways

• 😀 Agile struggles when external dependencies and constraints are the norm, especially in large organizations.
• 😀 Scrum can work well in small, self-contained teams but fails when dependencies and cross-team coordination become complex.
• 😀 Agile's cultural ethos of collaboration and adaptability is crucial, but it's challenging to sustain without stable, dedicated teams.
• 😀 The Scrum of Scrums model, while helpful, is reactive rather than proactive in addressing dependencies between teams.
• 😀 A 'Product Owner Team' can provide a proactive solution by identifying cross-cutting concerns early and collaborating across teams.
• 😀 SAFe (Scaled Agile Framework) is an attempt to address scaling challenges but introduces complexity when applied prescriptively.
• 😀 The Agile community is currently divided between those focused on culture and those focused on process, but both are insufficient on their own.
• 😀 The lack of clear backlogs, dedicated teams, and stable velocity often undermines the effectiveness of Agile methodologies in large organizations.
• 😀 Agile, as it is commonly practiced, often fails to produce business value when external dependencies aren't effectively managed.
• 😀 The Agile Manifesto's principles are still relevant, but their application needs to evolve to address the complexities of modern organizations.
• 😀 Agile's initial success was based on smaller teams with easy access to customers, but today's challenges require more sophisticated, cross-functional orchestration.

Q & A

What are the main challenges organizations face when adopting agile?

The main challenges include managing external dependencies and constraints, especially when they become the norm. This makes it difficult for teams to deliver a cohesive product, even if individual scrum teams are working well.

Why is it important for scrum teams to stay together?

Teams need stability to build a collaborative culture, develop consistent velocity, and maintain focus on delivering working, tested increments of software. Frequent team changes hinder this process.

What problem arises when external dependencies can't be proactively managed?

When external dependencies and constraints aren't managed proactively, scrum teams can still be productive but their efforts won't align into a cohesive whole, preventing the final product from being shipped successfully.

How does the concept of 'scrum of scrums' help address dependencies?

'Scrum of scrums' is a coordination mechanism where scrum masters from different teams meet to address cross-team dependencies. However, it can be reactive, resolving issues after they arise rather than preventing them early.

What is the difference between a 'scrum of scrums' and a 'product owner team'?

A 'scrum of scrums' is a reactive model focused on resolving issues after they happen, while a 'product owner team' is a more proactive approach designed to anticipate dependencies, risks, and cross-cutting concerns early in the process.

What role do product owners play in managing dependencies?

Product owners are responsible for managing the backlog and ensuring that dependencies are identified early. They collaborate with other roles like architects and analysts to plan ahead and manage risks.

How do cross-functional teams contribute to successful agile implementation?

Cross-functional teams bring together diverse skills and perspectives, enabling them to address different aspects of a project. This holistic approach helps ensure that all elements are covered, reducing the likelihood of bottlenecks or missing requirements.

What is the impact of adopting frameworks like SAFe on agile practices?

While frameworks like SAFe offer a structured approach and help address scalability issues, they can also introduce complexity. They risk becoming overly prescriptive, which may lead teams to overlook the fundamental principles of agile.

Why does the author believe agile, as commonly practiced, is insufficient?

The author argues that agile, in its common form, does not adequately address the challenges of large, complex organizations with multiple interdependent teams. It lacks mechanisms for managing cross-team dependencies and risks effectively.

How did the agile community evolve over the past 23 years?

The agile community has evolved into two camps: one focusing on the cultural ethos of agile with an emphasis on collaboration and adaptability, and the other focusing on structured processes and frameworks. Both camps face challenges in addressing the broader organizational needs.