TWO WEEKS SPRINT TIMELINE
RETROSPECTIVE MEETING - The Team will indentify what was working well and what was not working during the last Sprint. This is the basic for the continous improvement and increasing the productivity and quality.
REVIEW MEETING
Next Sprint Last Sprint
- The Team make a live demonstration. - Changes may come out of this meeting and will be added to the Product Backlog.
- Strategy Planning: Max 2 hours - Tactical Planning: Max 2 hours - Output: Final Sprint Backlog, all initialized Tasks for the upcoming Sprint.
MON
FRI
Daily Stand-up Meeting (max 15 minutes)
FINAL CROSS TEST
TH U
E TU
- Cross functional testing - Project deployment - Preparing for the Sprint Review
WED
WED
E TU
TH U
- Product Owner will accept or reject the demonstrated features.
PLANNING
FRI
MON
BACKLOG GROOMING - Product Owner spend time to review and update the priority of user story in product backlog - Revise product backlog and release plan Product Owner
Scrum Mater
PLAN - DO - CHECK - ACT 1. STRATEGY PLANNING RETROSPECTIVE
SPRINT BACKLOG
2. TACTICAL PLANNING
rs ou
PLAN
2 ho urs
ours 2h
1.5 h
ACT
DAILY STAND-UP o
CHECK
15 Minutes
ks s
ee
2h
ur
2
w
DO
SPRINT REVIEW
SPRINT BACKLOG POTENTIAL SHIPPABLE FEATURENS
PRODUCT
Team
TEST PROCESS
Testing
Requirements / User Stories
Iterative Software Development/ Design
Incremental Release
Customer Feedback
2 week cycles
Shipable Features