Scrum Vocabulary

Front 1

Burn-down Chart

Back 1

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

Front 2

Burn-up Chart

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

Front 3

Daily Scrum

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

Front 4

Definition of Done

Back 4

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

Front 5

Development Team

Back 5

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

Front 6

Emergence

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

Front 7

Empiricism

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

Front 8

Engineering standards

Back 8

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

Front 9

Forecast (of functionality)

Back 9

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

Front 10

Increment

Back 10

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

Front 11

Product Backlog

Back 11

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

Front 12

Product Backlog refinement

Back 12

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

Front 13

Product Owner

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

Front 14

Ready

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

Front 15

Scrum

Back 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 GuideTM.

Front 16

Scrum Board

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

Front 17

Scrum Guide™

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

Front 18

Scrum Master

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

Front 19

Scrum Team

Back 19

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

Front 20

Scrum Values

Back 20

a set of fundamental values and qualities underpinning the Scrum framework; commitment, focus, openness, respect and courage.

Front 21

Self-organization

Back 21

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

Front 22

Sprint

Back 22

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.

Front 23

Sprint Backlog

Back 23

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.

Front 24

Sprint Goal

Back 24

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.

Front 25

Sprint Planning

Back 25

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.

Front 26

Sprint Retrospective

Back 26

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 for improvements to be enacted during the next Sprint.

Front 27

Sprint Review

Back 27

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.

Front 28

Stakeholder

Back 28

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.

Front 29

Velocity

Back 29

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.