Download - SAFe vs Spotify, le match ! - ScrumDay 2015
SOMMAIRE Documentation Organisation Taille critique Formation REX Respect de la culture Technique Impacts Résultats
http://www.scaledagileacademy.com
http://www.scaledagileframework.com
Dean Leffwingwell
1
2
Publications :Scaling Agile @ Spotify
How Spotify builds products
Vidéos :Spotify Engineering Culture part 1 & 2
Slides :Agile @ Scale
Scrum = ?How to run an unconference
What is an Agile Tester ?
Principales ressources
Spotify Labslabs.spotify.com
Crisp’s Blogblog.crisp.se
Principal sources
Principal auteur
Henrik Kniberg
Spotify:0
SAFe:1Accessible
Simple… trop simpleDocumentation faible et trop éclatée
ExhaustivitéExplication pour tout
Du concret pour déployer
Lourdeur Pas adaptatif
Trop hiérarchique Quelle place pour l’auto-organisation?
CE QUE L’ON EN PENSE
Lourdeur Pas adaptatif
Trop hiérarchique Quelle place pour l’auto-organisation?
CE QUE L’ON EN PENSE CE QU’IL PROMEUT
Meddley de l’agilité Scrum SoS
Kanban Train de Release
WIP et variabilité pour innover Auto-organisation
Slack Sprint d’innovation
Leadership pour développer les individus
Lean Thinking Gestion Budget
Intégration du top management
LE MANIFESTE SPOTIFY« Agile à la Spotify (the skinny) »
CONTINUOUS IMPROVEMENTAt Spotify, part of my work is to look for ways to continuously improve, both
personally, and in the wider organisation.
ITERATIVE DEVELOPMENTSpotify believes in short learning cycles, so that we can validate our assumptions as
quickly as possible.
SIMPLICITYScaling what we do is key to Spotify’s success. Simplicity should be your guidance
during scaling. This is as true for our technical solutions, as for our methods of working and organising the organisation.
TRUSTAt Spotify we trust our people and teams to make informed decisions about the way
they work and what they work on.
SERVANT LEADERSHIPAt Spotify managers are focused on coaching, mentorship, and solving impediments
rather than telling people what to do.
LES 34 GRANDS PRINCIPES :1. Cross-pollination > Standardization2. Internal Open-source model3. Small & Frequent releases4. Decoupled releases5. Agile > Scrum6. Principles > Practises7. Servant > Master8. Autonomous Squads9. Loosely coupled, Tightly aligned
Squads10. Self-service model : Enable > Serve11. Community > Structure
12. Focus on Motivation13. People > ALL14. Trust > Control15. Release trains + Feature toggles16. Continuous improvement17. Impact > Velocity18. You are the culture19. Lean Startup20. Fail friendly environment21. Failure recovery > Failure avoidance22. Innovation > Predictability
23. Value delivery > Plan fulfillment24. Culture-focused Roles25. Healthy culture heals Broken Process26. Limited Blast Radius via Decoupled
Architecture and Gradual Rollout27. Experiment-friendly Culture28. Hack Time29. Hack Week30. Minimize the need for Big Projects31. Definition of Awesome32. Waste-repellent Culture33. Chaos > Bureaucracy
The place to be!Agile CompliantTrop beau???
Paradoxe :Vraie culture Agile
Mais rouleau-compresseurMaturité Agile nécessaire
Spotify:1
SAFe:0
Rôle architecte Architecture découplée Architecture emergente Spike
Intégration continue Tests automatisés BDD Feature Flipping
Déploiement continu DevOps Refactoring Pair Working…
Spotify laisse les équipes trouver leur propre cheminSAFe apporte directement le cadre des bonnes pratiques
Spotify:1
SAFe:1
A grands pouvoirs, grandes responsabilités!ATTENTION : des impacts forts à tous les étages!Peut-on faire du Spotify ailleurs que chez Spotify?
Peut-on vraiment implémenter SAFe jusqu’au bout?
Spotify:1
SAFe:1
Spotify6
SAFe5
Beaucoup les sépare :Produit vs Flux de valeur Culture vs Objectif final
REX vs Framework Partage vs Business