1. Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010
Process Framework
Sprint Activities
2 Weeks
Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010

2. Daily Scrum Meeting – 15 Minutes
Process Framework : Sprint Activities - 2 Weeks
Daily Scrum Meeting – 15 Minutes
Sprint Planning
Sprint Review
Meeting 1
Day 1-2Hrs
The Product Owner presents the high-priority, high risk stories that the team do. The Sprint starts at the end of this meeting.
Meeting 2
Day 1-2Hrs
The Team decomposes the high priority stories, into tasks and estimates them in hours. The team commits to the work.
Commit
After Meeting 1 & 2
Product Owner communicates commitment to stakeholders at end of Planning Meeting 2. Sprint backlog is built at this point.
Story workshop
Day Hrs
The Product Owner sits with the users to write User Stories Product Owner and User review current backlog and update as needed
PB Review
Day Hrs
The Product Owner spends 5%-15% of his time with the team to review the PB. Team revises and assigns story point estimates to PB.
PB Priority
Day Hrs
The Product Owner sits with the user to review the updated PB. Product Owner & User review and prioritize backlog items.
Demo
Day Hrs
User sits with the Team, SM and PO to review the functionality delivered in the Sprint. Changes may come for the next Sprint
Retrospective
Day Hrs
The SM facilitates the meeting. The Team identifies what worked & what didn’t
work and adjusts itself. PO
Team PO PO
Team PO
Team SM
Mon
Tue
Wed
Thu
Fri
Sat
Sun
wed
PO : Product Owner / SM : Scrum Master / BP : Product Backlog

3. Process Framework-Detailed Activities for every Sprint
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Day 1 2 3 4 5 6 7 8 9 10 11 12
Activity
Meeting 1
Meeting 2
Story Workshop
HOLIDAY
Product Backlog Review
Backlog Prioritization
Review Meeting
Team Retrospective
Cadence
Sprint Start
Days 2‐5 of each Sprint
Every 2nd Monday of each Sprint
Every 2nd Wednesday of each Sprint
Every 2nd Friday at Sprint End
Time Duration
2Hr
As Needed
5% ‐ 15% of Team Time
1.5Hr
Owner
Product Owner
Scrum Master
Team
Attendees
Team, Product Owner, Scrum Master
Team, ScrumMaster
Product Owner, Stakeholders
Team, Product Owner, ScrumMaster
Team, Product Owner,ScrumMaster, Stakeholders
Activities
The Product Owner presents to the team the highest business value, high risk stories that the stakeholders requested
The team decomposes the stories requested by the product owner into tasks and estimates them in hours. The sprint backlog is built by the team. The Scrum Master facilitates and provides guidance as needed.
While the team is working, the biz analyst is meeting with stakeholders to prioritize the work backlog, add any new work requests, and document requirements. Information gathered in these sessions will be eligible for work in following iterations
In this informal meeting, the Product Owner shows the team the latest work backlog and the proposed priority. This happens so that the team has time to put forethought into the upcoming work requests and also identify areas for groupings with the biz analyst.
The Product Owner presents the prioritized list to the stakeholders, reviewing the updated release plan and most important work that will be presented to the team in the upcoming Planning 1 meeting on Monday
In this meeting, the team presents the completed work that it committed to completing at the beginning of the Sprint. The goal is reviewed, the work is reviewed and comments are heard. Any new changes are added to the Product Backlog and prioritized after the meeting.
This meeting is for the team to review what worked and what didn't work for it over the Sprint. It will decide what refinements, if any, it will make moving forward on the project. Inspect & adapt.
Outputs
The team has a clear understanding of the work that is needed by the business and can begin decomposing it in the Sprint Backlog.
The team presents the Product Owner with the work it believes it can commit to for the sprint. The Product Owner communicates commitment to stakeholders at end of planning meeting 2
The Product Owner will keep the Product Backlog up to date, and clear, with the highest risk, highest priority work items as needed by the business.
The Product Owner has a clear understanding of the estimated work time for the new requirements and has adjusted any other requirements in the Product Backlog. This results in an updated release plan.
Review of the goal, the work completed to achieve the goal and, if needed, the work queued for release to production as determined by the stakeholders and Product Owner.
The team will collect what worked, what needed improvement and an action plan.