Glossary

Question 1

Burn-down Chart

Answer 1

a chart which shows the amount of work which is thought to remain in backlog.

Question 2

Burn-up Chart

Answer 2

a chart which shows the amount of work which has been completed.

Question 3

Coherent/Coherence

Answer 3

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

Question 4

Daily Scrum

Answer 4

Scrum Event that is a 15-minute time-boxed event held each day for the Developers. Occurs every day of the sprint. Used to plan work for the next 24 hours.

Question 5

Definition of Done

Answer 5

A formal description of the state of the increment when it meets the quality measures required for the product.

Question 6

Increment

Answer 6

Scrum Artifact that defines the complete and valuable work produced by the Developers during a Sprint.

Question 7

Developer

Answer 7

Any member of a Scrum Team, that is committed to creating any aspect of a usable Increment each sprint.

Question 8

Emergence

Answer 8

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

Question 9

Empiricism

Answer 9

The philosophy that all knowledge originates in experience and observations. In scrum specifically it refers to complex work requiring exploratory processes rather then pre-determined plans

Question 10

Engineering standards

Answer 10

A shared set of development and technology standards that Developers apply to create releasable Increments of software.

Question 11

Forecast(of functionality)

Answer 11

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

Question 12

Product

Answer 12

The sum of all Increments form a product

Question 13

Product Backlog

Answer 13

A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sustain a product.

Question 14

Product Backlog refinement

Answer 14

The activity in a Sprint through which the Product Owner and the Developers add granularity to the Product Backlog.

Question 15

Product Owner

Answer 15

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

Question 16

Product Goal

Answer 16

The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog.

Question 17

Ready

Answer 17

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

Question 18

Scrum

Answer 18

A lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

Question 19

Scrum Board

Answer 19

A physical board to visualize information for and by the Scrum Team, Often used to manage Sprint Backlogs. Optional

Question 20

Scrum Master

Answer 20

Role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and it’s environments in a proper understanding and use of Scrum.

Question 21

Scrum Guide

Answer 21

The definition of Scrum, consists of Scrum’s accountabilities, events, artifacts, and the rules that bind them together.

Question 22

Scrum Team

Answer 22

a self-managing team consisting of one Scrum Master, one Product Owner, and Developers.

Question 23

Scrum Values

Answer 23

A set of fundamental values and qualities underpinning the Scrum framework: Commitment, focus, openness, respect, and courate.

Question 24

Self-Managing

Answer 24

Scrum Teams are cross-functional, meaning the members have all the skills

Question 25

Sprint

Answer 25

Scrum Event that is time-boxed to one month or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps.

Question 26

Sprint Backlog

Answer 26

Scrum Artifact that provides an overview of the development work to realize a Sprint’s goal.

Question 27

Sprint Goal

Answer 27

A short expression of the purpose of a sprint, often business problem that is addressed.

Question 28

Sprint Planning

Answer 28

Scrum Event that is time-boxed to 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 the Sprint Backlog

Question 29

Sprint Retrospective

Answer 29

Scrum Event that is time-boxed at 3 hours or less, to end a Sprint.

Question 30

Sprint Review

Answer 30

Scrum Event that is set to a time-boxed of 4 hours, to conclude the development work of a sprint. For the scrum team and stakeholders to inspect the increment of product resulting from the sprint.

Question 31

Stakeholder

Answer 31

A person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery.

Question 32

Technical Debt

Answer 32

The typically unpredictable overhead of maintaining the product.

Question 33

Values

Answer 33

When the values of commitment, courage, focus, openness and respect are embodied and lived by the scrum team, the Scrum pullers of transparency, inspection, and adaptation come to life and build trust for everyone.