1 / 16

Sprint Planning

Sprint Planning. Renato Pinto López TUM18 - UPM. Sprint Planning Meeting. ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM PO DESCRIBES THE HIGHEST PRIORITY FEATURES TO THE TEAM

gerard
Download Presentation

Sprint Planning

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. Sprint Planning Renato Pinto López TUM18 - UPM

  2. Sprint Planning Meeting • ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM • PO DESCRIBES THE HIGHEST PRIORITY FEATURES TO THE TEAM • TEAM ASKS QUESTIONS TO TURN A HIGH-LEVEL USER STORY OF THE PRODUCT BACKLOG INTO DETAILED TASKS OF THE SPRINT BACKLOG

  3. ProductOwner (PO) • Whois he/she? • PO istypically a project's key • stakeholder. • It is important that this person has a vision of what they wish to build and that he or she is able to convey that vision to the scrum team. • Whatishis/herjob? • To motivate the team with a clear, elevating goal. • What is his/her job?

  4. Productbacklog • Whatisit? • Prioritized features list, containing short descriptions of all functionality • desired in the product. • Typical Scrum backlog comprises the following: • Features • Bugs • Technical work • Knowledge acquisition

  5. Productbacklog • Features & Bugs • Each describes something different that a user wants. • Technical work: • "Upgrade all developers' workstations to Windows 8.“ • Knowledge acquisition: • It could be a Scrum backlog item about researching JS libraries and making a selection.

  6. Userstory • What is it? • Short, simple descriptions of the desired functionality told from perspective of the user. • "As a shopper, I can review the items in my shopping cart before checking out so that I can see what I've already selected."

  7. Userstory • Does user stories replace requirements document?

  8. Userstory • Does user stories replace requirements document? • It is important to remember that the written part of a user story (“As a user, I want…”) is incomplete until the discussions about that story occur. It is often best to think of the written part as a pointer to the real requirement.

  9. Sprint Planning Meeting • RESULT • SPRINT GOAL • SPRINT BACKLOG

  10. Sprint Goal • Definition: short description of whattheteamplanstoachieveduringthe sprint • Use:we use the sprint goalstoreportthoseoutsidethe sprint. • Success:success of the sprint willbeassessedduringthe sprint reviewmeetingagainstthe sprint goal

  11. Sprint backlog • Definition: list of the product backlog items the team commits to deliver plus the list of tasks necessary to deliver those product backlog items. • IMPORTANT: workers choose how many hours a week they work.

  12. Sprint reviewmeeting • It is held at the end of each sprint. • Scrum team shows what they achieved. • Includes PO, Scrum team, Scrum master, management, customers and developers from other projects. • Should be held in a relaxed atmosphere, and in a natural way.

  13. References • http://www.mountaingoatsoftware.com/scrum/sprint-planning-meeting • http://www.mountaingoatsoftware.com/scrum/product-owner • http://www.mountaingoatsoftware.com/scrum/product-backlog • http://www.mountaingoatsoftware.com/topics/user-stories • http://www.mountaingoatsoftware.com/scrum/sprint-review-meeting

More Related