The document describes a game to introduce scrum concepts through planning a dinner party. Key scrum artifacts and roles are discussed through exercises where participants estimate tasks and prioritize product backlog items for the party. Participants estimate the effort for tasks like grocery shopping and cleaning. They use planning poker to refine estimates and divide large items into tasks with hour estimates. Velocity is calculated and prioritization is discussed to plan which items can be completed in the upcoming sprint while managing risks. The scrum master handles changes and delays to keep the sprint on track.

1. The Dinner A game for introducing scrum

2. Objectives Present scrum artifacts Discuss practices

3. The set Party Initiation

4. Before we can start working

5. A dinner, that means… All: Write down the three things that are needed for a successful dinner

6. What is a dinner? Type A birthday party (child, adult) Wedding dinner Special occasion dinner Family dinner Dinner for friends Other questions How many participants What needs to be fixed/ what do we have

8. Can we all decide? What is most important is an individual priority. When (which is often) we cannot come to a common decision, someone needs to decide.

9. The Product Owner A single, wringable neck Makes the priority list Makes sure that all items to be prioritized are included on the list of things needed to do Decides WHAT, but not HOW

10. We’re having a dinner Ed says: I’ve decided that we’re giving a dinner How much time will it take for you to fix that? All: Write down an estimate of how much time you think it takes

11. Project Objective Not actually a scrum artifact Needed to make sure that everyone knows what the objective is Even a common term as “party” means very different things to different people

12. How to write a Project Objective Commander’s intent If we’ve done nothing else during the project, we’ve at least done [Objective] Moore’s Product vision template For (target customer) Who (statement of the need or opportunity) The (product name) is a (product category) That (key benefit, compelling reason to buy) Unlike (primary competitive alternative) Our product (statement of primary differentiation)

13. The dinner objective The objective is to on next Friday host a family dinner for eight at Ed’s place. There will be two kids (ages 5 and 6), who need to have a dinner and to entertain themselves afterwards

14. The estimate of project size Ed says: Ok, how long will it take you to be done? All Write down how long it will take to make all the preperations

15. Estimate project size Impossible to give these estimates How many will work on the project Who will work on the project What do we have at home What do we want on this party How much other stuff will be done …

16. The Team All people who will perform work which leads to completing the items on the product backlog Is responsible for the estimations

17. Giving a relative answer Ed says: Ok, is it harder than the wedding we organized? OK, is it harder than the lunch we had for the next door neighbors last week? All: Write down the relative difficulty of this party, a wedding and a dinner for four people

18. Story point Presenting a relative estimate results in a more accurate answer Better as things, teams and people change Still gives an idea of size Template version of Fibonacci sequence

19. Estimating using story points Use a Golden list (one achieved item per number) 0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100. Compare all items to the golden list and give the number of the golden list item which best matches the new item

20. Golden list Not a scrum artifact A list of example product backlog which all can relate to One example per number which can be used for estimation During estimation, all new items are compared to items on golden list

21. A todo-list All: Write down all the things you would need for the party

22. The Product Backlog To meet an objective, you need a list of smaller objectives needed to be met All these steps are part of the product backlog But to make it work, we need to know size and priority

23. The product backlog estimation All: Estimate relative size of Product backlog items Food Drinks Entertainment for kids Cleaning Getting ready on the event

24. Ok, back to estimates You sometimes need to be very specific to make an estimate How estimate “Food”?

25. Do you know enough to make an estimate? All: Estimate how long it will take for the person to your right to prepare a dinner table for this party

26. Planning poker Not a scrum artifact Method for estimating All shows estimate Lowest estimate debates highest Steps 1-2 are repeated until all can agree on an estimate

27. The product backlog estimationtake 2 Use Planning poker to estimate: Buy all ingredients for three course dinner Buy wine, beer, mineral water, soft drinks Clean bathroom, living room & kitchen Buy new Nintendo Wii game Buy new clothes to Ed Getting clothed before dinner Prepare welcome drinks Prepare dinner table Prepare dinner

