0% found this document useful (0 votes)
199 views8 pages

Agile and Scrum For Dummies

The document outlines Agile ceremonies, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, detailing their purposes and expected outcomes. It provides a timeline for a two-week sprint, specifying who attends each ceremony and what occurs during them. The document emphasizes continuous improvement and the immediate transition to the next sprint after the retrospective.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
199 views8 pages

Agile and Scrum For Dummies

The document outlines Agile ceremonies, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, detailing their purposes and expected outcomes. It provides a timeline for a two-week sprint, specifying who attends each ceremony and what occurs during them. The document emphasizes continuous improvement and the immediate transition to the next sprint after the retrospective.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Agile Ceremonies

Ceremony
Purpose Outcome
(Event)

Define what work


Sprint A clear sprint
will be done in the
Planning backlog.
sprint.

Align team
Daily progress
Daily Scrum members and
updates.
identify blockers.

Showcase work Stakeholder


Sprint Review and gather input for
feedback. improvement.

Reflect on the
Sprint Actionable
sprint and
Retrospective improvements.
improve.

A working
Complete work
The Sprint product
and deliver value.
increment.
Sprint Timeline
(for a 2 week sprint)
Day Ceremony Purpose

Define the work for


Day 1 (Sprint Sprint
the sprint and create
Start) Planning
the Sprint Backlog.

15-minute check-in to
Daily Scrums
Day 2-10 track progress and
(Stand-ups)
address blockers.

Demonstrate
Day 10 (Final
completed work to
Working Day of Sprint Review
stakeholders and
Sprint)
gather feedback.

Day 10 (After Reflect on the sprint


Sprint
Review or Next and identify
Retrospective
Day) improvements.

Day 11-12 Start the next sprint


New Sprint
(Next Sprint immediately after the
Planning
Start) retrospective.
Sprint Planning
(Day 1)
Who Product Owner, Business Analyst,
attends Scrum Master, Development Team.

Discuss high-priority backlog


items.
The team discusses scope,
What
estimates effort, and commits
happens
to tasks.
A Sprint Goal is set, and work is
added to the Sprint Backlog

Timebox 2-4 hours.

Outputs Clear plan for the next 2 weeks.

BA Ensure well-defined stories with


focus clear acceptance criteria.
Daily Scrums
(Days 2 - 10)
Who
Scrum team.
attends

Each team member answers:


What What did I do yesterday?
happens What will I do today?
Any blockers?

Timebox 15 minutes

Team stays aligned, and blockers


Outputs
are identified early.

Help resolve requirement-related


BA focus
blockers.
Sprint Review
(Day 10)
Who
Scrum Team + Stakeholders.
attends

The team presents a working


product increment.
What Stakeholders provide
happens feedback.
The Product Owner discusses
what’s next.

Timebox 1-2 hours.

Feedback is collected, and the


Outputs
product backlog is refined.

Gather feedback and ensure


BA focus
business needs are met.
Sprint Retro
(End of day 10 or next
day)
Who
Scrum team.
attends

Team discusses:
What went well?
What What didn’t go well?
happens What can we improve?
Action items are assigned for
improvement in the next sprint.

Timebox 1-2 hours.

Continuous improvement actions


Outputs
are identified.

Identify ways to improve


BA focus
requirements and processes.
When does the
next Sprint start?
The next sprint starts after the
retrospective, usually the next
working day.
There’s no waiting period...
Scrum follows a continuous
delivery cycle.
Sprint Planning for the next
sprint happens right after the
retrospective or the next
morning.
The team starts working on the
next Sprint Backlog immediately
after planning.
Did you find this useful?

If so... Give me a Follow


& Repost to your
audiences so they can
level up too!

Matthew Thomas
The BA Mentor

You might also like