Unpopular Opinion But ... Scrum Isn't Always the Answer! ??

As a seasoned tech professional who's been in the game since the 2000s, I've witnessed the rise and fall of countless methodologies gurus. Today, I'm here to share a perspective that might ruffle a few feathers: Scrum isn't always the best framework. ??

Don't get me wrong : I ???? Scrum, and from the day I was trained to be a SCRUM Product Owner, back in 2008 by Claude Aubry (the most famous French Scrum writer/trainer/speaker/mentor), it really shaped the way i work as an agile Product Leader. While Scrum has undoubtedly revolutionised how many teams work, it's not a one-size-fits-all solution. Let's dive deep into why this matters and explore alternatives that might better suit your unique needs.

?? The Scrum Dominance: A Double-Edged Sword

Scrum has become the go-to framework for many organisations embarking on their agile journey. Its popularity is bolstered by a robust certification ecosystem and widespread adoption. However, this dominance can lead to a tunnel vision where teams force-fit Scrum into scenarios where it might not be the most effective approach.

The appeal of Scrum is undeniable:

• Clear roles and responsibilities
• Structured events that promote transparency and collaboration
• Emphasis on continuous improvement through retrospectives

But here's the catch: this very structure that makes Scrum powerful can sometimes be its Achilles' heel.

?? When Scrum Might Not Be the Answer

1. Research and Innovation Projects => Imagine you're working on a cutting-edge AI algorithm. The unpredictable nature of research doesn't always align with Scrum's fixed sprint structure. In such cases, a more flexible approach might be more suitable. Example: DeepMind, the AI research laboratory, often employs a more fluid approach to project management. Their groundbreaking work on AlphaGo and AlphaFold required the flexibility to pursue unexpected breakthroughs – something that might have been stifled by rigid sprint schedules.
2. Maintenance and Support Teams => For teams primarily focused on responding to incidents or bug fixes, the rhythm of Scrum sprints is an unnecessary burden. A flow-based system could be more appropriate here. Many DevOps teams find that Kanban's visual workflow and focus on cycle time are more suited to their need for rapid response and continuous delivery.
3. Highly Regulated Environments => In industries with strict compliance requirements, the documentation and approval processes does not fit neatly with the iterative incremental Scrum's nature. A hybrid approach combining agile principles with more traditional project management might be necessary. Example: In the pharmaceutical industry, where clinical trials and regulatory approvals are paramount, companies like Novartis have adopted a hybrid approach. They tend to incorporate agile principles for research and development while maintaining more traditional processes for compliance and documentation.

?? Alternatives to Consider

1. Kanban => Ideal for teams with a continuous flow of work items. It emphasises visualising work, limiting work in progress, and maximising efficiency. Key Benefits: Flexibility to adapt to changing priorities Focus on flow efficiency and reducing bottlenecks Continuous delivery model Who's Using It: Pixar Animation Studios uses Kanban to manage their complex, creative processes in film production.
2. Extreme Programming (XP) => Emphasises technical excellence and is well-suited for teams dealing with rapidly changing requirements. Key Practices: Pair programming Test-driven development Continuous integration Simple design Refactoring Who's Doing It Well: XP has been proven at cost conscious companies like IBM, Bayerische Landesbank, Credit Swiss Life, DaimlerChrysler, First Union National Bank, Ford Motor Company and UBS until now, influencing traditionnal companies and many startups and tech giants alike. (source and here)
3. Shape Up (by Basecamp) => A newer approach that focuses on shaping work before committing to it, giving teams full autonomy, and working in six-week cycles. Unique Aspects: Six-week cycles followed by two-week cool-down periods No daily meetings; more focus time for developers Emphasis on upfront shaping of projects to reduce uncertainty Early Adopters: Besides Basecamp itself, companies like Joyous - tech company in New Zealand - have reported success with this methodology.
4. Hybrid Approaches => Combining elements of different methodologies to create a tailored approach that fits your specific context. Example: Spotify's famously developed its own agile approach, moving away from strict Scrum to a more flexible approach that emphasises autonomy and cross-functional collaboration. This allowed them to scale agility across a rapidly growing organisation while maintaining their innovative edge.

?? The Psychology of Methodology Adoption

It's worth noting that the resistance to moving away from Scrum often has psychological roots:

1. Sunk Cost Fallacy: Teams and organisations that have invested heavily in Scrum training and certification may be reluctant to consider alternatives.
2. Comfort Zone: Scrum provides a clear structure that can be comforting. Exploring other methodologies requires stepping into the unknown.
3. Identity: For many professionals, being a "Scrum Master" or "Product Owner" has become part of their identity, making it challenging to embrace change.