28. But what is important on the todo-list? All: Prioritize the different items on the list If you take the perspective of the kids; does your priority look different? How much does the size affect the priority? Exercise

29. Product planning meeting Identifying product backlog items Estimating items Giving input on priority/ get priority from product owner

30. A quick summery, Part 1

31. Artifacts from product planning All: Write down your definition of Product Owner Project objective Product Backlog Product Backlog item Estimations Planning poker Story point Product Planning meeting Team Exercise

32. So, how do we Get moving?

33. What next? All: It’s two weeks to the party. You are five persons, what do you do next? Exercise

34. How does scrum do it? Divide the time to final delivery into smaller projects For example One week at the time Plan these smaller projects when they start When a new week start, you plan what to do during that week

35. The sprint A time boxed period Starts with a sprint planning meeting End with working functionality

36. The sprint planning meeting Dividing highest prioritized items into tasks Commitment to which product backlog items are to be completed

37. The product backlog All: Given that we think that we can achieve 40 story points per week, which items should we plan that we can do week 1? Buy all ingredients for three course dinner & soft drinks & mineral water , 20 story points Buy new kitchenware, 8 story points Buy wine & beer , 8 story points Clean bathroom, living room & kitchen , 13 story points Prepare dinner , 8 story points Getting dressed before dinner , 3 story points Prepare dinner table , 3 story points Prepare welcome drinks , 1 story points Buy new Nintendo Wii game , 8 story points Buy new clothes to Ed , 8 story points

38. The product backlog Buy all ingredients for three course dinner & soft drinks & mineral water , 20 story points Buy new kitchenware, 8 story points Buy wine & beer , 8 story points Clean bathroom, living room & kitchen , 13 story points Prepare dinner , 8 story points Getting dressed before dinner , 3 story points Prepare dinner table , 3 story points Prepare welcome drinks , 1 story points Buy new Nintendo Wii game , 8 story points Buy new clothes to Ed , 8 story points

39. Dividing into tasks All: Divide the following items into tasks Buy all ingredients for three course dinner & soft drinks & mineral water , 20 story points Buy new kitchenware, 8 story points Buy wine & beer , 8 story points

40. Example of tasks Ingredients Drive to store Food Drinks Complete purchase Drive home Kitchenware Drive to store Barbeque Plates Complete purchase Drive home Wine & Beer Drive to store Beer Wine Complete purchase Drive home

41. Estimating tasks Tasks are estimated near when they are to be performed Tasks are so small and specific that they can be estimated in hours Planning poker can be used, but instead of story points, hours is the metric used

42. Estimate tasks Ingredients Drive to store Food Drinks Complete purchase Drive home Kitchenware Drive to store Barbeque Plates Complete purchase Drive home Wine & Beer Drive to store Beer Wine Complete purchase Drive home All: Use planning poker to estimate the different tasks

43. Example of estimations Ingredients Drive to store 3 Food 3 Drinks 0,5 Complete purchase 1 Drive home 3 Kitchenware Drive to store 2 Barbeque 0,5 Plates 0,5 Complete purchase 0,5 Drive home 2 Wine & Beer Drive to store 2 Beer 0,5 Wine 1 Complete purchase 0,5 Drive home 2 Three people, 1 hour drive

44. Sprint backlog Tasks and product backlog items which the team commits to during the sprint planning meeting

45. The first day of the project All: What happens now? What do you do?

46. Daily standup All working days include this meeting All tell what they did the day before, what they will do today and if there are any impediments All team members pull tasks from the board

47. Daily meeting, Day 1 Drive to store 3 – Bob, Ed, Clara Food 3 – Bob & Clara Drinks 0,5 - Ed Complete purchase 1, Bob, Ed, Clara Drive home 3 - Bob, Ed, Clara

