Scrum Drawing Game for Scrum Gathering Tokyo
•Télécharger en tant que PPTX, PDF•
3 j'aime•1,265 vues
Scrum Drawing Game is a good workshop for people who want to experience what the scrum is and how it works
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (9)
Similaire à Scrum Drawing Game for Scrum Gathering Tokyo
Similaire à Scrum Drawing Game for Scrum Gathering Tokyo (20)
Plus de Juggernaut Liu
Plus de Juggernaut Liu (16)
Dernier
Dernier (20)
Scrum Drawing Game for Scrum Gathering Tokyo
- 2. Hello ! I am Juggernaut Developer / Scrum Master / Agile Coach Community Volunteer / Speaker / Blogger / Agile Fighter Trend Micro CTBC Bank
- 3. My Goals After this workshop, you will understand what the scrum is why we should run it
- 6. Product – A Picture
- 7. Development 01:00 SM PO Team Team Team TeamScrum Team Product Owner * 1 Scrum Master * 1 Others are all team members Sprint Planning (3 mins) Running Sprint (6 mins) Sprint Review (5 mins) Sprint Retrospective (5 mins) 3 Sprints
- 8. Product Owner Describe requirements Prepare Product Backlog • Look at the sample and describe the requirements • Write down the stories • Prioritize
- 9. Scrum Master Facilitation Support your team • Facilitate all to follow the scrum process • Control the time-box • Do all what you could do
- 10. Team Complete the tasks • Follow the stories to draw • Cut and paste them to the white paper
- 11. Sprint 0 (7 minutes) Describe requirements Prepare the “Board” • Product Owner describes the SPEC, and members write down the story • Backlog, To Do, Doing, Done
- 12. Story & Acceptance Criteria [Story] A big Tiger [acceptance criteria] Its hair is golden [acceptance criteria] It’s smiling [acceptance criteria] It holds 3 books
- 13. Sprint Planning Describe • Product Owner describes the stories Estimate • Estimate how many stories team could do in this sprint and pick up them to Sprint backlog Sprint Backlog • Paste these stories to your ”To Do” column in your board
- 14. Working in Sprint Product Owner • Prepare Product Backlog • Prioritize the stories Scrum Master • Timebox & Support All Team • Drawing
- 15. Sprint Review Product Learning • Demo the release in this sprint • Get the feedback from users • Adjust the product backlog
- 16. Sprint Retrospective Next step • What did you learn? • What’s your action item? 02:00 03:00
- 17. Play ball
- 20. Before the sprint 1 What did we do ? What should we do before the Sprint 1 ? And Why ? 05:00 01:00
- 22. Sprint Planning What did we do ? What should we do in the sprint planning ? And Why ? 05:00 01:00
- 23. 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
- 25. 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
- 27. 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 %
- 29. Sprint Review What did we do ? What should we do in the sprint review ? And Why ? 05:00 01:00
- 30. 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
- 32. Sprint Retrospective What did we do ? What should we do in the sprint retrospective ? And Why ? 05:00 01:00
- 33. 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
- 34. Source : Titansoft Continuous Improvement Team What is retrospective ? Learn & Improve
- 35. Final Review
- 36. Show your product What’s the best thing ? What should be improved most? What did you learn ? What’s your next step ?03:00 10:00
- 38. Reference Scrum Primer Scrum Guide
- 39. CREDITS Special thanks to all the people who made and released these awesome resources for free: Presentation template by SlidesCarnival Photographs by Unsplash
Notes de l'éditeur
- A retrospective is an opportunity to learn and improve. It is time set aside – outside of day-to-day routine – to reflect on past events and behaviors. In its simplest form the team reflects on 3 questions: ・What did we do well? ・What did we do poorly? ・What will we do differently next time to improve?