{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

03+Scrum.ppt - Scrum Overview Scrum is a development...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Modern Software Methodologies Week 03: Scrum Scrum Overview / Scrum Methodology / Scrum Results
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Scrum Overview Scrum is a development framework in which cross-functional teams develop products or projects in an iterative, incremental manner. It structures development in cycles of work called Sprints. The current short Sprint is meant to focus on a small, clear, relatively stable goal. Every day the Team gathers briefly to inspect its progress, and adjust the next steps needed to complete the work remaining. 2
Background image of page 2
Scrum Overview: 3
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Scrum Roles In Scrum, there are three roles: Product Owner, Team, and ScrumMaster. Together these are known as the Scrum Team. The Product Owner is responsible for maximizing return on investment (ROI) by identifying product features, translating these into a prioritized list, deciding which should be at the top of the list for the next Sprint, and continually re-prioritizing and refining the list. The Team (also called Development Team) builds the product that the Product Owner indicates. The ScrumMaster helps the product group learn and apply Scrum to achieve business value. 4
Background image of page 4
Product Backlog 5
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
A Good Product Backlog Detailed appropriately Estimated Emergent Prioritized Traditional development does not usually emphasize delivering according to highest bang for your buck, but this is a theme of Scrum, and therefore the Product Owner will need to learn how to assess the bang of “business value.” 6
Background image of page 6
Definition of Done The output of every Sprint is officially called a Potentially Shippable Product Increment. Unfortunately, when Teams start using Scrum, they are often not able to achieve the goal of delivering a Potentially Shippable Increment every Sprint. Before the first Sprint, the Product Owner and Team need to agree on a Definition of Done, which is a subset of the activities that are needed for creating a Potentially Shippable Product Increment. A good Product Owner will always want the Definition of Done to be as close as possible to Potentially Shippable. 7
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Sprint Planning A meeting to prepare for the Sprint, typically divided into two parts part one is “what” part two is “how” In Sprint Planning Part One, the Product Owner and Team review the high-priority items in the Product Backlog that the Product Owner is interested in implementing this Sprint.
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}