Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
•
2 likes•1,085 views
啥? Scrum 是什麼? 能吃嗎? 我們每天都站著開會啊, 這不就是Scrum嗎?想知道真正Scrum的流程跟精髓嗎? 為什麼我們要敏捷? 沒有什麼比Workshop更能體驗一門學問喔!帶顆輕鬆的心情來場 Scrum Drawing Game 吧!!!Scrum Drawing Game 2.0 - Draw your dream house 是講師賈格為了Agile Tour全新推出的workshop, 所以去年曾經體驗過Scrum Drawing Game的朋友也沒關係, 在進階版的Scrum Drawing Game中我們擴大了版圖, 新增了Persona與Storyboard元素, 讓學員們有更完整的體驗, 於是透過這場Workshop, 我們將體驗到 : A. 如何生出需求 B. Product Owner 的責任 C. Scrum Team 如何運作 D. Team Building 來吧! 一起來玩 Scrum Drawing Game 吧 !
Recommended
More Related Content
What's hot
What's hot (8)
Similar to Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
Similar to Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu) (20)
More from AgileTour@TW
More from AgileTour@TW (9)
Recently uploaded
Recently uploaded (20)
Scrum Drawing Game 2.0 - Draw Your Dream House (Chao-Kung Liu)
- 2. Hello ! I am Juggernaut Developer / Scrum Master / Agile Coach / CSM / CSPO Scrum Drawing Game Author / Agilecommunity.tw Volunteer / Speaker / Blogger / Agile Fighter Trend Micro CTBC Bank
- 3. Outline Scrum Drawing Game Introduction Play Ball Show Time Recap & Discussion Q & A
- 5. Check in – Build a A-Team 03:00 Juggernaut ---------------- --- Scrum Master Stakehold er Product Owner Scrum Master Tea m
- 7. Scrum is easy to learn , but difficult to master.
- 8. Scrum Drawing Game Draw Your Dream House
- 9. A Storyboard about Dream House
- 10. You will play 2 roles User Scrum Team Think of our own ideas Develop user’s ideas
- 11. Pair teams Team2’s requiremen ts Team 1 develop Team2’s requirements Team 2 develop Team1’s requirements Team1’s requiremen ts
- 12. Workshop Process User Team Scrum Team Requirements User Story Sprint 0 Sprint 1 ~ 3 Show time Sprint Review Sprint Review Sprint Review
- 13. Sprint 0 Choose the role Prepare the “Board” • Stakeholder * 1 • Product Owner * 1 • Scrum Master * 1 • Others are Team 03:00 Backlog To Do Doing Done
- 14. Role - Stakeholder Provide requirements • Provide top 10 requirements Estimate the business value • Estimate the business value for these requirements Evaluate the story • Evaluate if this story is qualified
- 15. Role - Product Owner Describe requirements Prepare Product Backlog • Understand the requirements • Describe the requirements • Write down the stories • Prioritize the stories
- 16. Role - Scrum Master Facilitate your team Support your team • Facilitate all to follow the scrum process • Control the time-box • Do all what you could do
- 17. Role - Team Complete the tasks • Follow the stories to draw • Cut and paste them to the white paper
- 18. Role Card I have some requirements I propose some ideas to fit user’s requirements I facilitate the scrum team to focus on our goal I complete the work Stakeholder Product Owner Scrum Master Team Stakeholder Product Owner Scrum Master Team
- 19. Requirements - Persona 10:00 Top 10 Require ments
- 20. About Requirements (Just for the game) Requirements : 沒有籃球就吃不下飯, 睡 不著覺 Requirements : 我想要一個室內籃球場
- 21. Requirements - PO co-work with users Team 1 (User Team) Team 2 (Scrum Team) PO Requirements
- 22. Requirements – Business value Requirements Business Value Requirement 7 20 Requirement 2 8 Requirement 4 8 Requirement 9 5 Requirement 5 3 Requirement 1 2 Requirement 3 2 Requirement 8 1 Requirement 6 1 Requirement 10 0 Summary 50 03:00
- 23. User Story As a 籃球員, I want 院子架設一組籃框 so that 我可以每天練球 Requirements : 沒有籃球就吃不下飯, 睡不著覺 10:00
- 24. Development – Scrum Team SM PO Team Team Team TeamScrum Team Product Owner * 1 Scrum Master * 1 Others are all team members Sprint Planning (3 mins) Running Sprint (5 mins) Sprint Review I (4 mins) Sprint Review II (4 mins) Sprint Retrospective (1 mins) 3 Sprints
- 25. Profit & Cost Profit Cost • If Stakeholder thinks it’s qualified, scrum team get the profit by the business value • Based on how many people work in this sprint SM PO Team Team Team Team Scrum Team
- 26. Financial statements Group : 1 Sprint Profit Cost Net Profit The cumulative amount 1 0 6 -6 -6 2 13 6 7 1 3 13 + 10 6 17 18 4 13 + 10 + 16 6 33 51
- 27. Play Ball
- 28. Sprint Planning Discuss • Product Owner describes the stories • Team talk about how to do Estimate • Estimate how many stories team could do in this sprint and pick up them to Sprint backlog Prepare Sprint Backlog • Paste these stories to your ”To Do” column in your board 03:00
- 29. Working in Sprint Product Owner • Prepare Product Backlog • Prioritize the stories Scrum Master • Set the Timebox • Support All Team • Draw the picture 05:00
- 30. Sprint Review Product Learning • Scrum Team demo the release in this sprint • User team give the feedback • Stakeholder evaluate the stories • Product Owner adjust the product backlog • CHANGE ! 04:00 04:00
- 31. Sprint Retrospective Next step • What did you learn? • What’s your action item? 01:00 02:00
- 32. Show time
- 33. Show your product User Team recap the requirements Scrum Team demo the product 02:00 02:00 • Tell us this story • What’s the best thing ? • Which requirements has been implemented ?
- 34. Show your product by shooting video Shoot video Share to “Agile Tour Hsinchu” FB Page
- 36. Before the Sprint 1
- 37. Before the sprint 1 What did we do ? How about the user story ? 03:00 02:00
- 38. Sprint Planning
- 40. Sprint Planning What did we do ? What should we do in the sprint planning ? And Why ? 03:00 02:00
- 41. Sprint Planning Product Backlog PO SM Team !@#$ %^& * Sprint Backlog Part I : What PO Team !@#$ %^& * Sprint Backlog Part II : How *&^ % Tasks SM 1 ~ 4hr 1 ~ 4hr
- 42. Ask as many questions as you can
- 43. Daily Scrum
- 45. Daily Scrum To Do Doing Done 012 Kaori 001 Evelyn 004 011 010009 Jug 008 Juyi 005 Kaori 007 SMPO Team !@#$ • What did I do yesterday that helped the Development Team meet the Sprint Goal? • What will I do today to help the Development Team meet the Sprint Goal? • Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? 15:00
- 46. Another Practices for Daily Scrum – Based on stories Story To Do Doing Done Kaori 001 Evelyn 004Story A Jug 008 Juyi 005 Kaori 007 SMPO Team !@#$ Foreach (story a in stories) { About story a : What did I do ? What will I do today ? Do I see any impediment ? } Story B Jug 011
- 49. Product Backlog Refinement Product Backlog PO SM Team !@#$ %^& *%^& * *&^ % Refinement usually consumes no more than 10% of the capacity of the Development Team. More detail and estimation < 10 %
- 50. Sprint Review
- 52. Sprint Review What did we do ? What should we do in the sprint review ? And Why ? 03:00 02:00
- 53. Sprint Review Invite & Explain PO SMTeam Our spirit goal (done & undone) stakeholders Team demo stakeholders POSM Demo Product Learning stakeholders POSM Team !@#$ !@#$ !@#$ !@#$ Product Backlog 1 ~ 4hr
- 56. Sprint Retrospective What did we do ? What should we do in the sprint retrospective ? And Why ? 03:00 02:00
- 57. Sprint Retrospective Good Bad Action 012 Kaori 001 Evelyn 004 011 010009 Jug 008 Juyi 005 Show don’t tell SMPO Team !@#$ 1 ~ 3hr Improve Process Lessons Learned Improve Engagement
- 58. Source : Titansoft Continuous Improvement Team What is retrospective ? Learn & Improve
- 59. Roles in Scrum • Clearly expressing Product backlog items (PBIs) • Single Product Owner • Product Discovery • Ordering the PBIs to best achieve goals and missions Product Owner Scrum Master • Coach the facilitate the Scrum team • Service to the PO, Team, and Organization • Make sure the Scrum team observe the Scrum spirit Team • Consists of professionals who do the work of delivering the product • Self-organizing team and the size should be between 5 and 9 • Develop the product actually 03:00 06:00
- 62. Adapt to change quickly
- 63. Agile Manifesto
- 66. Reference Scrum Primer Scrum Guide
- 67. CREDITS Special thanks to all the people who made and released these awesome resources for free: Presentation template by SlidesCarnival Photographs by Unsplash