Scrum Terms

Front 1

Burn-down Chart

Back 1

A chart which shows the amount of work which is thought to remain in a backlog. Time is shown on the horizontal axis and work remaining on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing work remaining may be expected to fall. The amount of work may be assesed in any of several ways such as user story points or task hours. Work remaining in Sprint Backlogs and Product Backlogs may be communicated by means of a burn-down chart.

Hint 1

A chart which functions to track amount of ____ remaining in _____.

Front 2

Burn-up Chart

Back 2

A chart which shows the amount of work which has been completed. Time is shown on the horizontal axis and work completed on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing the work done may be extpected to rise. The amount of work may be assessed in any of several ways such as user story points or task hours. The amount of work considered to be in-scope may also be plotted as a line; the burn-up can be expected to approach this line as work is completed.

Hint 2

A chart that shows the amount of ____ which has been _____.

Front 3

Coherent/Coherence

Back 3

The quality of the relationship between certain Product Backlog items which may make them worthy of consideration as a whole.

Hint 3

Relationship between certain _____ that makes them worthy of _____ as a whole.

Front 4

Daily Scrum

Back 4

Daily time-boxed event of 15 minutes for the Development Team to replan the next day of development work during a Sprint.

Hint 4

15 minutes meeting for the ________.

Front 5

Definition of Done (DoD)

Back 5

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

Hint 5

Managed by the _______. Says the increment is ________.

Front 6

Development Team

Back 6

The role within a Scrum Team accountable for managing, organizing, and doing all development wok required to create a releasable increment of product.

Hint 6

Under the Scrum Team, this team is responsible for the development of the increment of _______.

Front 7

Emergence

Back 7

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.

Hint 7

Spontaneous fact emergence

Front 8

Empiricism

Back 8

Process controm type in which only the past is accrpted as certain and in which decisions are based on observation, experience, and experimentation. Empericism has three pillars: transparency, inspection, and adaptation.

Hint 8

The 3 pillars of Empiricism are Transparency, _______, and ________.

Front 9

Engineering Standards

Back 9

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

Front 10

Forecast (of functionality)

Back 10

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

Hint 10

Items selected from the Product Backlog by the ______.

Front 11

Increment

Back 11

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

Hint 11

What is completed at the end of each sprint.

Front 12

Product Backlog

Back 12

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

Hint 12

An ordered list of the _____ to be done in order to create, maintain, and sustain a _____. Managed by the ________.

Front 13

Product Backlog Refinement

Back 13

The aftivity in a Sprint through which the Product Owner and the Development Teams add granularity to the Product Backlog.

Hint 13

Granularity

Front 14

Product Owner

Back 14

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

Hint 14

The role in Scrum Teams accountable for maximizing the value of a _________.

Front 15

Ready

Back 15

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

Front 16

Refinement

Back 16

Product Backlog Refinement

Front 17

Scrum

Back 17

A framework to support teams in complex product development. Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules as defined by the Scrum Guide. Scrum Master, Development Team, and Product Owner.

Front 18

Scrum Board

Back 18

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 19

Scrum Guide TM

Back 19

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.

Hint 19

Ken Schwaber and Jeff Sutherland co-created this

Front 20

Scrum Master

Back 20

The role within the Scrum Team accountable for guiding, coaching, teaching, and assisting a Scrum Team and its environments in a proper understanding and use of Scrum.

Front 21

Scrum Team

Back 21

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

Front 22

Scrum Values

Back 22

A set of fundamental values and qualities underpining the Scrum framework; commitment, focus, openess, respect, and courage.

Front 23

Self-organization

Back 23

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 24

Sprint

Back 24

Time-boxed event of one month or less, that serves as a container for the other Scrum events and acyivities. Sprints are done consecutively, without intermediate gaps.

Front 25

Sprint Backlog

Back 25

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 26

Sprint Goal

Back 26

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 27

Sprint Planning

Back 27

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

Front 28

Sprint Retrospective

Back 28

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 29

Sprint Review

Back 29

Time-boxed event of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and 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 30

Stakeholder

Back 30

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 31

Technical Debt

Back 31

The typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the increment or introduced purposefully to realize value earlier.

Front 32

Values

Back 32

When the values of commitment, courage, focus, openess, and respect are embodied and lived by the Scrum Team, the "Scrum pillars" of transparency, inspection, and adaptation "come to life" and "build trust" for everyone. The Scrum Team members learn and explose those values as they work with the Scrum events, roles, and artifacts.

Front 33

Velocity

Back 33

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.