Scrum Events

Scrum is a framework for product management commonly used in software development

1. Scrum Events
Lov Kimsrung, 31-August-2022

2. Scrum Team
●Scrum Master: who facilitates the
meeting.
●Product Owner: who clarifies the
details of the product backlog
items and their respective
acceptance criteria.
●Development Team: who defines
the work and effort necessary to
meet the sprint commitment.

3. Daily Scrum/Standup Meeting
WHO ATTENDS: Developers
OBJECTIVES: To inspect progress toward the
Sprint Goal and adapt the Sprint Backlog as
necessary
DURATION: Up to 15 mins and everyday
ACTIVITIES: Each developers would take turn
to update their progress of works during the
standup with format as Yesterday, Today,
Problems

4. Sprint Grooming
WHO ATTENDS: Developers + Scrum
Master
OBJECTIVES: Keeping the backlog up to
date and Preparation of the next Sprint
Planning.
DURATION: Up to 2 hours, 2 times per week
ACTIVITIES: adding details, estimates, and
order to items in the Product Backlog. During
this meeting, items are reviewed, revised and
when possible estimated.

5. Sprint Planning
WHO ATTENDS: Developers + Scrum Master +
PO
OBJECTIVES: An ACTION PLAN for
implementing improvements to Scrum Team.
DURATION: Keep it Positive, Productive and up
to 1 hour.
ACTIVITIES:
1.What can be done this Sprint?
2.How will the chosen work get done?

6. Sprint Retrospective
WHO ATTENDS: Developers + Scrum Master + PO
OBJECTIVES: The whole team inspects itself and creates a
plan for improvements for next Sprint.
DURATION: Up to 2 hours, last day of sprint
ACTIVITIES:
1.Reviewing the previous Retrospective items. 5-10 min
2.CONTINUE - START - STOP. 30-40 min
3.ACTIONS for improvements selected by team 10-15 min

7. Sprint Review
WHO ATTENDS: Devs + Scrum Master +
PO + Stakeholders
OBJECTIVES: A revised Product Backlog
that defines the probable Product Backlog
items for the next Sprint.
DURATION: Up to 2 hours, last day of sprint
ACTIVITIES:
●PO explains what Product Backlog items
have been "Done" and what has not

8. Sprint Review Con’t
ACTIVITIES:
●The Development Team discusses what went well, what problems, and
how those problems were solved
●SPRINT DEMO
●The entire group collaborates on what to do next, so that it provides
valuable input to next Sprint Planning
●Review of the timeline, budget, potential capabilities, and marketplace for
the next anticipated releases of functionality or capability of the product.