Process Framework Sprint Activities 2 Weeks Muthu Swamy

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

Process Framework : Sprint Activities - 2 Weeks Daily Scrum Meeting – 15 Minutes Sprint Planning Meeting 1 Meeting 2 The Product Owner presents the high‐ priority, high risk stories that the team do. The Sprint starts at the end of this meeting. The Team decompose s the high priority stories, into tasks and estimates them in hours. The team commits to the work. Day 1‐ 2 Hrs PO Mon Team Tue Commit Product Owner communica tes commitmen t to stakeholder s at end of Planning Meeting 2. Sprint backlog is built at this point. After Meeting 1 & 2 PO Wed Story workshop PB Review PB Priority Demo Retrosp ective The Product Owner sits with the users to write User Stories Product Owner and User review current backlog and update as needed 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. The Product Owner sits with the user to review the updated PB. Product Owner & User review and prioritize backlog items. User sits with the Team, SM and PO to review the functionalit y delivered in the Sprint. Changes may come for the next Sprint The SM facilitates the meeting. The Team identifies what worked & what didn’t work and adjusts itself. Day 5‐ 8 1 ‐ 3 Hrs Day 8‐ 10 2‐ 4 Hrs Day 10 2 Hrs Team PO Thu Fri Sprint Review Sat Sun Mon Day 12 1 ‐ 2 Hrs PO Tue wed PO : Product Owner / SM : Scrum Master / BP : Product Backlog Day 12 1. 5 Hrs Team SM Thu Fri

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