Was it Worth It? Measuring the Success of an Agility Project in Business Terms - Ethan Ram at Agile Israel 2015
Transforming a company that is working in "traditional" methodologies to "Agile" is expensive: management attention, overcoming change resistance, cost of consultants and time spent on re-education and training. Is it worth it? Measuring success in business terms is hard but may be crucial in management buy-in into executing an Agility project. How will it improve the bottom lines? Can we expect more lines of code to be written by less developers? Can the success of an Agility project be somehow quantified? This session looks at statistics gathered in my company - R&D, QA, Support, HR and Sales have all contributed their KPI graphs - to try and answer this question. I'll be presenting some enlightening graphs of before and after a major Agility project that covered many aspects of the company operations. Trying to explain the change both in qualitative AND in quantitative measures. Hopefully, making a clear business case for going Agile.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Was it Worth It? Measuring the Success of an Agility Project in Business Terms - Ethan Ram at Agile Israel 2015
Similar to Was it Worth It? Measuring the Success of an Agility Project in Business Terms - Ethan Ram at Agile Israel 2015 (20)
More from AgileSparks
More from AgileSparks (20)
Recently uploaded
Recently uploaded (20)
Was it Worth It? Measuring the Success of an Agility Project in Business Terms - Ethan Ram at Agile Israel 2015
- 1. How to Measure Agility Project Success in Business Terms? Agile Israel 2015 Ethan Ram v1.1 © All rights reserved Want to use slides from this presentation? Ask for permission: ethanram@gmail.com
- 2. 11-Jun-15 2
- 3. Going Agile: Scrum, Kanban, CI, DevOPs 11-Jun-15 3
- 4. How to Measure? Number of code lines? Number of releases? Number of QA bugs opened? Need less support engineers? Main operations KPIs – Support queue – Fault rate Release cycle time Measure waste Employee glee Bottom lines: revenues 11-Jun-15 4
- 5. Support KPI: Open Escalations in R&D • Number of support cases pending R&D resolution 11-Jun-15 5 Agile Injection Agility Project
- 6. Support KPI: Fault Rate • Oper1 fault rate is under SLA after 2 years above 11-Jun-15 6 Agile Injection Agility Project ---- Oper1 daily/trend ---- SLA ---- Oper2 daily/trend
- 7. Waste KPI: Builds vs Deliveries • QA builds vs. Customer deliveries • Build automation reduced miss-configs by 40% • Builds per delivery down from 2.2 to 0.8 11-Jun-15 7 Agile Injection Agility Project
- 8. QA KPI: Bugs Resolution Turnaround • Avg. days to resolve a QA bug is down from ~30 days to ~15 days 11-Jun-15 8 Agile Injection Agility Project
- 9. QA KPI: Game Sign-offs per Month • Games signed-off by QA • Games titles up from 15/m to 25/m (+60%) • Game variations up from 150/m to 260/m (+73%) 11-Jun-15 9 Agile Injection Agility Project
- 10. • Game Dev Gantt 2012 – 22 weeks critical path Release Cycle Time: Game Dev. 11-Jun-15 10 Scoping Week Math Graphics HD 2 4 6 8 10 12 14 16 18 20 22 1 Graphics SD Scene layout Coding QA 6 4 2.5 8 4 4Low-spec support 4
- 11. • 2013: from 22 weeks to 12 weeks Release Cycle Time: Game Dev. Week 2 4 6 8 10 12 14 16 18 20 22 1 3 4 4 3 3 4 2 Scoping Math Graphics HD Graphics SD Scene layout Coding QA Low-spec support 11-Jun-15 11
- 12. HR: Employee Survey Dec. ’13 11-Jun-15 12 Processes and planning 57% Improved 37% Same 6% Worse Working Environment 73% Improved 25% Same 2% Worse Mar. ’13 TOP 5 DEMOTIVATORS
- 13. Revenues: Q2-12 >> Q2-13 • Customers: Up 30% • Deployed terminals: Up +26% • Headcount: no-change • Revenues: Up 14% 11-Jun-15 14
- 14. How to Measure Agility Project Success in Business Terms? Ethan Ram ethanram@gmail.com linkedin.com/in/ethanram @ethanram