Scrum Glossary Flashcards

1
Q

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

A

Burn-down Chart

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

shows the amount of work which has been completed

A

Burn-up Chart

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

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

A

Coherent/Coherence

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Scrum Event that is a 15-minute time-boxed event held each day for the Developers

A

Daily Scrum

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

a formal description of the state of the Increment when it meets the quality measures required for the product

A

Definition of Done

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

any member of a Scrum Team, that is committed to creating any aspect of a usable Increment each Sprint regardless of technical, functional or other specialty

A

Developer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

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

A

Emergence

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

process control type in which only the past is accepted as certain and in which decisions are based on observation, experience and experimentation

A

Empiricism

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

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

A

Engineering standards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

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

A

Forecast (of functionality)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

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

A

Increment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

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

A

Product Backlog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

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

A

Product Backlog refinement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Role in Scrum accountable for maximizing the value of a product

A

Product Owner

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

describes a future state of the product which can serve as a target for the Scrum Team to plan against

A

Product Goal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

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

A

Ready

17
Q

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

A

Scrum

18
Q

a physical board to visualize information for and by the Scrum Team

A

Scrum Board

19
Q

the definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co-creators of Scrum

A

Scrum Guide

20
Q

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

A

Scrum Master

21
Q

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

A

Scrum Team

22
Q

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

A

Scrum Values

23
Q

This means teams internally decide who does what, when, and how

A

Self-Managing

24
Q

Scrum Event that is time-boxed to one month or less, that serves as a container for the other Scrum events and activities

A

Sprint

25
Q

Scrum Artifact that provides 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

A

Sprint Backlog

26
Q

a short expression of the purpose of a Sprint, often a business problem that is addressed

A

Sprint Goal

27
Q

Scrum Event that is time-boxed to 8 hours, or less, to start a Sprint

A

Sprint Planning

28
Q

Scrum Event that is set to a time-box of 3 hours, or less, to end a Sprint

A

Sprint Retrospective

29
Q

Scrum Event that is set to a time-boxed of 4 hours, or less, to conclude the development work of a Sprint

A

Sprint Review

30
Q

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

A

Stakeholder

31
Q

the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership

A

Technical Debt

32
Q

an optional, but often used, indication of the amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Developers for use within the Scrum Team

A

Velocity

33
Q

commitment, courage, focus, openness and respect are what?

A

values