A Story of Cultural Transformation at OLX
11 likes1,805 views
Case Study of a Cultural Transformation towards Agile. Presented in Scrum Gathering in Johannesburg - October 2015
A Story of Cultural Transformation at OLX
- 1. A Story of Cultural Transformation at OLX October 2015 Dami叩n Buonamico Scrum Gathering Johannesburg - 2015
- 2. True Story
- 3. Dami叩n Buonamico Information Systems Engineer Buenos Aires @dbuo Organisational Agile Coach
- 4. Argentina
- 5. Whats OLX Monthly Active Users + 250,000,000 New Monthly Listings + 25,000,000 The Largest Online Classifieds Company in the World
- 6. Employees + 1200 Offices + 20 BA HQ 280
- 8. Architecture
- 9. Android iOS Mobile Web Mobile Team Web Core QA UI Designers BI PO Mobile API SEO Infr Silos Departments CTO Dev ManagerDev Manager
- 10. Conways Law Software architectures will reflect the structure of the organization that built them - Melvin Conway (1968)
- 11. 意鞄顎壊.
- 12. 意鞄顎壊. Inconsistencies Defects Local Optimisation Delays Lack of Collaboration Conflicts Dependencies Frustrations
- 13. Apply Conways Law Key Learning Flexible organizations are willing to re-organize to produce an optimal design. @dbuo
- 14. All Started
- 15. In a Small Team
- 16. Agile Principles Agile Values Scrum Values Ground Rules Core Values Frequent Delivery Sustainable Pace Close cooperation Self-Organizing Adaptation to change Face-to-face communication Simplicity Collaboration Commitment Focus Openness Respect Courage Test assumptions Share relevant information Valid Information Empathy Informed Choice Strong Culture
- 17. Cumulative Flow (for a single Sprint) Motivated to Improve
- 18. Fully Scrum
- 19. Scope of Action TeamManagers Stakeholders Organisational Processes Other Teams / Departments CULTURE Sub-Culture Scope
- 20. Key Learning For an Agile Team to thrive A fertile context is required @dbuo
- 21. 10X
- 22. Key Learning If you want a performing team Cultural Fit is equally or more important than skills @dbuo
- 23. The Results
- 25. Demo
- 26. We Went Public
- 27. Demo as a Driver Measure of Progress Extra Motivator to Deliver Feedback, Celebrate, Share Incremental Product Exposure
- 28. Key Learning The Demo is one the Most Powerful Drivers for Agile Adoption @dbuo
- 29. Breaking Silos
- 30. Transition Period Meantime strategyInitial situation Long-term strategy S o l r DB ABL S A L FP Asyn Proc SMAUG SMSMSMSM SMSMSMSMSM SM
- 31. Expeditions Teams Stable Packs1 3Packs V 1.02 Learning Process
- 33. EPICS 1._______ 2._______ 3._______ EXPEDITION 1 _._______ _________ _________ _________ EXPEDITION 2 _________ _________ _________ _________ EXPEDITION 3 _________ _________ _________ _________ EXPEDITION 4 _________ _________ _________ _________ Requests Weekly Master Backlog Session (CPO) Ad-Hoc Staffing Weekly Sprints Centralisation of Product Priorities Master Product Backlog (MPB)
- 34. Ad hoc staffing 11 Expeditions
- 35. Expedition Teams Broke silos Alignment Collaboration Priorities Control Centralisation No Real Teams Bottlenecks In Retrospective Staffing Overhead
- 36. Packs Teams (v1) Mission + KPI 5 Teams Iteration 2
- 38. Trainings Coding Standards Reduce Technical Debt Take care of Health Dimensions System Owners
- 39. Health Dimensions Continuous Delivery, Automated Testing Monitoring, Metrics, Logging Caching, Scalability Documentation Fault Tolerance Security
- 40. Stable Teams Effectivity Cross-Functional Communication Scrum Master not Master in Scrum Method Imposition Parallel Development In Apps In Retrospective Packs Teams
- 41. Stable Packs Teams Iteration 3 Better Context Long-Term Smaller Size: 4-5
- 42. Onboarding Inventory Negotiate Search Monetisation Communications Support QA DevOps SCRUM SCRU M QA QA DesignBI QA Has a QA SCRUM Has Scrum Master / Scrum Process Why Tech Leads (TL) ? TL System Owners (Apps) Weekly
- 43. Mon MonTue Wed Thu Fri Tue Wed Thu Fri Demo Planning BACKLO G PLANNING RETRO Daily Meeting RETRO ANDROID RELEASEiOS RELEASE BACKLO G BACKLO G PLANNING PLANNING PLANNING PLANNING Autonomy in Process
- 44. Demo? of Course! Q & A Feedback Every 2 Weeks
- 46. Stable Packs Teams Motivation Getting Better The Big Picture Autonomy vs Alignment Parallel Development In Apps In Retrospective Stability Small Teams = Less overhead
- 47. Key Learning Small and stable teams with proper context perform the best @dbuo
- 48. Summary
- 49. 1. Conways Law How do you Apply the Conways Law.
- 50. 2. Fertile Context For an Agile Team to thrive A fertile context is required.
- 51. 3. Cultural Fit If you want a performing team Cultural Fit is equally or more important than skills
- 52. 4. Demo The Demo is one the Most Powerful Drivers for Agile Adoption
- 53. 5. Smaller Teams Small and stable teams with proper context perform the best
- 54. Thank you Dami叩n Buonamico @dbuo 臓 GRACIAS !