Make children book in 90 minutes thanks to Scrum by Enis Zeherovic
4 likes•647 views
The document outlines a methodology for rapidly creating a children's book using Scrum, an agile framework. It details the Scrum process, including its roles, artifacts, and events, and provides a step-by-step plan for conducting short sprints to efficiently develop the book. The focus is on teamwork, planning, and iterative reviews to enhance quality and productivity.
Make children book in 90 minutes thanks to Scrum by Enis Zeherovic
- 1. MAKE CHILDREN BOOK IN 90 MINUTES THANKS TO SCRUM ENIS ZEHEROVIĆ
- 2. Enis Zeherović • Software engineer • More than 8 years of experience in traditional and agile software development • TA specialist • QA/QC and HP software consultant • Comtrade employee • Certified Professional Scrum Product Owner • Bosnia Agile co-founder
- 4. AGENDA • Scrum introduction • Practice the Scrum – Make children book
- 5. SCRUM INTRODUCTION What is Scrum? • Lean is aproach with empirical inspect-and-adapt iterations instead of defined process steps. • Agile is Lean applied to software delivery. • Scrum is the leading universal agile framework.
- 6. SCRUM INTRODUCTION Why Scrum? • Over 32% of traditional projects fail to meet time and budget. • Scrum is: • Simple • Scalable • Widespread, used by over 50% of companies that implement agile • Proven to improve quality and productivity by 33% or more
- 7. OVERVIEW OF SCRUM 2-4 weeks 24 hrs Sprint Planning Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Daily Scrum Potentially Shippable Product Increment Sprint Goal 3 Roles • Product Owner • Development Team • Scrum Master 3 Artifacts • Product Backlog • Sprint Backlog • Increment 5 Events • Sprint Planning • Sprint • Daily Scrum • Sprint Review • Retrospective
- 9. MAKE CHILDREN BOOK 19 minutes for Sprint, 2 sprints: • 2 minutes for Sprint Planning • 5 minutes Day work x2 • 1 minute Daily Scrum • 4 minutes Sprint Review/Demo • 2 minutes Sprint Retrospective
- 10. TEAM BUILDING 2 min End Meet each other, decide on roles
- 11. INTRODUCE THE PRODUCT 4 min End Read the story
- 12. REMINDER • Product Backlog • Sprint Planning • Daily Scrum
- 13. 1. Identifies anything unique about the coming Sprint (vacations, holidays, etc.) 2. Selects a Sprint Goal 3. Selects the highest priority Product Backlog items that support the Sprint Goal A. Discusses Stories to break into tasks B. Estimates each task into work that could be delivered in a day C. The team asks itself, “Can we commit to this?” D. Repeat until no more can be committed SPRINT PLANNING 2-4 weeks 24 hrs Sprint Planning Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Daily Scrum Potentially Shippable Product Increment
- 14. DAILY SCRUM 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? 1 2 3 2-4 weeks 24 hrs Sprint Planning Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Daily Scrum Potentially Shippable Product Increment
- 15. SPRINT 1 PLANNING 2 min End Decide how much to do
- 16. DAY 1 IN SPRINT 1 5 min End Work
- 17. DAILY SCRUM IN SPRINT 1 1 min End What did you do? What will you do? Any obstacles?
- 18. DAY 2 IN SPRINT 1 5 min End Work
- 19. REMINDER • Sprint Review • Sprint Retrospective
- 20. • Team presents the product increment finished during the sprint • Typically takes the form of a demo of new features • Duration: 4-hour time-boxed meeting for one-month Sprints • Whole team participates • Invite the world SPRINT REVIEW (AKA DEMO) 2-4 weeks 24 hrs Sprint Planning Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Daily Scrum Potentially Shippable Product Increment
- 21. • Periodically take a look at what is and is not working • Duration: 4-hour time-boxed meeting for one-month Sprints • Done after each Sprint • Whole team participates: Scrum Master, Product Owner, Development Team, others SPRINT RETROSPECTIVE 2-4 weeks 24 hrs Sprint Planning Sprint Review Sprint Retrospective Product Backlog Sprint Backlog Daily Scrum Potentially Shippable Product Increment
- 22. SPRINT 1 REVIEW / DEMO 4 min End Demo by each team
- 23. SPRINT 1 RETROSPECTIVE 2 min End What went well? What to improve?
- 24. SPRINT 2 PLANNING 2 min End Decide how much to do
- 25. DAY 1 IN SPRINT 2 5 min End Work
- 26. DAILY SCRUM IN SPRINT 2 1 min End What did you do? What will you do? Any obstacles?
- 27. DAY 2 IN SPRINT 2 5 min End Work
- 28. SPRINT 2 REVIEW / DEMO 4 min End Demo by each team
- 29. SPRINT 2 RETROSPECTIVE 2 min End What went well? What to improve?
- 30. WRAP UP Demo for everyone by each team