Session antwerp
- 2. The team Julien Biezemans julien@agilecampustour.org @jbpros Simon Schoeters simon@agilecampustour.org @cimm Marc Lainez marc@agilecampustour.org @mlainez If you want to tweet use the hashtag #actbe
- 3. Wants to strike the game market
- 5. Guys at namco contact Bill ®
- 6. He works in a great and famous software development company, RaftingSoftware
- 7. Bill, as a project manager, commits on the requirements, with a specific deadline and therefore, a budget
- 8. Bill analyses the work that needs to be done
- 9. He goes back to his team and dispatches the work
- 10. Everyone works on his own part, and this part only
- 11. After 2 months, team says they are on track... but still nothing finished
- 12. As the deadline approaches, the team looses confidence...
- 13. Great idea from the people at namco ® Infinite grid!
- 14. Bill starts to negociate, it was not in the requirements...
- 15. The end is near... Time to put a little bit of pressure on the team... C’mon guys, we can make it!
- 16. Still not fast enough... Extra hours...
- 17. They end up finishing what was in the requirements but the client is not fully satisfied...
- 18. Bill, from his point of view, has met the requirements, the budget and the time constraints, project is a success!
- 19. That’s how Bill sees a project Negotiation Analysis Development
- 20. What’s wrong? Requirements were met after all?
- 21. A few leads... Customer is not satisfied Team didn’t have anything to say Requirements stayed rigid throughout the project Changes had to be hardly negotiated Bill dispatched the work amongst his team members Team started to work on every aspect of the application Delays could only be identified at the end of the project Team had to do extra hours Team had to take shortcuts to finish on time
- 22. Maybe you’ve already been in a situation like this...
- 23. But for namco , money is not the real issue, they ® want to try another supplier
- 24. They contact Bob from ACTic
- 25. Bob suggests that they work in iterations, but before that, what is the vision of the project?
- 26. Bob and the guys from namco then write ® user stories, all these user stories are part of the product backlog ~~~~~~~~~~~~ ~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~ In order to apply my ~~~~~ ~~~~~~~~ strategy As a player ~~~~~~~~~ ~~~~~~~ ~~~~~ ~~~~~~ I want to move pacman in ~~~~~~~~~~~~ four directions ~~~~~~~~~~ ~~~~~~~~~~~~
- 27. He asks the guys from namco to prioritize ® the user stories ~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~ ~~~~~~~~~~~~ ~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~ ~~~~~ ~~~~~~
- 28. Together, they review a few of the top user stories, and add details, to make sure the team can start working on them
- 29. They all agree, with the team on what being “done” actually means...
- 30. The team itself then estimates the user stories, Bob and the guys from namco are ® there only to answer to the team’s questions
- 31. The team tries to figure out how much work they can accomplish in one iteration
- 32. From the estimated user stories, we take the top prioritized ones that fit the team’s maximum work constrain } ~~~~~~~~~~~~ 3 ~~~~~~~~~~~~ 3 ~~~~~~~~ ~~~~~~~~ ~~~~~~ ~~~~~~ ~~~~~~~~~~~~ 5 ~~~~~~~~~~~~ 5 ~~~~~~~ ~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~ 2 ~~~~~~~~ 2 ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~ ~~~~~~~~~~ ~~~~~ 3 ~~~~~ 3 ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~ ~~~~~~~ 5 ~~~~~~~ 5 ~~~~~ ~~~~~ ~~~~~~ ~~~~~~ ~~~~~~~~~~~~ 2 ~~~~~~~~~~ ~~~~~~~~~~~~ ~~~~~~~~~~~~ 8 ~~~~~~~~ ~~~~~~ ~~~~~ 13 ~~~~~~~~ ~~~~~~~~~
- 33. They start developing the user stories, one by one
- 34. Meanwhile, Bob and the guys from namco ® are adding more details to the next user stories
- 35. When the team thinks a user story is “done”, the customer can test it and give feedback
- 36. Not satisfied? Team changes the feature right away, included the customer’s feedback
- 37. Customer has another great idea, pacman can teleport when he eats a special fruit!
- 38. No worries, Bob adds it in the product backlog, it’ll be done during the next iteration ~~~~~~~ 5 ~~~~~ ~~~~~~ In order to escape the ~~~~~~~~~~~~ ~~~~~~~~~~ 2 ghosts ~~~~~~~~~~~~ As a player ~~~~~~~~~~~~ ~~~~~~~~ 8 I want pacman to teleport ~~~~~~ ~~~~~ 13 ~~~~~~~~ ~~~~~~~~~
- 39. At the end of the iteration, the team makes a demo of what was “done” during the iteration
- 40. And they gather for a retrospective, to see how they can improve
- 41. When they reach the deadline, there are still some stories left in the backlog but the customer is fully satisfied ~~~~~~~~~~~~ 8 ~~~~~~~~ ~~~~~~ ~~~~~ 13 ~~~~~~~~ ~~~~~~~~~
- 43. A project seen by Bob Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 44. But what does it mean, “being Agile”?
- 45. Values and principles Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan http://agilemanifesto.org
- 46. AGILE SCRUM LEAN XP FDD KANBAN DSDM
- 47. Alright, but how did they do that at ACTic
- 48. Once upon a time... Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 49. Once upon a time... Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 50. Together with Bob, they defined the vision of the project On PC & MAC Replace r mi n esweepe
- 51. With the customer, Bob wrote some user stories In order to apply my strategy As a player I want to move pacman in four directions
- 52. Ok, stop, what is a user story?
- 53. In order to <business value> As a <role> I want <functionality>
- 54. With these user stories, they have built the product backlog ~~~~~~~~~~~~ ~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~ In order to apply my ~~~~~ ~~~~~~~~ strategy As a player ~~~~~~~~~ ~~~~~~~ ~~~~~ ~~~~~~ I want to move pacman in ~~~~~~~~~~~~ four directions ~~~~~~~~~~ ~~~~~~~~~~~~
- 55. They then prioritized these stories by business value ~~~~~~~~~~~~ ~~~~~~~~ ~~~~~~ ~~~~~~~~~~~~ ~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~ ~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~ ~~~~~ ~~~~~~
- 56. They defined, together with the development team, what “done” means
- 57. What do we tackle by doing that? Customer is not satisfied Team didn’t have anything to say Requirements stayed rigid throughout the project Changes had to be hardly negotiated Bill dispatched the work amongst his team members Team started to work on every aspect of the application Delays could only be identified at the end of the project Team had to do extra hours Team had to take shortcuts to finish on time
- 58. Where can you find more information?
- 59. What next? Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 60. What next? Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 61. Bob asked his team to estimate the complexity of the user stories in story points
- 62. Bob asked his team to estimate the complexity of the user stories in story points
- 63. Bob asked his team to estimate the complexity of the user stories in story points
- 64. Bob asked his team to estimate the complexity of the user stories in story points 1/200
- 65. Bob asked his team to estimate the complexity of the user stories in story points ~~~~~~~~~~~~ ~~~~~~~~ 3 In order to apply my 3 ~~~~~~ ~~~~~~~~~~~~ 5 strategy ~~~~~~~ ~~~~~~~~~~~ As a player ~~~~~~~~ 2 I want to move pacman in ~~~~~~~~ ~~~~~~~~~~ four directions ~~~~~ 3 ~~~~~~~~ ~~~~~~~~~ ~~~~~~~ 5 ~~~~~ ~~~~~~ Handle 4 Build grid directions, north, south, east, west Implement controls
- 66. Using planning poker http://www.planningpoker.com/
- 67. The team was then asked to estimate its velocity 13 ~~~~ ~ ~~ ~ ~~ ~~~~ ~ ~~ ~~~~ ~~~ ~~~~ ~~~~ 8 ~~ ~~~~ ~~ ~~ ~~~ ~~~ ~~~~~ ~~~ ~~~~~ ~~~~ 18 ~~~ 3 5 ~~ ~~ 8 ~~ ~~ ~~~ ~ ~~ ~~~ ~~~~ ~~~ ~~ ~~ ~~ ~~ ~~ ~~~ ~~~ ~~~~~ ~~ ~ ~~ ~~ ~ ~~~ ~~~ 3 ~~~ ~~~~ ~ ~~~~~ ~ ~~~ ~~~~ ~ ~~~ ~ ~~~~~~ ~~ ~~~ ~ 2 ~ ~~~~~~ ~~ ~~ ~~~ ~~~~ ~~ ~~~ ~~~ ~~ ~~ ~~ ~~~~ ~~~ ~~ ~~ ~~ ~~ ~ ~~~~ ~ 5 ~~ ~~ ~~ 2
- 68. How many can you eat in 1 minute?
- 69. How many can you eat in 1 minute?
- 70. How many can you eat in 1 minute?
- 71. How many can you eat in 1 minute?
- 72. How many can you eat in 1 minute?
- 73. How many can you eat in 1 minute?
- 74. How many can you eat in 1 minute?
- 75. How many can you eat in 1 minute?
- 76. How many can you eat in 1 minute?
- 77. How many can you eat in 1 minute?
- 78. How many can you eat in 1 minute?
- 79. How many can you eat in 1 minute?
- 80. How many can you eat in 1 minute?
- 81. How many can you eat in 1 minute?
- 82. How many can you eat in 1 minute?
- 83. Based on that velocity, Bob built the iteration backlog } ~~~~~~~~~~~~ 3 ~~~~~~~~~~~~ 3 ~~~~~~~~ ~~~~~~~~ ~~~~~~ ~~~~~~ ~~~~~~~~~~~~ 5 ~~~~~~~~~~~~ 5 ~~~~~~~ ~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~ ~~~~~~~~ 2 ~~~~~~~~ 2 ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~~ ~~~~~~~~~~ ~~~~~ 3 ~~~~~ 3 ~~~~~~~~ ~~~~~~~~ ~~~~~~~~~ ~~~~~~~~~ ~~~~~~~ 5 ~~~~~~~ 5 ~~~~~ ~~~~~ ~~~~~~ ~~~~~~ ~~~~~~~~~~~~ 2 ~~~~~~~~~~ ~~~~~~~~~~~~ ~~~~~~~~~~~~ 8 ~~~~~~~~ ~~~~~~ ~~~~~ 13 ~~~~~~~~ ~~~~~~~~~
- 84. What do we tackle by doing that? Customer is not satisfied Team didn’t have anything to say ++ Requirements stayed rigid throughout the project Changes had to be hardly negotiated Bill dispatched the work amongst his team members Team started to work on every aspect of the application Delays could only be identified at the end of the project Team had to do extra hours Team had to take shortcuts to finish on time
- 85. Where can you find more information?
- 86. What now? Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 87. What now? Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 88. Every morning they gathered in front of the team board Blue Stories TODO WIP(4) DONE ~~~~~~~~~~~~3 ~~~~~~~~ Name ~~~~~~~~~~~~5 ~~~~~~~ ~~~~~~~~ 2 ~~~~~~~~ Mis ~~~~~ 3 ~~~~~~~~ ~~~~~~~ 5 ~~~~~
- 90. During a “daily standup” Blue Team Stories TODO WIP(4) DONE ~~~~~ 3 Name tags ~~~~~ 5 ~~~~~ 2 Misc. ~~~~~ 3 ~~~~~ 5 3 ways the brain creates meaning
- 91. Team members worked by pair
- 92. 1 keyboard 1 mouse
- 93. 2 keyboards 2 mice
- 95. 2 claviers 2 souris 2 écrans (mirroring)
- 96. They also organized code reviews
- 97. They wrote tests
- 98. They wrote tests Before the code...
- 99. After you have a written test
- 100. You write the minimal amount of code to make it pass
- 101. You “refactor” the code
- 102. If there is a regression identified, some test will fail
- 103. During that time, the customer and Bob have detailed some more user stories
- 104. It’s like...
- 105. Each time the team thought they had “done” something, the customer could test
- 106. Last but not least... Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 107. Last but not least... Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 108. At the end of each iteration, the team members presented everything that was “done” during the iteration
- 109. The customer “accepted” all “done” user- stories
- 110. And what was accepted was ready to be shipped in production
- 111. After the demo, Bob’s team organized a retrospective to improve the way they work
- 112. What do we tackle by doing that? Customer is not satisfied Team didn’t have anything to say ++ ++ ++ Requirements stayed rigid throughout the project Changes had to be hardly negotiated Bill dispatched the work amongst his team members Team started to work on every aspect of the application Delays could only be identified at the end of the project Team had to do extra hours Team had to take shortcuts to finish on time
- 113. Where can you find more information?
- 114. Celebrate!
- 115. And Iterate...
- 116. Until there is no $$$ left
- 117. Or before, when the client is satisfied
- 118. After the very last iteration, the last demo
- 119. And a project wide retrospective
- 121. What do we tackle by doing that? Customer is not satisfied Team didn’t have anything to say ++ ++ ++ Requirements stayed rigid throughout the project Changes had to be hardly negotiated Bill dispatched the work amongst his team members Team started to work on every aspect of the application Delays could only be identified at the end of the project Team had to do extra hours Team had to take shortcuts to finish on time
- 122. Where can you find more information?
- 123. And... Celebrate!
- 124. Bob’s team is now ready for a new project
- 125. Blu Week Day Sto TO WI D ~ Na rie D P O ~ s O (4) NE Mi ~ ~ ~
- 126. More readings?
- 127. If you want more, ask us!
- 128. Questions? @agilecampustour http://agilecampustour.org