Scrum

Question 1

Burn-down Chart

Answer 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 assessed 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. See also: Burnup Chart

Question 2

Burn-up Chart

Answer 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 expected 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.

Question 3

Coherence

Answer 3

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

Question 4

Daily Scrum

Answer 4

daily time-boxed event of 15 minutes for the Development Team to re-plan the next day of development work during a Sprint. Updates are reflected in the Sprint Backlog.

Question 5

Definition of Done

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

Question 6

Development Team

Answer 6

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.

Question 7

Emergence

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

Question 8

Empiricism

Answer 8

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.

Question 9

Engineering standards

Answer 9

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

Question 10

Forecast (of functionality)

Answer 10

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

Question 11

Increment

Answer 11

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

Question 12

Product Backlog

Answer 12

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

Question 13

Product Backlog refinement

Answer 13

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

Question 14

Product Owner

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

Question 15

Ready

Answer 15

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.

Question 16

Refinement

Answer 16

see Product Backlog Refinement

Question 17

Scrum

Answer 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 in the Scrum GuideTM.

Question 18

Scrum Board

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

Question 19

Scrum Guide

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

Question 20

Scrum Master

Answer 20

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.

Question 21

Scrum Team

Answer 21

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

Question 22

Scrum Values

Answer 22

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

Question 23

Self-organization

Answer 23

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

Question 24

Sprint

Answer 24

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

Question 25

Sprint Backlog

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

Question 26

Sprint Goal

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

Question 27

Sprint Planning

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

Question 28

Sprint Retrospective

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

Question 29

Sprint Review

Answer 29

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.

Question 30

Stakeholder

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

Question 31

Technical Debt

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

Question 32

Values

Answer 32

When the values of commitment, courage, focus, openness 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 explore those values as they work with the Scrum events, roles and artifacts. Download the Scrum Values Poster

Question 33

Velocity

Answer 33

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 Development Team for use within the Scrum Team.