Flashcards
SCRUM Glossary
Cards in this deck (28)
- 1Burn-down Charta chart showing the evolution of remaining effort against time. Burn-down charts are an optional implementation within Scrum to make progress transparent
- 2Burn-up Charta chart showing the evolution of an increase in a measure against time. Burn-up charts are an optional implementation within Scrum to make progress transparent
- 3Daily Scrumdaily time-boxed event of 15 minutes, or less for the Development Team to re-plan the next day of development work during a Sprint. Updates are reflected in the Sprint Backlog
- 4Definition of Donea shared understanding of expectations that software must live up to in order to be releasable into production. Managed by the Development Team
- 5Emergencethe process of the coming into existence or prominence of new facts or new knowledge of a fact becoming visible unexpectedly
- 6Development Teamthe role within a Scrum Team accountable for managing, organizing and doing all development work required to create a releasable Increment of product every Sprint
- 7Empiricismprocess control type in which only the past is accepted as certain and in which decisions are based on observation, experience and experimentation. Empiricism has three pillars: Transparency, Inspection and Adaptation
- 8Engineering Standardsa shared set of development and technology standards that a Development Team applies to create releasable Increments of software
- 9Incrementa piece of working software that adds to previously created Increments, where the sum of all increments-as a whole- form a product
- 10Forecast (of functionality)the selection of items from the Product Backlog a Development Team deems feasible for implementation in a Sprint
- 11Product Backlogan ordered list of the work to be done in order to create, maintain and sustain a product. Managed by Product Owner.
- 12Product Backlog refinementthe activity in a Sprint through which the Product Owner and the Development Team add granularity to the Product Backlog
- 13Product Ownerthe role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Development Team(s)
- 14Readya shared understanding by the Product Owner and the Development Team regarding the preferred level of description of Product Backlog items introduced at Sprint Planning
- 15Scruma framework to support teams in complex product development. Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules, as defined in the Scrum GuideTM
- 16Scrum Boarda physical board to visualize information for and by the Scrum Team, often used to manage Sprint Backlog. Scrum boards are an optional implementation within Scrum to make information visible
- 17Scrum Masterthe role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and its environments in a proper understanding and use of Scrum
- 18Scrum Teama self organizing team consisting of a Product Owner, Development Team and Scrum Master
- 19Scrum Valuesa set of fundamental values and qualities underpinning the Scrum framework; commitment, focus, openness, respect and courage
- 20Self-organizationthe management principle that teams autonomously organize their work. Self-organization happens within boundaries and against given goals. Teams choose how best to accomplish their work, rather than being directed by others outside the team.
- 21Sprinttime-boxed event of 30 days, or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps.
- 22Sprint Backlogan overview of the development work to realize a Sprint's goal, typically a forecast of functionality and the work needed to deliver that functionality. Managed by the Development Team.
- 23Sprint Goala short expression of the purpose of a Sprint, often a business problem that is addressed. Functionality might be adjusted during the Sprint in order to achieve the Sprint Goal.
- 24Sprint Planningtime-boxed event of 8 hours, or less, to start a Sprint. it serves for the Scrum Team to inspect the work from the Product Backlog that's most valuable to be done next and design that work into Sprint backlog
- 25Sprint Retrospectivetime-boxed event of 3 hours, or less, to end a Sprint. It serves for the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during the next Sprint
- 26Sprint Reviewtime-boxed event of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and the stakeholders to inspect the increment of product resulting from the Sprint, assess the impact of the work performed on overall progress and update the Product Backlog in order to maximize the value of the next period
- 27Stakeholdera person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review.
- 28Velocity:an optional, but often used , indication of the average amount of Product Backlog turned into an increment of product during a Sprint by a Scrum Team, tracked by the Development Team for the use within the Scrum Team
Information
- Description
- Certificate SCRUM Master Flashcards on SCRUM Glossary, created by g.allen.msie on 06/01/2016.
- Created by
- g.allen.msie
- Views
- 22
- Tags
- Rating