48. Daily meeting, Day 2 Clara Yesterday, went to store, got the food, drove back. Today: another project Bob Yesterday, went to store, got the food, drove back. Today: another project Ed Yesterday, went to store, got the drinks, drove back. Today: fix the soft drinks since he forgot them

49. We’re running behind All: Think about ways to handle the delays

50. Ed is not happy with the chicken It is the third day of the project and Ed decides that he doesn’t want the bought chicken. He want some steak and he thought he clarified this with the team. He goes to Bob and ask him to fetch that. All: Think about how Bob should handle this

51. Changes will occur People change their minds New ideas arrive Mistakes and errors are made We cannot count on a plan Being agile is about handling changes

52. Changes in priorities A product owner can change the priorities Changes in priority is not done during sprint but before a sprint planning meeting is completed, the priorities may change

53. The scrum master The scrum master protects the team from outside disturbances If a problem rises during the sprint, the product owner communicates with the scrum master

54. Handling of delays The delay is discussed during the following Daily Standup The team discusses if the delay can be handled and sprint objectives can be met anyway, otherwise the breaking of the sprint or cutting of sprint backlog is decided by product owner

55. Handling of changes in priority Ed brings the issue to Clara, who is the scrum master. She thinks the change is so big that this risks the sprint objective. She asks if Ed wishes to cut the sprint and re plan or if the chicken can be prioritized for the upcoming sprint

56. End of first week All: What do you/we need to be able to plan next week?

57. Sprint review Ends a sprint The team shows stakeholders what has been accomplished during the sprint No PowerPoint, just working functionality

58. Sprint retrospect Not a scrum artifact The team discusses the previous sprint, What has improved What should remain Effect of previous changes

59. Planning meeting for week 2 All: What do you think can be accomplished during the upcoming week? Buy all ingredients for three course dinner & soft drinks & mineral water , 20 story points, DONE Buy new kitchenware, 8 story points, DONE Buy wine & beer , 8 story points, DONE Clean bathroom, living room & kitchen , 13 story points Prepare dinner , 8 story points Getting dressed before dinner , 3 story points Prepare dinner table , 3 story points Prepare welcome drinks , 1 story points Buy new Nintendo Wii game , 8 story points Buy chicken, 2 story points Buy new clothes to Ed , 8 story points

60. Planning meeting for week 2 Buy all ingredients for three course dinner & soft drinks & mineral water , 20 story points, DONE Buy new kitchenware, 8 story points, DONE Buy wine & beer , 8 story points, DONE Clean bathroom, living room & kitchen , 13 story points Prepare dinner , 8 story points Getting dressed before dinner , 3 story points Prepare dinner table , 3 story points Prepare welcome drinks , 1 story points Buy new Nintendo Wii game , 8 story points Buy chicken, 2 story points Buy new clothes to Ed , 8 story points Pretty safe Perhaps Probably not

61. Velocity The estimated speed Approximate Story points per sprint What we can count on, what we can hope for and what is out of the question

62. The product owner before the sprint planning meeting Buy all ingredients for three course dinner & soft drinks & mineral water , 20 story points, DONE Buy new kitchenware, 8 story points, DONE Buy wine & beer , 8 story points, DONE Clean bathroom, living room & kitchen , 13 story points Prepare dinner , 8 story points Getting dressed before dinner , 3 story points Prepare dinner table , 3 story points Prepare welcome drinks , 1 story points Buy new Nintendo Wii game , 8 story points Buy chicken, 2 story points Buy new clothes to Ed , 8 story points Place effort on making priorities in yellow area and see that nothing red is important The WII game is at the bottom of the yellow sector – high risk that it won’t be done

63. Ed thinks before the last week Ed realizes that the kids won’t be happy if there is no game available, so he places this on top Ed understands that he can stop wishing for a new outfit and he won’t get that chicken dinner And the week’s planning can start

64. Artifacts from the sprint All: Write down your definition of Sprint Sprint planning meeting Sprint review Sprint retrospective Change of priorities Scrum master Velocity Exercise

65. Questions