TWO WEEK SPRINT TIMELINE ACTIVITIES

TIMELINE
MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY
1 2 3 4 5 6 7 8 9 10
DAILY SCRUM/STANDUP MEETING OCCURS DAILY AT THE SAME TIME, SAME PLACE. 15 MINUTE TIMEBOX.

PLANNING MEETING PT 1 STORY WORKSHOP GROOMING BACKLOG PRIORITIZATION REVIEW MEETING

PLANNING MEETING PT 2 RETROSPECTIVE

SETTING THE FORECAST

ACTIVITY DETAILS
CURRENT SPRINT FUTURE SPRINT CURRENT SPRINT
WHAT

WHAT
PLANNING MEETING PART 1 PLANNING MEETING PART 2 SETTING THE FORECAST STORY WORKSHOP GROOMING BACKLOG PRIORITIZATION REVIEW MEETING RETROSPECTIVE
WHO

WHO
PRODUCT OWNER SCRUMMASTER PRODUCT OWNER PRODUCT OWNER PRODUCT OWNER PRODUCT OWNER TEAM SCRUMMASTER

1 1 1 2-5 6,7,8 9 10 10
HOURS WHEN

HOURS WHEN
Sprint Start Sprint Start Sprint Start First Week of Every Sprint Sprint Week Two Middle of Sprint Week Two Sprint End Sprint End

AFTER MEETING 1 & 2

2 HOURS 2 HOURS VARIES BY PROJECT 1-6 HOURS (5%-15%) VARIES: 1-3 HOURS 1 HOUR 1.5 HOURS
EMAIL OR IN PERSON
PEOPLE

PEOPLE
Team, Product Owner, Team, ScrumMaster Product Owner, Stakeholders Product Owner, Stakeholders Team, Product Owner, Product Owner, Stakeholders Team, Product Owner, Team, ScrumMaster
ScrumMaster ScrumMaster ScrumMaster, Stakeholders

The product owner presents to The Team decomposes the The product owner communi- The product owner works with The product owner spends 5% The product owner reviews The stakeholders sit with the The team identifies what
the team the high priority high priority stories, as de- cates commitment to stake- the stakeholders to generate to 15% of his time with the the updated product backlog team, ScrumMaster and product worked and what didnt work,
(high value, high risk) stories in scribed by the product owner, holders at end of planning user stories. team to review the updated with the stakeholders. owner to review the function- and what to improve for the
the product backlog. Team into tasks and estimates them meeting 2. Typically done via product backlog. ality delivered in the sprint. next sprint. The ScrumMaster
ACTIONS

ACTIONS
members ask clarifying ques- in hours. email or in personal conversa- Product owner & stakeholders Product owner & stakeholders facilitates the meeting.
tions and the acceptance criteria tion. review product backlog and Team revises and assigns review and prioritize backlog Changes may come out of this
is communicated. The team forecasts/commits add / update / modify new story point estimates to user items. meeting for the next sprint. The team adjusts itself
to the work. The sprint backlog and existing stories as stories in the product backlog. accordingly.
Sprint officially starts at the is built. needed.
end of this meeting.
OUTPUT

OUTPUT
User stories and acceptance Committed sprint backlog and Agreement on path forward. Clarification on stories in the Updated product backlog, Revised product backlog priority Customer acceptance of the Items for improvement for the
criteria Scrum board initialized with product backlog, updated pri- estimated by the team. and release plan. work presented and demon- team to implement in future
tasks for the sprint. ority. strated by the team. sprints.

Copyright 2006 - 2012 Mitch Lacey | Last Updated 30 June 2012 | Version 7.4 WWW.MITCHLACEY.COM