Sprint Timeline 14 Day Detailed v7.8.

ai 1 3/15/2019 10:10:29 AM

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 T.1 STORY WORKSHOP PRODUCT BACKLOG REFINEMENT BACKLOG PRIORITIZATION REVIEW MEETING

PLANNING MEETING T.2 RETROSPECTIVE

SETTING THE FORECAST

ACTIVITY DETAILS
CURRENT SPRINT FUTURE SPRINT CURRENT SPRINT
C
WHAT

WHAT
M PLANNING MEETING TOPIC 1 PLANNING MEETING TOPIC 2 SETTING THE FORECAST STORY WORKSHOP PRODUCT BACKLOG REFINEMENT BACKLOG PRIORITIZATION REVIEW MEETING RETROSPECTIVE

Y
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
CM
HOURS WHEN

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

CY
AFTER MEETING 1 & 2
2 HOURS 2 HOURS VARIES BY PROJECT 1-6 HOURS (10%) VARIES: 1-3 HOURS 1 HOUR* 1.5 HOURS*
EMAIL OR IN PERSON
CMY
PEOPLE

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

The product owner presents to
the team the high priority
(high value, high risk) stories in
the product backlog. Team
ACTIONS
The Team decomposes the The product owner The product owner works with The product owner spends The product owner reviews The stakeholders sit with the The team identifies what
high priority stories, as communicates commitment to the stakeholders to generate ~10% of team capacity to the updated product backlog team, ScrumMaster and product worked and what didn’t work,
described by the product stakeholders at end of user stories. review details, estimates, and with the stakeholders. owner to review the and what to improve for the
owner, into tasks and planning meeting 2. Typically order of items in the Product functionality delivered in the next sprint. The ScrumMaster

members ask clarifying
questions and the acceptance
criteria is communicated.
Sprint officially starts at the
end of this meeting.
estimates them in hours.
The team forecasts/commits
to the work. The sprint backlog
is built.
done via email or in personal
conversation.
Product owner & stakeholders Backlog. This is an ongoing
review product backlog and process in which the Product
add / update / modify new Owner and the Development
and existing stories as Team collaborate on the
needed. details of Product Backlog
items.
Product owner & stakeholders
review and prioritize backlog
items.
ACTIONS
sprint. facilitates the meeting.
Changes may come out of this The team adjusts itself
meeting for the next sprint. accordingly.

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
OUTPUT

OUTPUT
criteria Scrum board initialized with product backlog, updated estimated by the team. and release plan. work presented and team to implement in future
tasks for the sprint. priority. demonstrated by the team. sprints.

* Offiical Scrum Guide times may differ. These are my recommendations. See http://scrumguides.org/ for more information
WWW.MITCHLACEY.COM
Copyright 2006 - 2019 Mitch Lacey | Last Updated 15 MARCH 2019 | Version 7.8