The document discusses the differences between home cooks and professional chefs, highlighting that professional chefs regularly taste their dishes, whereas home cooks may not. It emphasizes the importance of feedback in both cooking and agile software development, mentioning that effective feedback loops can improve processes. The document also touches on the exponential cost of changes during the development cycle, advocating for shorter feedback loops in agile practices.

1. Question:
What is the difference between a
home cook and a professional
chef?
Tuesday, March 5, 13

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 - Famous American chef]
Tuesday, March 5, 13

3. Feedback
The Secret Ingredient
Of success
Elad Sofer - Agile coach
www.practical-agile.com / @eladsof /
elad@practical-agile.com
Tuesday, March 5, 13

4. What

5. is

6. Feedback

7. ?
• The supply of an input to some
process or system as a function
of its output
4
Tuesday, March 5, 13

8. What

9. if...
• There was a 30 second delay between
pushing the breaks, and your car
responding?
• There was a 10 minutes delay between
responses in a conversation?
• There was a 15 second delay between
pushing the button and this bullet
appearing? :)
5
Tuesday, March 5, 13

10. Late

11. Feedback

12. Is

13. Useless!
6
Tuesday, March 5, 13

14. How

15. does

16. a

17. chef

18. work?
7
Tuesday, March 5, 13

19. Agile is all about Shrinking
the feedback loop
[Corey Haines - Software craftsmen]
Tuesday, March 5, 13

20. Question:
How feedback loops are
different In agile
software development
process?
Tuesday, March 5, 13

21. Agile

22. Development

23. Practices
Tuesday, March 5, 13

24. Code

25. Review

26. Feedback

27. Loop
Tuesday, March 5, 13

28. Code

29. Review

30. Feedback

31. Loop
12
Tuesday, March 5, 13

32. Bug

33. Feedback

34. Loop
Tuesday, March 5, 13

35. Bug

36. Feedback

37. Loop
Tuesday, March 5, 13

38. Build

39. status

40. Feedback

41. Loop
Tuesday, March 5, 13

42. Build

43. status

44. Feedback

45. Loop
Tuesday, March 5, 13

46. Agile

47. Feature

48. Management
Tuesday, March 5, 13

49. Requirement

50. Feedback

51. Loop
Tuesday, March 5, 13

52. Feature

53. Progress

54. Feedback

55. Loop
Tuesday, March 5, 13

56. Feature

57. Progress

58. Feedback

59. Loop
Tuesday, March 5, 13

60. Feature

61. Progress

62. Feedback

63. Loop
Tuesday, March 5, 13

64. Agile

65. Project
Management
Tuesday, March 5, 13

66. Regression

67. Feedback

68. Loop
Tuesday, March 5, 13

69. Regression

70. Feedback

71. Loop
Tuesday, March 5, 13

72. Improvement

73. Feedback

74. Loop
Tuesday, March 5, 13

75. Improvement

76. Feedback

77. Loop
Tuesday, March 5, 13

78. Summary
Tuesday, March 5, 13

79. Tuesday, March 5, 13

80. The cost of changes increases
exponentially the farther
along you are in the
development cycle
[Dr. Barry Boehm]
Tuesday, March 5, 13

81. cost

82. of

83. bugs
Tuesday, March 5, 13

84. cost

85. of

86. bugs
D !
T E
DA
U T
O
Tuesday, March 5, 13

87. The

88. big

89. Picture
Tuesday, March 5, 13

90. Agile is all about Shrinking
the feedback loop
[Corey Haines - Software craftsmen]
Tuesday, March 5, 13

91. Agile is all about
Having Many Short
Fast Nested
Fe e d back lo o p s
that are simple to learn
from Text
Tuesday, March 5, 13

92. Don't

93. simply

94.
“Shrink”

95. the

96.
feedback

97. loop
Tuesday, March 5, 13

98. Improve

99. The

100. Feedback

101. Loop
• Pair Programming • Having daily meetings.
• Unit testing TDD. • Using Burn-Down
• Doing testing Inside charts.
the team. • Running Automatic
• Running Automatic test process.
build process. • Doing Retrospectives.
• Working in short • KPIs at the right
Iterations. level.
• Using BDDATDD
35
Tuesday, March 5, 13

102. Thank

103. you
Any
Questions ?
Elad Sofer - Agile coach
www.practical-agile.com / @eladsof /
elad@practical-agile.com
Tuesday, March 5, 13