Download as PDF, PPTX
Uploaded byMuhammad Azani Hasibuan, M.T.I., PMP
Scrum in a nutshell
SCRUM is a framework for managing complex projects that emphasizes iterative development, daily self-organization, and regular inspection of progress and results. Key components of SCRUM include roles like the Product Owner, Scrum Master, and Development Team. Artifacts include the Product Backlog, Sprint Backlog, and Increment. Events in each Sprint include Sprint Planning, Daily Scrums, Sprint Execution, Sprint Review, and Sprint Retrospective. The goal is to optimize predictability, risk control, and value delivery through short cycles of work called Sprints.
In this document
Powered by AI
Introduces SCRUM with its definition and components, and outlines the SCRUM process.
Describes the project complexity spectrum, outlining terms like simple, complicated, complex, and chaos.
Highlights SCRUM's iterative approach for optimizing predictability and risk management in projects.
Presents the SCRUM workflow timeline detailing planning, design, coding, testing, and release activities across iterations.
Identifies key SCRUM roles: Product Owner, Scrum Master, and Development Team, fundamental for project success.
Details the Product Owner's role in managing the Product Backlog and engaging with stakeholders.
Outlines Development Team's collaborative responsibilities for developing the product and ensuring quality.
Describes the Scrum Master's role in facilitating the SCRUM process, removing impediments, and maintaining productivity.
Explains the critical events in SCRUM, including sprint planning, execution, review, and retrospective.
Details the daily SCRUM meetings, focusing on planning and progress assessment to ensure effective collaboration.
Summarizes the key SCRUM artifacts such as Product Backlog, Sprint Backlog, and Increment.
Lists key sources for deeper understanding of SCRUM, including The Scrum Guide and training resources.
More Related Content
![Vibe Coding vs. Spec-Driven Development [Free Meetup]](https://cdn.slidesharecdn.com/ss_thumbnails/vibecodingvsspecdrivendevelopment-251209105622-43f455e7-thumbnail.jpg?width=640&height=640&fit=bounds)
Scrum in a nutshell
- 1.
- 2. Definition of SCRUM SCRUMComponents SCRUM Process
- 3. Definition of SCRUM SCRUMComponents SCRUM Process
- 4.
- 5.
- 6. The best wayto optimize the predictability and control the risk is by employs an iterative and incremental approach. --SCRUM Guide
- 7. SCRUM GUIDE A frameworkwithin which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Source: Ken Schwaber, SCRUM Guide
- 8. Jan Feb MarApr Mei Jun Jul Aug Oct Nov Planning Design Coding Testing Release Review
- 9. Jan Feb MarApr Mei Jun Jul Aug Oct Nov Planning Review Design Coding Testing Release Planning Review Design Coding Testing Release Planning Review Design Coding Testing Release Planning Review Design Coding Testing Release ITERATION #1 ITERATION #2 ITERATION #3 ITERATION #4
- 10. Definition of SCRUM SCRUMComponents SCRUM Process
- 11. ROLE Product Owner Scrum Master DevelopmentTeam ARTIFACTS Product Backlog Sprint Backlog Increment EVENTS Sprint Planning Daily SCRUM Sprint Execution Sprint Review Sprint Retrospective
- 12. Product Owner SCRUMMaster Development Team
- 13. Define features/Product Backlog Prioritizefeatures/ Product Backlog Pick release dates Give feedback Manage stakeholders Accept or reject results Product Owner
- 14. Define tasks Estimate effort Developproduct Collaboratively Ensure quality Evolve processes Development Team
- 15. Remove impediments Prevent interruptions Facilitatethe team Support the process Ensuring SCRUM is undestood and enacted SCRUM Master Keep the team fully productive
- 16. Definition of SCRUM SCRUMComponents SCRUM Process
- 17.
- 18. SPRINT PLANNING DAILY SCRUM SPRINT REVIEW SPRINT RETROSPECTIVE SPRINT/ ITERATION Product Owner •An ordered list of requirement • Potential features of the product • The single source of truth for what is planned in the product • Public and available
- 19. DAILY SCRUM SPRINT REVIEW SPRINT RETROSPECTIVE SPRINT/ ITERATION Subset of ProductBacklog SPRINT PLANNING 4 hours for 2 weeks sprint / 8 hours for 4 weeks sprint Product Owner, SCRUM Master, and Dev. Team •Estimate the complexity of each product backlog item (PBI) •Negotiate the scope of PBI to PO •Decompose each product backlog items into tasks (called sprint backlog) Subset of product backlog Sprint backlog, Sprint Goal
- 20. SPRINT PLANNING SPRINT REVIEW SPRINT RETROSPECTIVE SPRINT/ ITERATION Sprint Backlog 15minute ( in the early day) SCRUM Master, and Dev. Team • Create a plan for the next 24 hours • Assess progress toward the Sprint Goal • By the Development Team, for the Development Team) Progress in previous day SPRINT EXECUTION DAILY SCRUM
- 21. SPRINT PLANNING SPRINT REVIEW SPRINT RETROSPECTIVE SPRINT/ ITERATION Sprint Backlog 2-4weeks SCRUM Master, and Dev. Team Implement the sprint backlog Sprint Backlog SPRINT EXECUTION DAILY SCRUM Increment
- 23. SPRINT RETROSPECTIVE SPRINT/ ITERATION Sprint Backlog SPRINT PLANNING SPRINT EXECUTION DAILY SCRUM PO,SCRUM Master, and Dev. Team • No Slides • Show the increment • Get Feedback form Product Owner Increment Of Software 2 hours for 2 weeks sprint/ 4 hours for 4 weeks sprint Feedback from Product Owner SPRINT REVIEW Increment
- 24. SPRINT PLANNING SPRINT REVIEW Increment SPRINT/ ITERATION Sprint Backlog SPRINT EXECUTION DAILY SCRUM SCRUMMaster, and Dev. Team • Identify what worked well • Identify what could be improved • Find the actionable improvements Feedback from PO & Experiences 2 hours for 2 weeks sprint/ 4 hours for 4 weeks sprint Future Improvements SPRINT RETROSPECTIVE
- 25.
- 26. ROLE Product Owner Scrum Master DevelopmentTeam ARTIFACTS Product Backlog Sprint Backlog Increment EVENTS Sprint Planning Daily SCRUM Sprint Execution Sprint Review Sprint Retrospective
- 27. • Schwaber, Ken& Jeff Sutherland (2011), The Scrum Guide, scrum.org •Joshua Partogi (2012), The Scrum Fundamental Course, scrumway.co