Recognizing these psychological factors is crucial when considering methodology changes. It's not just about processes; it's about people and culture ;-)

?? Global Perspectives on Agile Diversity

We also need to remember ourselves that SCRUM - like most of the agile frameworks - are originated from the US, mostly created by a bunch of white male IT professionals from the Silicon Valley... so they might also included some cultural biases.

As a French professional who has worked internationally for over two decades, I've had the unique opportunity to observe and participate in the adaptation of agile principles across various cultures. This experience has shown me that a by-the-book SCRUM is often not suitable, but thanks gods agility is truly about principles rather than rigid practices, with each culture bringing its own flavor to the agile world.

???? Japan: The Kaizen Conundrum

In Japan, the concept of "Kaizen" (continuous improvement) aligns beautifully with agile principles. This cultural value of constantly seeking better ways to do things has been a cornerstone of Japanese manufacturing for decades and translates well to software development.

However, the traditional hierarchical business culture in Japan often clashes with agile's emphasis on self-organizing teams. This has led to a unique Japanese flavor of agile:

• Emphasis on consensus-building (nemawashi) before implementing changes
• Detailed upfront planning, merging agile with elements of waterfall
• Respect for seniority influencing team dynamics and decision-making

Case Study: Toyota's Approach While not a software company, Toyota's lean manufacturing principles have heavily influenced agile methodologies. Their adaptation of agile principles in software development for their vehicles demonstrates a blend of traditional Japanese business culture with modern agile practices.

???? Scandinavian Countries: Flat Structures and Work-Life Balance

In Scandinavian countries like Sweden, Norway, and Denmark, the flat organizational structures and strong focus on work-life balance have led to unique interpretations of agile methodologies:

• High emphasis on team autonomy and decentralized decision-making
• Flexible working hours and remote work integrated into agile practices
• Strong focus on consensus-building and inclusive decision processes

Unique Aspects:

• "Fika" breaks integrated into work life, promoting team bonding
• Longer sprint cycles to accommodate generous vacation policies
• High trust environments leading to less formal reporting structures

Example: Spotify's "Model" -born in Sweden, Spotify's agile operating model emphasizes autonomy, cross-functionality, and loose coupling between teams. This reflects the Scandinavian values of trust and flat hierarchies.

???? India: Scaling Agile for Global Delivery

India's large-scale IT services industry has developed its own flavors of agile to manage distributed teams and complex client relationships:

• Adapting agile for 24/7 global delivery models
• Balancing agile principles with the need for detailed documentation for offshore clients
• Developing hybrid models that incorporate elements of traditional project management to meet varied client expectations

Key Innovations:

• "Distributed Scrum" practices for managing teams across multiple time zones
• Enhanced focus on cultural training to bridge communication gaps with Western clients
• Integration of agile principles in large-scale projects, often involving thousands of team members

Case Study: Infosys' Agile Approach Infosys, one of India's largest IT services companies, has developed a unique "Zen Agile" framework that combines elements of Scrum, Kanban, and traditional project management to suit diverse client needs and large-scale projects.

???? France: Balancing Innovation with Structure

In my home country, France, I've observed a unique blend of innovation-driven agility and a desire for structure:

• Strong emphasis on conceptual understanding before implementation
• Preference for detailed planning phases, even within agile frameworks
• Integration of agile principles with France's strong project management traditions

Notable Aspects:

• Extended discovery phases to align with French business culture's emphasis on thorough analysis
• Adaptation of agile roles to fit within more traditional organizational structures
• Emphasis on written communication and documentation, reflecting French business norms

Example: Airbus' Agile Transformation

Airbus, the European aerospace giant with strong French roots, provides an excellent example of how agile methodologies have been adapted to suit French business culture while driving innovation in a complex, high-stakes industry.

Airbus' journey to agility is particularly interesting:

1. Gradual Adoption: Airbus didn't rush into a full-scale agile transformation. Instead, they started with pilot projects in their digital and software teams before expanding to other areas.
2. Hybrid Approach: Recognizing the need for structure in aerospace engineering, Airbus developed a hybrid model that combines agile principles with traditional engineering practices. This approach, sometimes referred to as "Agile@Airbus," respects both the need for flexibility and the rigorous safety standards of aircraft manufacturing.
3. Focus on Culture: Airbus put significant effort into changing the company culture to support agile ways of working. This included extensive training programs and changes to leadership styles to encourage more collaborative and less hierarchical decision-making.
4. Adapting Scrum: While adopting Scrum practices, Airbus adapted them to fit their specific needs. For instance, they extended sprint lengths in some cases to accommodate the complexity of aerospace engineering tasks.
5. Digital Transformation: Airbus' agile journey is closely tied to its digital transformation efforts. They've created digital factories and innovation centers that operate on agile principles, fostering rapid prototyping and iteration.
6. Balancing Documentation: While embracing agile's preference for working products over comprehensive documentation, Airbus has had to maintain rigorous documentation practices to meet aviation industry standards. They've worked to find a balance that satisfies both agile principles and regulatory requirements.

