Agile at Salesforce From theory to practice, how to be agile at scale
11 likes3,829 views
The document outlines Salesforce's journey to adopting Agile methodologies and principles, demonstrating how they established a scalable Agile culture through frameworks like Scrum and Kanban. Key to their approach is the Adaptive Delivery Methodology (ADM), which emphasizes respect for people, eliminating waste, and delivering quality. Additionally, it highlights practices such as continuous planning, iteration, and the importance of metrics and communication in supporting over 400 Agile teams across Salesforce.
Agile at Salesforce From theory to practice, how to be agile at scale
- 1. Agile at Salesforce From theory to practice, how to be agile at scale Pierre-Yves “pitch” Chevalier Christophe Mourot Director Search Engineering Lead Quality Engineering [email protected] [email protected]
- 2. MOST INNOVATIVE COMPANY IN THE WORLD Salesforce is the 6th Largest Software Company in the World 2013 • 2014 • 2015 2008 • 2009 • 2010 2011 • 2012 • 2013 2014 • 2015 2011 • 2012 2013 • 2014 $1.51B FY16 Q1 Revenue 16K Employees ONE OF THE BEST WORKPLACES FOR MILLENNIALS 2015
- 3. Leveraging Solr to provide search across Salesforce Products Search for the World’s Most Trusted Enterprise Cloud Documents / day~6B Enterprise Security High Availability / Disaster Recovery Performance at Scale Structured & Unstructured Data Machine Learned Relevance 2.8 Petabytes Indexed Data (HA, DR, Replicas) 1.25B+Queries / day
- 4. The journey to Agile
- 5. In the Early Days… • Delivering consistently • Easy with everyone in same office • No hand-offs • Clear communication
- 6. Incredible Growth Higher Transaction Volume Larger R&D Org Unpredictable Releases Fewer Features Processes needed to scale Jump to 2006…
- 7. 2000 2001 2002 2003 2004 2005 2006 Features Delivered per Team Days between Major Releases Time in between major releases increased
- 8. Is an Agile discipline and culture specific to Salesforce. Is built upon lean principles. Is guided by the agile manifesto. Employs scrum and kanban frameworks to manage work. Includes certain extreme programming (xp) technical practices. Adaptive Delivery Methodology (ADM) was the Solution
- 9. ADM Principles Respect people Eliminate waste Create knowledge Build quality in Deliver fast Optimize the whole Just in time decisions 7 ADM Principles are the Foundation of our Agility
- 10. 2007 2008 2009 2010 2011 2012 2013 Features Delivered per Team Days between Major Releases ADM Enables 3 Predictable Major Releases a Year
- 11. +400 Agile Teams @ Salesforce We’ve Built a Scalable Model
- 12. Vision V2MOM 2 Release Review 1 Release Review Sprint Daily Continuous Planning & Prioritization at Every Level Spring Summer 3-5 Years 1 year R1 2 Releases 1 Release ~ 2 Weeks Daily Vision Values Method Obstacles Metrics
- 14. Daily Health check Strong Attention to Metrics Release Health Monitoring • Dedicated Release Management team • Daily Health check view • Weekly Review of releases • Continuously release-able dashboard • Feature Freeze tracking dashboard • Release Freeze tracking dashboard
- 15. Stop the code line when test failures are too high
- 17. Lessons Learned
- 18. ADM enables Innovation Agile practices empower teams to experiment - ADM sets the general principles, teams are free to execute in that context, don’t forget the global safety net, not a free pass for no process Iterative development delivers new ideas every release - makes it harder to go after long-term, risky new features Debt free development enables powerful agility and high quality - not all teams are mature enough. Bad citizen (teams) are locked out of the SCM system until issues get resolved Just-in-time Decisions – release sign-off and patch decision made at team level - optimize for speed (slight duplication of effort is OK)
- 19. Additional Tips ▪ Distributed Teams – It does work :-) – Need to compromise – don’t go by the book – Over-communication is key and video is your friend ▪ Scrum of Scrums – Vital to connect autonomous teams – Scrum master and product owner as proxy for the team ▪ Release Planning at Team Level – 3 times per year – Interesting mix of spike work (technical investigations) and business priority – Very short / almost too aggressive on purpose – Dependencies
- 20. Agile at Salesforce AUTONOMOUS TEAMS BE PRAGMATIC, STAY AGILE ONE TOOL TO RULE THEM ALL NO FREE PASS ON QUALITY TRUST IS OUR NUMBER ONE VALUE COMMUNICATE COLLABORATE
- 21. Questions
- 22. thank y u