The document discusses the differences between home cooks and professional chefs, as well as differences in feedback loops between agile software development processes and traditional processes. It notes that chefs receive constant feedback while cooking that allows them to adjust their dish, unlike home cooks who just follow recipes without tasting. For software development, it describes how agile processes have much shorter and more frequent feedback loops at various levels compared to traditional processes, such as having code reviews that take minutes instead of days and unit testing that provides feedback in minutes rather than weeks. Keeping feedback loops short, frequent, and at multiple levels is key to success with agile methods.

1. Question: What is the difference between a home cook and a professional chef?

2. The biggest difference between home cooks and professional chefs is that home cooks don't taste the dish often enough as they prepare it. They just follow the recipe step-by-step, without getting that feedback along the way. [Wolfgang Puck – chef – Owns 20 restaurants]

3. The Secret Ingredient Of success Feedback

6. Late Feedback Is Useless!

7. The cost of changes increases exponentially the farther along you are in the development cycle [Dr. Barry Boehm]

8. How does a chef work?

9. Agile is all about Shrinking the feedback loop [Corey Haines]

10. Question: What is difference of feedback loops in agile software development process?

11. Agile Development Practices

12. Code Review Feedback Loop Developer / TL Developer Several days

13. Code Review Feedback Loop Several minutes Development pair

14. Bug Feedback Loop Release Integrator Developer Bug tracking System QA Team leader between 1 week and 1 month

15. Bug Feedback Loop Developer 3 to 10 minutes 1 to 3 days QA Unit test

16. Build status Feedback Loop SCM system Developer QA Release integrator Bug tracking System between 1 day and 2 weeks

17. Build status Feedback Loop SCM system Developer between 5min and 1 hour CI Server

18. Agile Feature Management

19. Requirement Feedback Loop Marketing System Team leader Between 3 month and 1 year Customer Developer

20. Requirement Feedback Loop Customer Product Owner between 1 to 4 weeks Developer Acceptance tests up to 3 days

21. Feature Progress Feedback Loop Team Leader Developer Project Manager Tool Plan between 1 week and 1 month

22. Feature Progress Feedback Loop Developer Max. Daily Max. Daily Task Board & Burn down Rest of the Team Plan Max. Sprint length

23. Agile Project Management

24. Regression Feedback Loop SCM system Developer QA Release integrator Bug tracking System between 1 week and 2 month

25. Regression Feedback Loop SCM system Developer between 30min and 6 hours CI Server

26. Improvement Feedback Loop Team Leader Developer Project Manager Lessons Learned QA Once per release Not enough testing

27. Improvement Feedback Loop Developer Project Manager QA Once per sprint Retrospective

28. Keep It Simple

29. Summary

30. Let’s Look At The big Picture Development Practices level Feature level Project level

31. Success is about: Feedback loops Nested Short Fast Many Having

32. Shrink The Feedback Loop

34. Thank you Any Questions ? Elad Sofer - Agile coach www.theScrumster.com / @ eladsof / elad.sofer@gmail.com