0% found this document useful (0 votes)
186 views

Cheat Sheet

The document outlines the roles, events, and artifacts of the Scrum framework. It describes the roles of the Product Owner, Scrum Master, and Development Team. It lists the Scrum events of Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. It also describes artifacts like the Product Backlog, Sprint Backlog, and Increment. The document provides details on how each role participates in the events and interacts with the artifacts.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
186 views

Cheat Sheet

The document outlines the roles, events, and artifacts of the Scrum framework. It describes the roles of the Product Owner, Scrum Master, and Development Team. It lists the Scrum events of Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. It also describes artifacts like the Product Backlog, Sprint Backlog, and Increment. The document provides details on how each role participates in the events and interacts with the artifacts.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 3

Events Timebox Who Inspect Adapt

Roles Scrum Team 3 – 5 - 3


Sprint Planning 8 uur max Scrum Team Capaciteit, Increment Sprint Backlog

Product Owner Roles Events Artifact Sprint Goal

- Product Owner - Sprint - Sprint Backlog Daily Scrum 15 min Development Sprint Backlog Sprint Backlog
• Accountable max Team Impediment
- Scrum Team - Sprint Planning - Product Backlog
• Optimizing value work develop Team
- Scrum Master - Sprint Retrospective - Increment
• Maintains the Product Backlog Sprint Review 4 uur max Scrum Team, Increment product Pruduct Backlog
- Daily Scrum * Definition of Done
• Ensures team work highest valued items Stakeholders Backlog,
- Sprint Review
• Dev Team understands items
Sprint Retrospective 3 uur max Scrum Team Way of working, Definition of Done
to level needed
• Stakeholder management Sprint Planning Definition of Done Commitment actiepunten

Refinement 10 % max Product Owner, Product Backlog Product Backlog


Backlog item
Scrum master needed (Items) (Items)
- Visible - Clear to all •
- Ordered - Maintains - taken place
- Transparent - Scrum team understand goal
- timebox
Cancel Sprint
Development Team • Scrum Team • Authority Product Owner
Cross-functional • Influence Development Team, Scrum Master, Stakeholders,
• • Answers : whats next increment
No titles • Goal obsolete, circumtances change
• - development team forecast sprint
No sub roles • “Done” to the releable increment, Product Owner Accepts
• - Product Owner, vision Sprint Goal
Specialized skills • Incomplete re-estimated and on Backlog
• with Back log items
• Self-organizing, managing - Scrum Team collaborates understand • Cost, Scrum Team traumatic
• Leads Sprint Review Sprint Goal • Uncommon
• Maintain Sprint Backlog - Input Backlog, latest Increment
Capacity Development Team - End of Sprint
Sprint Review
Scrum Master
Solely Development Team
- Scrum Team formulate Sprint Goal - collaborate -Stakeholders
- Present Increment
-Scrum Team
• Continuous improver • Answers : how achieved - Inspect the increment
- Everybody Discusses what’s next
• Teaches Daily Scrum timebox Development Team : - adapt backlog(if needed)
Input Sprint Planning
• Scrum promoting, supporting - How into “Done” - Design System - Sprint Planning - Scrum Master : -timebox
- Review -market, potential use
• Interactions Scrum Team helpful or not - work increment - Work first days - Clarify Product Owner -ensures take place
-timeline
• Facilitator - How much, little - Invite people -invitee knows goal
-budget
- explain Product Owner and Scrum Master - Product Owner -organizes Sprint Review
-potential capabilities
-what (not) “Done”
Daily Scrum -Condition Product Backlog
- Product Backlog -revised
-adjusted/adapt
Values -Prognosis next Delivery’s
(if needed)
-new items next Sprint
- Development Team -new opportunities
- next 24hr, same time, place - Development Team -went well
- Inspecting Sprint Goal, optimize probability
Openness - Respect – Courage - Focus - -How problems into/solved
- Understands how to work, self organized team Commitment -”Done” Demo
- Questions or discussion
- After Daily Scrum discussion other Team members
- Scrum Master Coached, 15 min, no disruption Sprint
- Improve knowledge
- Improve communication
- Eliminates other meetings, quick decision
Sprints contain and consist : Sprint Planning, Daily
- KEY → Inspect and adapt Scrums, development work, Sprint Review, Sprint
Retrospective
Sprint Goal
Is a objective/goal achieved by Sprint
- Implementation of Product Backlog items
- guidance Development Team
- Some flexibility how implementation
- coherent (related) functionality
→ Development Team work together
- Development Team keeps Sprint Goal in mind
- Functionality and Technology
- Development Team collaborate with
→ Product Owner

Sprint Retrospective
- Afer Sprint Review
Scrum Team inspecteren
→ plan to improve
- Before Sprint Planning
- How last sprint
- people
- relationship
- process tools
Indentify major items
→ well and improve
Plan implementing improvements
→ Scrum Team
Scrum Master
- take place
- Scrum Team understand goal
- Positive and Productive
- Timebox
- responsible Scrum proces framework
- anticipate

You might also like