Airbus' agile transformation showcases how French companies can adapt agile methodologies to suit their unique business environment and industry requirements. It demonstrates that even in industries with high regulatory oversight and complex engineering challenges, agile principles can be successfully applied when tailored to the specific context.

This example highlights the French approach to agile: embracing innovation and flexibility while maintaining a structured approach that respects traditional engineering and management practices. It's a testament to the adaptability of agile principles and their potential to drive efficiency and innovation in even the most complex industries.

???? Germany: Engineering Precision Meets Agility

Germany's strong engineering culture has led to a unique interpretation of agile methodologies:

• High emphasis on quality and testing within agile frameworks
• Detailed documentation integrated into agile processes
• Structured approach to scaling agile across large organizations

Key Features:

• Integration of agile with traditional German quality management systems
• Adaptation of Scrum roles to align with German organizational structures
• Focus on long-term planning within agile frameworks

Case Study: BMW's Agile Transformation BMW's adoption of agile methodologies in their software development for vehicles showcases how German engineering precision can be successfully merged with agile flexibility.

These global variations remind us that agility is about principles, not rigid practices. The beauty of agile lies in its adaptability to different cultural contexts while maintaining its core values of flexibility, customer focus, and continuous improvement.

"The key is to focus on agile principles rather than getting bogged down in the specifics of any one framework," says Alistair Cockburn, one of the original signatories of the Agile Manifesto. "Adapt and evolve your practices based on what works for your team and your product."

Esther Derby, a leading voice in agile leadership, adds,

"The most successful teams I've worked with are those that understand the 'why' behind agile practices and are willing to experiment to find what works best for them."

?? Embracing Agile Diversity: A Practical Guide

1. Assess Your Current State => What's working well with your current methodology? Where are the pain points? What are your team's unique characteristics and needs?
2. Educate and Explore => Encourage team members to learn about different agile approaches. Attend conferences or webinars that showcase diverse methodologies Invite experts or consultants to share insights on alternative approaches
3. Start Small => Begin with pilot projects or single teams when trying new methodologies. Use retrospectives to gather feedback and iterate on your approach
4. Measure and Adapt => Define clear metrics to evaluate the impact of methodology changes Be prepared to course-correct based on results and team feedback
5. Foster a Culture of Continuous Improvement => Encourage ongoing learning and experimentation. Celebrate successes and learn from failures

?? Moving Forward: The Future of Agile

Scrum is a powerful tool, but it's just one tool in our agile toolkit. By embracing a diverse range of approaches, we can truly embody the agile spirit of continuous improvement and adaptation.

The future of agile lies not in rigid adherence to any single framework, but in the intelligent combination of practices that best serve our teams, our products, and ultimately, our customers. As the technology landscape continues to evolve, with trends like AI, IoT, and remote work reshaping how we build products, our approaches to agile must evolve too.

?? Further Reading

To deepen your understanding of agile diversity, I recommend these insightful books:

• "Agile Project Management with Kanban" by Eric Brechner
• For my French peeps l'excellent : "Kanban pour l'IT" de ??Laurent Morisseau??
• "Lean from the Trenches: Managing Large-Scale Projects With Kanban"and "Kanban and Scrum - making the most of both" by Henrik Kniberg
• "Implementing Lean Software Development: From Concept to Cash" by Mary Poppendieck
• "The Art of Agile Development" by James Shore
• "Shape Up: Stop Running in Circles and Ship Work that Matters" by Ryan Singer
• "Team Topologies: Organizing Business and Technology Teams for Fast Flow" by Matthew Skelton and Manuel Pais (Team Topologies) ???? ????

?? Let's Connect!

Are you grappling with finding the right agile approach for your team? I'd love to hear about your experiences and challenges. Drop a comment below or reach out to me directly. Together, we can explore the rich landscape of agile methodologies and find the perfect fit for your unique context. Let's make your company not just effective, but truly exceptional! ??

Remember, the goal isn't to be agile; it's to create amazing products that delight our customers. The methodology should serve that goal, not the other way around. So, let's break free from the Scrum-or-nothing mindset and embrace the full spectrum of agile possibilities!

#AgileMethodologies #OneSizeFitsNone #ScrumAlternatives #ContinuousImprovement #TechInnovation