This document outlines the basics of four Scrum ceremonies: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Sprint Planning involves defining sprint goals, clarifying requirements, and planning work. The Daily Scrum is a daily meeting to improve coordination and plan the next 24 hours. The Sprint Review demonstrates the product increment to stakeholders and gathers feedback. The Sprint Retrospective focuses on process improvements for future sprints. Each ceremony has defined inputs, participants, duration, outputs, and occurrence within the sprint cycle.
2. GG
PURPOSE:
DEFINE SPRINT GOALS (PO)
USER REQUIREMENT CLARIFICATION
PLANNING WORK
1. SPRINT PLANNING
INPUT:
PRODUCT BACKLOG
VELOCITY OF PAST
AVAILABLE CAPACITY
PARTICIPANTS:
ACTIVE/DEV TEAM
PRODUCT OWNER
STAKEHOLDERS BY PRODUCT OWNER
SCRUM MASTER (OPTIONAL)
TECHNICAL SUPPORT INVITED BY PRODUCT
OWNER
DURATION:
MAX 8 HOURS (FOR 4 WEEKS)
OUTPUT:
SPRINT BACKLOG
SPRINT GOAL
OCCURRENCE:
FIRST DAY OF THE SPRINT
3. GG
INPUT:
WORK DONE / NOT DONE
PAST DAILY SCRUM IMPEDEMENTS
PARTICIPANTS:
ACTIVE/DEV TEAM
PRODUCT OWNER
SCRUM MASTER
DURATION:
MAX 15 MINUTES
OUTPUT:
NEW IDENTIFIED IMPEDEMENTS
PLAN FOR NEXT 24 HOURS
(OPTIONAL)
PURPOSE:
IMPROVE COORDINATION
PLANNING FOR 24 HOURS
2. DAILY SCRUM
OCCURRENCE:
EVERY WORKING DAY
4. GG
INPUT:
PRODUCT INCREMENT w/ DEMO
DURATION:
4 HOURS
PARTICIPANTS:
SCRUM TEAM (Product Owner,
Scrum Master, Active/Dev Team)
STAKEHOLDERS
OUTPUT:
STAKEHOLDER FEEDBACK
ADAPTED PRODUCT BACKLOG
ADAPTED DoD FOR FUTURE
SPRINTS
PURPOSE:
STAKEHOLDER FEEDBACK
3. SPRINT REVIEW
OCCURRENCE:
JUST BEFORE THE END OF THE
SPRINT
5. GG
INPUT:
WHAT WENT WELL
WHAT DID NOT GO WELL
WHAT CAN BE DONE BETTER
DURATION:
3 HRS
PARTICIPANTS:
SCRUM TEAM
OUTPUT:
PROCESS IMPROVEMENT
PLAN FOR IMPROVEMENT
PURPOSE:
FUTURE IMPROVEMENT FOR THE
UPCOMING SPRINT
4. SPRINT RETROSPECTIVE
OCCURRENCE:
JUST AFTER SPRINT REVIEW