Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Wastful waste or why everything is so slow in development

219 visualizaciones

Publicado el

I think almost everybody experienced cases when things are moving very slowly in IT companies or teams. You have many people, talented engineers, Agile process and development speed is still below expectations. We try to focus on performance and efficiency last 10 years, improving our practices and tools. But we are still there in terms of speed when they are applied to real life cases. How is it possible? In this talk we will review the concept of waste circles and understand what are the main sources of time waste in development process. This concept would help you to check your processess, focus on right things and achieve much better results in your organization or team.

Publicado en: Tecnología
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Wastful waste or why everything is so slow in development

  1. 1. Wasteful waste or why everything is so slow in development Mikalai Alimenkou @xpinjection http://xpinjection.com
  2. 2. Telegram channel https://t.me/xpinjection_channel
  3. 3. Disclaimer This talk is based on personal experience
  4. 4. What is our performance?
  5. 5. Let’s tune our Agile process!
  6. 6. No good metrics for performance
  7. 7. Customers always want… New features ASAP!
  8. 8. It’s impossible to understand if performance limit is reached
  9. 9. Big team is not always effective
  10. 10. Top performance mode
  11. 11. Developers have different focus factor
  12. 12. Definitely great source of improvements
  13. 13. Waste Circles: another view on waste Your performance Technical waste Team waste Process waste Organizational waste
  14. 14. Stories about organizational waste Bad coffee Global meetings and corporate discussions Lunch time Bureaucracy
  15. 15. Typical meeting structure Get out of work context Waiting Useful part Discussions and relax Get into work context 15 minutes 30-40 minutes
  16. 16. • Planning (4 hours) • Grooming (2 hours) • Daily Scrum (20 minutes) • Retrospective (1 hour) • Demo and Sprint Review (2 hours) Waste % = 12.3/80 ~ 15.5% Process waste
  17. 17. Stories about team waste Communication CI/CD Additional roles Conflicts
  18. 18. Stories about technical waste Technical debt Code review Bad tools Defects
  19. 19. Let’s calculate your performance, bro! Focus factor = 0.7 [ideal] * (1 – OrgWaste) * (1 – ProcWaste) * (1 – TeamWaste) * (1 – TechWaste) For some large teams in ineffective organizations actual FF ~ 0.1-0.2 for ALL TEAM MEMBERS
  20. 20. Summary • Focus on waste analysis instead of performance tuning • Start from waste with maximal impact • Don’t add waste continuously through your process • Monitor waste level with right metrics • Adopt focus factor based capacity planning • Use product increment as the only performance metric
  21. 21. Some books on this topic
  22. 22. @xpinjection http://xpinjection.com mikalai.alimenkou@xpinjection.com

×