Scrum Glossary

Question 1

Burn down chart

Answer 1

Measures amount of work in a backlog, by calculating the amount of work to do versus the remaining time.

Question 2

Burn up chart

Answer 2

Measures the amount of work completed, by calculating the amount of work done versus the remaining time.

Question 3

Coherence

Answer 3

Quality of relationship between Product Backlog Items.

Question 4

Daily Scrum

Answer 4

15-minute Scrum event held every day to plan work and inspect and adapt progress in the Sprint

Question 5

Definition of Done

Answer 5

Describes the state a Product Backlog Item must meet in order to be considered a Done Increment.

Question 6

Developer

Answer 6

A member of a Scrum team that creates a usable Increment within a Sprint.

Question 7

Emergence

Answer 7

Process of new knowledge coming into existence or prominence.

Question 8

Empiricism

Answer 8

Philosophy behind Scientific method. In Scrum defines that solving complex problems is done by using an exploratory process and not predetermined plans.

Question 9

Engineering Standards

Answer 9

Shared set of development standards that Developers must apply.

Question 10

Forecast

Answer 10

The selection of Product Backlog Items that are deemed feasible to complete in the Sprint.

Question 11

Increment

Answer 11

Scrum artifact defining complete valuable work produced by Developers in a Sprint

Question 12

Product Backlog

Answer 12

Scrum artifact managed by a Product Owner that includes the work that needs to be done to create, maintain or sustain a product.

Question 13

Product Backlog Refinement

Answer 13

Activity where Product Owners and Developers discuss and break down the Product Backlog.

Question 14

Product Owner

Answer 14

A member of a Scrum Team that is responsible for maximizing value of a product, primarily by managing and communicating business and functional expectations to Developers.

Question 15

Product Goal

Answer 15

Targeted future state of the Product.

Question 16

Ready

Answer 16

Shared definition regarding the level of detail in PBIs required to introduce them in a Sprint.

Question 17

Scrum

Answer 17

Leightweight framework for solving complex problems.

Question 18

Scrum Board

Answer 18

A board for the Scrum Team to visualize information, namely the Sprint Backlog.

Question 19

Scrum Guide

Answer 19

A definition that consists of Scrum’s accountabilities, events, artifacts, and rules.

Question 20

Scrum Master

Answer 20

A member of a Scrum Team that guides and assists the team to properly understand and use Scrum.

Question 21

Scrum Team

Answer 21

Self-managing team consisting of 1 Product Owner, 1 Scrum Master and 1 or more Developers, with a size no bigger than 1o people.

Question 22

Scrum Values

Answer 22

5 fundamental qualities in Scrum: Commitment, focus, openness , respect and courage.

Question 23

Self-managing

Answer 23

The Scrum Team has the skills and autonomy to decide internally who does what, when and how.

Question 24

Sprint

Answer 24

A Scrum event timeboxed to a maximum of 1-month where the Scrum Team commits to delivering an Increment. It contains all other Scrum events.

Question 25

Sprint Backlog

Answer 25

A Scrum Artifact that includes the development work necessary to achieve a Sprint Goal, including a forecast of functionality and the work needed to deliver it.

Question 26

Sprint Goal

Answer 26

A short description of the purpose of a Sprint, what should be accomplished within it.

Question 27

Sprint Planning

Answer 27

Scrum Event of no more than 8h (for 1-month Sprints) that starts the Sprint. The Scrum Team inspects the Product Backlog Item and creates a plan to turn the most valuables ones into an Increment within the Sprint.

Question 28

Sprint Retrospective

Answer 28

Scrum Event of no more than 3h that ends the Sprint. The Scrum Team inspects the past Sprint and plans improvements for the next Sprints.

Question 29

Sprint Review

Answer 29

Scrum Event of no more than 4h, where the Scrum Team and Developers inspect the Increment created, assessing its impact on the Product Backlog.

Question 30

Stakeholder

Answer 30

Person external to the Scrum Team with interest and knowledge required for the product.

Question 31

Technical Debt

Answer 31

Unpredictable overhead of maintaining a Product due to design decisions which increase the cost of ownership.

Question 32

Scrum Pillars

Answer 32

Transparency, inspection and adaptation.

Question 33

Velocity

Answer 33

Indication of the amount of Product Backlog Items turned into an Increment over the course of a Sprint.