Agile experts Yuval Yeret and Ryan Ripley join to discuss Marty Cagan's perspectives on SAFe and scaling Agile. They explore pain points of scaling technology, compatibility of Agile frameworks with big tech culture, and the comprehensive solution needed for a successful transition. The conversation delves into challenges of scaling Agile, the role of Scrum Masters vs Safe Program Consultants, the importance of technology architecture, and the need to focus on outcomes. They also discuss presenting SAFe principles and comparing them to Scrum.
Read more
AI Summary
AI Chapters
Episode notes
auto_awesome
Podcast summary created with Snipd AI
Quick takeaways
Successful companies focus on agility and understand Agile principles, whether or not they use SAFE.
Solid tech excellence, architecture, and build pipelines are crucial prerequisites for successful scaling, even with a comprehensive framework like SAFE.
Deep dives
Marty Kagan's Perspective on SAFE Implementation
Marty Kagan's post on scaling agile questions the use of SAFE and argues for a more product-centric approach. While Marty acknowledges the pain points and challenges in producing technology at scale, he believes that SAFE may not be suitable for companies that have already embraced agility and have the technical prowess to empower product teams without relying on excessive coordination mechanisms. He highlights that successful companies, like Google and Facebook, focus on agility and understand the principles of Agile, whether or not they use SAFE. Marty suggests that the target audience for SAFE implementation is the majority of organizations still transitioning towards agility, as they require a comprehensive solution, including case studies, certifications, and a business movement around it. He emphasizes the need for strong tech excellence, architecture, and build pipelines before considering a transformation to ensure successful scaling.
The Balance of Adoption and Quality in SAFE
The debate around SAFE implementation raises questions about striking a balance between adoption and the quality of implementation. As a framework created by a for-profit organization, SAFE faces the challenge of setting the bar for people who will implement it. While raising the bar would ensure quality, it might slow down adoption, while lowering it could lead to the wrong use of SAFE for profit without adequate experience in agile practices. However, market forces also play a role in setting expectations, as organizations increasingly demand more experience from those implementing SAFE. Marty's post also highlights the importance of focusing on principles rather than just practices, as principles drive successful agile transformations. Marty and others criticize SAFE without fully considering its alignment with core agile principles and the need for principles-driven approaches in implementing any agile framework.
The Need for Tech Excellence in SAFE Implementation
Marty's post draws attention to the importance of solid-tech excellence in successful scaling, as exemplified by companies like Amazon and Google. He argues that while implementing SAFE, organizations need to prioritize leveling up their technology, architecture, and build pipelines before pursuing a transformation. This is crucial for organizations to earn the right to scale and deliver frequent value to customers. Marty cites examples like Southwest Airlines, a SAFE-adopting company with technology deficiencies, leading to poor customer experiences. He emphasizes that technology and architecture excellence are prerequisites for successful scaling, and without it, even the most comprehensive framework like SAFE may not yield desired outcomes.
DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!
FTC DISCLAIMER: This video is not sponsored by anyone.