TWO WEEK SPRINT TIMELINE ACTIVITIES
TIMELINE
MONDAY
1 2
PLANNING MEETING PT 1
PLANNING MEETING PT 2
SETTING THE FORECAST
WHAT
PLANNING MEETING PART 1
WHO
PRODUCT OWNER
1 1
HOURS WHEN
Sprint Start
2 HOURS
PEOPLE
Team, Product Owner,
ScrumMaster
The product owner presents to
the team the high priority
(high value, high risk) stories in
the product backlog. Team
ACTIONS
members ask clarifying ques-
tions and the acceptance criteria
is communicated.
Sprint officially starts at the
end of this meeting.
OUTPUT
User stories and acceptance
criteria
TUESDAY WEDNESDAY
CURRENT SPRINT
PLANNING MEETING PART 2
SCRUMMASTER
Sprint Start
2 HOURS
Team, ScrumMaster
The Team decomposes the
high priority stories, as de-
scribed by the product owner,
into tasks and estimates them
in hours.
The team forecasts/commits
to the work. The sprint backlog
is built.
Committed sprint backlog and
Scrum board initialized with
tasks for the sprint.
THURSDAY
3 4
DAILY SCRUM/STANDUP MEETING OCCURS DAILY AT THE SAME TIME, SAME PLACE. 15 MINUTE TIMEBOX.
STORY WORKSHOP
SETTING THE FORECAST
PRODUCT OWNER
1 2-5
Sprint Start
AFTER MEETING 1 & 2
EMAIL OR IN PERSON
Product Owner, Stakeholders
The product owner communi-
cates commitment to stake-
holders at end of planning
meeting 2. Typically done via
email or in personal conversa-
tion.
Agreement on path forward.
Copyright 2006 - 2012 Mitch Lacey | Last Updated 30 June 2012 | Version 7.4
FRIDAY MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY
5 6 7 8 9 10
GROOMING BACKLOG PRIORITIZATION REVIEW MEETING
RETROSPECTIVE
ACTIVITY DETAILS
FUTURE SPRINT CURRENT SPRINT
WHAT
STORY WORKSHOP GROOMING BACKLOG PRIORITIZATION REVIEW MEETING RETROSPECTIVE
WHO
PRODUCT OWNER PRODUCT OWNER PRODUCT OWNER TEAM SCRUMMASTER
6,7,8 9 10 10
HOURS WHEN
First Week of Every Sprint Sprint Week Two Middle of Sprint Week Two Sprint End Sprint End
VARIES BY PROJECT 1-6 HOURS (5%-15%) VARIES: 1-3 HOURS 1 HOUR 1.5 HOURS
PEOPLE
Product Owner, Stakeholders Team, Product Owner, Product Owner, Stakeholders Team, Product Owner, Team, ScrumMaster
ScrumMaster ScrumMaster, Stakeholders
The product owner works with The product owner spends 5% The product owner reviews The stakeholders sit with the The team identifies what
the stakeholders to generate to 15% of his time with the the updated product backlog team, ScrumMaster and product worked and what didnt work,
user stories. team to review the updated with the stakeholders. owner to review the function- and what to improve for the
product backlog. ality delivered in the sprint. next sprint. The ScrumMaster
ACTIONS
Product owner & stakeholders Product owner & stakeholders facilitates the meeting.
review product backlog and Team revises and assigns review and prioritize backlog Changes may come out of this
add / update / modify new story point estimates to user items. meeting for the next sprint. The team adjusts itself
and existing stories as stories in the product backlog. accordingly.
needed.
OUTPUT
Clarification on stories in the Updated product backlog, Revised product backlog priority Customer acceptance of the Items for improvement for the
product backlog, updated pri- estimated by the team. and release plan. work presented and demon- team to implement in future
ority. strated by the team. sprints.
WWW.MITCHLACEY.COM