ScrumGlossary

Question 1

Term: Burn-down Chart

Answer 1

a chart showing the evolution of remaining effort against time. Burn-down charts are an optional implementation within Scrum to make progress transparent.

Question 2

Term: Burn-up Chart

Answer 2

a 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.

Question 3

Term: Daily Scrum

Answer 3

daily 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.

Question 4

Term: Definition of Done

Answer 4

a shared understanding of expectations that software must live up to in order to be releasable intro production. Managed by the Development Team.

Question 5

Term: Development Team

Answer 5

the role within a Scrum Team accountable for managing, organising and doing all development work required to create releasable Increment of product every Sprint.

Question 6

Term: Emergence

Answer 6

the process of the coming into existence or prominence of new facts or new knowledge of a fact, or knowledge of a fact becoming visible unexpectedly.

Question 7

Term: Empiricism

Answer 7

process 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.

Question 8

Term: Engineering standards

Answer 8

a shared set of development and technology standards that a Development Team applies to create releasable Increments of software.

Question 9

Term: Forecast (of functionality)

Answer 9

the selection of items from the Product Backlog a Development Team deems feasible for implementation in a Sprint.

Question 10

Term: Increment

Answer 10

a piece of working software that add to previously created Increments, where the sum of all Increments -as a whole - form a product.

Question 11

Term: Product Backlog

Answer 11

an ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.

Question 12

Term: Product Backlog refinement

Answer 12

the activity in a Sprint through which the Product Owner and the Development Team add granularity to the Product Backlog.

Question 13

Term: Product Owner

Answer 13

the 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).

Question 14

Term: Ready

Answer 14

a shared understanding by the Product Owner and the Development Team regarding the preferred level of description of Product Backlog items introduced at Sprint Planning.

Question 15

Term: Scrum

Answer 15

a 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 Guide™.

Question 16

Term: Scrum Board

Answer 16

a 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.

Question 17

Term: Scrum Guide™

Answer 17

the definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co-creators of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together.

Question 18

Term: Scrum Master

Answer 18

the 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.

Question 19

Term: Scrum Team

Answer 19

a self-organizing team consisting of a Product Owner, Development Team and Scrum Master.

Question 20

Term: Self-organization

Answer 20

the management principle that teams autonomously organize their work. Self-organization happens within boundaries and against given goals. Team choose how best to accomplish their work, rather than being directed by others outside the team.

Question 21

Term: Sprint

Answer 21

time-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.

Question 22

Term: Sprint Backlog

Answer 22

an 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.

Question 23

Term: Sprint Goal

Answer 23

a 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.

Question 24

Term: Sprint Planning

Answer 24

time-boxed event of 1 day, 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.

Question 25

Term: Sprint Retrospective

Answer 25

time boxed event of 3 hours, or less, to end a Sprint. It serves for the Scrum Team to inspect the past Sprint and plan form improvements to be enacted during the next Sprint.

Question 26

Term: Sprint Review

Answer 26

time-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.

Question 27

Term: Stakeholder

Answer 27

a 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.

Question 28

Term: Velocity

Answer 28

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 use within the Scrum Team.