agile_lean_it
0 likes751 views
This document discusses how an IT organization at a company called Adform scaled up from 2 people to over 600 people while adopting Agile and Lean principles. Some key changes included: 1) Splitting into dedicated teams focused on different services like development, operations, etc. This replaced the previous "creative chaos" structure. 2) Implementing Scrum, Kanban and other Agile practices to manage the work and facilitate continuous delivery with over 20 deployments per day. 3) Shifting to a culture where teams took responsibility for their own services and metrics rather than having a centralized operations group. Automation and platforms were used to support this. 4) Evolving the procurement process to be
agile_lean_it
- 1. Agile, Lean and IT www.agilemindstorm.com @ruckiand From 35 to 600+ www.adform.com
- 3. # of IT people: 2 -> 23 +6 business offerings # of developers: 25 -> 280
- 4. 20+ deployments per day 1 mln. reqs per second <100 ms 1 PB of data 2000+ servers
- 5. Agile and Scrum Build process that works Deliver early and adjust Find your pace
- 6. Lean and Kanban Manage value delivery flow Manage queues and bottlenecks Eliminate waste in your flow
- 10. #2 Scrum in da House
- 11. ITPM DEV Scrum team Scrum team CS Sales Push
- 12. Challenges popped up as # of people increased Micro changes vs Batches IT scope enormous, but 5 people Increased # of dependencies Automation vs Manual
- 13. #1 Deployment
- 14. ITDEV Scrum team Scrum team 1 release manager Release day Rollbacks Exceptions Measure Hot fixes Rollbacks fail Lack of knowledge Complex Manual work
- 15. ITDEV Scrum team Scrum team Deployment platform: custom No rollbacks Measure product quality, not exceptions Delegate
- 17. ITDEV Scrum team Scrum team OnDuty Setting up KPIs Reaction Exceptions Need to involve devs but feature not working Server up Micro changes are too fast
- 18. ITDEV Metrics platform: zabbix graphite grafana bosun Scrum team Scrum team Teams are responsible for their SLAs 3d party 24/7
- 20. ITDEV Scrum team Scrum team Configuration Troubleshooting Queues of developers Distraction long resolution time Manual work
- 21. ITDEV Scrum team Scrum team Access platform: sit.adform.com Access to prod given Personalised accounts Configuration automation Config platform: puppet
- 22. #4 Procurement
- 23. ITDEV Scrum team Scrum team Batching: office and prod Costs optimisation CTO HW #1 #2 #3 #4 deliver #5 #4.1 Negotiation during purchase #1.1 Custom HW
- 24. IT DeV CTO #1 deliver ALL #1.1 stock contracts configs: S, M, L, XL, XXL #2 Office stock contractsdeliver On demand
- 25. Evolution Lean Adapt to business needs Permanent change Agile Growth Competition
- 27. What has changed for IT? Structure Culture and not only
- 28. Services DevOps DC Virt Security 2. Service catalogue Structure 1. Split into areas with dedicated people PMDev CS Ops 3. Ops in teams
- 30. Important I think following is very for any service unit
- 31. Imagine you have to earn money shifts your thinking away from cost center
- 33. Say No Control scope Be explicit about what you can do
- 34. Monitoring and Transparency Best way to control
- 36. Grow you process evolution vs adoption
- 37. Know value flow Local efficiency is not what you need
- 38. www.agilemindstorm.com @ruckiand Credits to my team for bringing these ideas to life Questions ? www.adform.com