1 / 3

Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010 Rms.reddy@hotmail

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. Sprint Review. Sprint Planning. Daily Scrum Meeting – 15 Minutes. Demo Day 12 1-2 Hrs. PB Priority

latif
Download Presentation

Muthu Swamy S, APSM, PMP, CSM, PM-2008 Friday, October 1, 2010 Rms.reddy@hotmail

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

  2. Process Framework : Sprint Activities - 2 Weeks Sprint Review Sprint Planning Daily Scrum Meeting – 15 Minutes Demo Day 12 1-2 Hrs PB Priority Day 10 2 Hrs PB Review Day 8-10 2-4 Hrs Retrospective Day 12 1.5 Hrs Story workshop Day 5-8 1-3 Hrs Meeting 2 Day 1-2Hrs Commit After Meeting 1 & 2 Meeting 1 Day 1-2Hrs The Team decomposes the high priority stories, into tasks and estimates them in hours. The team commits to the work. User sits with the Team, SM and PO to review the functionality 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. The Product Owner presents the high-priority, high risk stories that the team do. The Sprint starts at the end of this meeting. 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 sits with the user to review the updated PB. Product Owner & User review and prioritize backlog items. Product Owner communicates commitment to stakeholders at end of Planning Meeting 2. Sprint backlog is built at this point. 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. Team PO Team PO Team SM PO PO PO : Product Owner / SM : Scrum Master / BP : Product Backlog

  3. Process Framework-Detailed Activities for every Sprint

More Related