SCRUM

Each Sprint is...what?92

*Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something.*

CONVINCING THE PRODUCT OWNER76

*The Product Owner may represent the desires of a committee in the Product Backlog,* but those wanting to change a Product Backlog item's priority must address the Product Owner.

PRODUCT OWNER VISIBILITY78

*The Product Owner's decisions are visible in the content and ordering of the Product Backlog.* NO ONE can force the Development Team to work from a different set of requirements.

Cancelling a Sprint:98

-A Sprint can be cancelled BEFORE the Sprint time-box is over. -Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.

EXAMPLES of Transparency56

-A common language referring to the process must be shared by all participants; and, -Those performing the work and those inspecting the resulting increment must share a common definition of "Done".

What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?29

-By facilitating Development Team decisions -By removing impediments that hinder the Development Team *A Scrum Master is a servant-leader for the Development Team. Facilitation and removing impediments serves a team in achieving the best productivity possible.*

Product Backlog management includes:72

-Clearly expressing Product Backlog items; -Ordering the items in the Product Backlog to best achieve goals and missions; -Optimizing the value of the work the Development Team performs; -Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, -Ensuring the Development Team understands items in the Product Backlog to the level needed.

Which two (2) things does the Development Team do during the first Sprint?40

-Develop and deliver at least one piece of functionality. -Deliver an increment of releasable software. *The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and potentially releasable product Increment is created. This applies to every Sprint*

Which of the below are roles on a Scrum Team?32

-Development Team -Product Owner -Scrum Master

Scrum is:43

-Lightweight -Simple to understand -Difficult to master

Extent of Artifact Transparency122

-To the extent that transparency is complete, these decisions have a sound basis. -To the extent that the artifacts are incompletely transparent, these decisions can be flawed, value may diminish and risk may increase.

When is a "Done" increment required?79

A "Done" increment is required at the Sprint Review.

When would a Sprint be cancelled?99

A Sprint would be cancelled if the Sprint Goal becomes obsolete. *This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances.*

When many Development Teams are working on a single product, what best describes the definition of "done?"3

All Development Teams must have a definition of "done" that makes their combined work potentially releasable.

How much work must a Development Team do to a Product Backlog item it selects for a Sprint?25

As much as it has told the Product Owner will be done for every Product Backlog item it selects in conformance with the definition of "Done". *The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done".*

Development Team membership should change:7

As needed, while taking into account a short term reduction in productivity.

Do Sprint cancellations often happen?100

Due to the short duration of Sprints, cancellation rarely makes sense.

Upon what type of process control is Scrum based?13

Empirical Empiricism asserts that knowledge comes from experience and making decisions based on what is known.

Empiricism asserts what?54

Empiricism asserts that knowledge comes from experience and making decisions based on what is known. *Scrum employs an iterative, incremental approach to optimize predictability and control risk using the three pillars: TRANSPARENCY, INSPECTION, and ADAPTATION.*

Once a Sprint begins, its duration is...91

FIXED and CANNOT be shortened or lengthened. *The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.*

When multiple teams work together on the same product, each team should maintain a separate Product Backlog.22

False *Products have one Product Backlog, regardless of how many teams are used. Any other setup makes it difficult for the Development Team to determine what it should work on.*

It is mandatory that the product increment be released to production at the end of each Sprint.28

False *The product increment should be usable and releasable at the end of every Sprint, but it does not have to be released.*

Teams Smaller Than THREE EFFECT81

Fewer than three Development Team members decrease interaction and results in *smaller productivity gains.* *Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment.*

Teams LARGER Than Nine EFFECT82

Having more than nine members *requires too much coordination.* *Large Development Teams generate too much complexity for an empirical process to be useful.*

What is the main reason for the Scrum Master to be at the Daily Scrum?36

He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum. *The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.*

The CEO asks the Development Team to add a "very important" item to a Sprint that is in progress. What should the Development Team do?33

Inform the Product Owner so he/she can work with the CEO. *The items selected for a Sprint have been selected as most valuable with the Product Owner. The items serve the Sprint's goal. No changes should be made that endanger the Sprint Goal. No one external to the Scrum Team can force changes on the Development Team (Sprint Backlog) and the Product Owner (Product Backlog).*

The three pillars of empirical process control are:38

Inspection, Transparency, Adaptation *Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.*

Scrum Teams are:64

Scrum Teams are *self-organizing and cross-functional.*

How do Scrum Teams deliver products?68

Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback.

Is Scrum a process, technique, or definitive method?44

Scrum is *NOT* a process, technique, or definitive method. Rather, it is a framework within which you can employ various processes and techniques.

What is Scrum used now for?51

Scrum is now widely used for products, services, and the management of the parent organization.

Scrum relies on what?121

Scrum relies on transparency. * Decisions to optimize value and control risk are made based on the perceived state of the artifacts.*

What do Sprint cancellations consume?102

Sprint cancellations consume resources, since everyone regroups in another Sprint Planning to start another Sprint. Sprint cancellations are often traumatic to the Scrum Team, and are very uncommon.

Sprints enable what?97

Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. Sprints also limit risk to one calendar month of cost.

What is the role of Management in Scrum?24

Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to cause organizational change that fosters empiricism, self-organization, bottom-up intelligence, and intelligent release of software. *Management has no active role in the actual product development through Scrum. However, management external to the Scrum team is incredibly important in setting the vision and strategy to guide the overall direction of the organization.*

How does a Product Owner succeed?77

The *ENTIRE* organization must respect his or her decisions.

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?4

The Product Owner

Who has the final say on the order of the Product Backlog?20

The Product Owner *The Product Owner is the sole person responsible for managing the Product Backlog.*

What does the Scrum framework consist of?46

The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. *Each component within the framework serves a specific purpose and is essential to Scrum's success and usage.*

The essence of Scrum is?52

The essence of Scrum is a small team of people.

What does it mean to say that an event has a time-box?34

The event can take no more than a maximum amount of time.

Heart of Scrum94

The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and potentially releasable product Increment is created. *Sprints are limited to one calendar month.*

Scrum does not have a role called "project manager."39

True

The purpose of a Sprint is to produce a done increment of working product.11

True

What happens when a Sprint is cancelled?101

When a Sprint is cancelled, any completed and "Done" Product Backlog items are reviewed. -If part of the work is potentially releasable, the Product Owner typically accepts it. -All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog. -The work done on them depreciates quickly and must be frequently re-estimated.

When might a Sprint be abnormally cancelled?14

When the Sprint Goal becomes obsolete. A Sprint can be cancelled before the Sprint time-box is over. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change.

When is a Sprint over?35

When the time-box expires.

When is a Sprint over?16

When the time-box expires. *The duration of a Sprint is fixed and cannot be shortened or lengthened.*

Self-organizing teams:65

choose how best to accomplish their work, rather than being directed by others outside the team.

Cross-functional teams:66

have all competencies needed to accomplish the work without depending on others not part of the team.

Scrum Master to the *ORGANIZATION*89

-Leading and coaching the organization in its Scrum adoption; -Planning Scrum implementations within the organization; -Helping employees and stakeholders understand and enact Scrum and empirical product development; -Causing change that increases the productivity of the Scrum Team; and, -Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.

During the Sprint...95

-No changes are made that would endanger the Sprint Goal; -Quality goals do not decrease; and, -Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

The length of a Sprint should be:15

-Short enough to keep the business risk acceptable to the Product Owner. -Short enough to be able to synchronize the development work with other business events. -No more than one month.

Scrum prescribes four formal events for inspection and adaptation. What are they?60

-Sprint Planning -Daily Scrum -Sprint Review -Sprint Retrospective

What does the Scrum Master do?86

-The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. -The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.

Development Team characteristics80

-They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; -Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment; -Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person; -Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and, -Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?30

-Without a new vocabulary as a reminder of the change, very little change may actually happen. -The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. -Management may feel less anxious.

The time-box for a Daily Scrum is?26

15 Minutes. *The length of a daily Scrum is time-boxed at 15 minutes, it does not change with the length of a Sprint.*

Which statement best describes a Product Owner's responsibility?27

Optimizing the value of the work the Development Team does. *The Product Owner is responsible for maximizing the value of the product and the work of the Development Team.*

Scrum Events: Prescribed Events USAGE90

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.

SCRUM USUAGE & DEFINITION CONTENT41

Scrum is a framework for developing, delivering, and sustaining complex products. This definition consists of Scrum's roles, events, artifacts, and the rules that bind them together.

What does Scrum make clear?45

Scrum makes clear the relative efficacy of your product management and work techniques so that you can continuously improve the product, the team, and the working environment.

Why is the Scrum team model designed this way?67

The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

The Product Backlog is ordered by:37

Whatever is deemed most appropriate by the Product Owner. *The Product Owner decides what makes the most sense to optimize the value of the work being done by the Development Team.*

What happens when the Sprint's horizon is too long?96

When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase.

Scrum VALUES61

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.

Does the Scrum Team members respect each other to be capable, independent people?63

YES.

Does the Scrum Team agree to be open about their work?62

YES. The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.

THIRD PILLAR: Adapatation59

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. *An adjustment must be made AS SOON AS POSSIBLE to minimize further deviation.*

Incremental deliveries ensure what?69

Incremental deliveries of "Done" product ensure a potentially useful version of working product is always available.

Are The Product Owner and Scrum Master roles included in the Development Team Size?83

NO, UNLESS. The Product Owner and Scrum Master roles are NOT included in this count *unless they are also executing the work of the Sprint Backlog.*

When does a Development Team member become the sole owner of a Sprint Backlog item?8

Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be implemented by an individual development team member.

Why are Scrum events designed this way?93

These events are specifically designed to enable *critical transparency* and *inspection.* *Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.*

Scrum Master Service to the *DEVELOPMENT TEAM*88

-Coaching the Development Team in self-organization and cross-functionality; -Helping the Development Team to create high-value products; -Removing impediments to the Development Team's progress; -Facilitating Scrum events as requested or needed; and, -Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

Scrum Master Service to the *PRODUCT OWNER*87

-Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible; -Finding techniques for effective Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items; -Understanding product planning in an empirical environment; -Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; -Understanding and practicing agility; and, Facilitating Scrum events as requested or needed.

What is the recommended size for a Development Team (within the Scrum Team)?31

3 to 9

The time-box for the Sprint Planning meeting is?19

8 hours for a monthly Sprint. For shorter Sprints it is usually shorter. *Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.*

Who is accountable for a bad Product Backlog management setup?74

However, the Product Owner remains accountable.

When does the next Sprint begin?1

Immediately after the conclusion of the previous Sprint.

When are Inspections MOST beneficial?58

Inspections are most beneficial when diligently performed by skilled inspectors at the point of work.

Which statement best describes the Sprint Review?17

It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

Does the product owner need to manage?73

NO. The Product Owner may do the above work, or have the Development Team do it.

Who is responsible for managing the progress of work during a Sprint?5

The Development Team

Who is required to attend the Daily Scrum?18

The Development Team. *Only the people doing the work described on the Sprint Backlog need to inspect and adapt at the Daily Scrum. If the Scrum Master or Product Owner is also on the Development Team, they will need to be at the Daily Scrum. Otherwise, the Scrum Master simply has to make sure the Development Team knows how to conduct a Daily Scrum and does so.*

Why is the Daily Scrum held at the same time and same place?9

The consistency reduces complexity.

The Development Team should have all the skills needed to:10

Turn the Product Backlog items it selects into an increment of potentially releasable product functionality.

What do the words "develop" and "development" refer to?53

When the words "develop" and "development" are used in the Scrum Guide, they refer to complex work, such as those types identified below. *These strengths continue operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architectures and target release environments.*

Scrum has been used extensively, worldwide, to:49

1.Research and identify viable markets, technologies, and product capabilities; 2.Develop products and enhancements; 3.Release products and enhancements, as frequently as many times per day; 4.Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and, 5.Sustain and renew products.

The maximum length of the Sprint Review (its time-box) is:21

4 hours for a monthly Sprint. For shorter Sprints it is usually shorter. *Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.*

Which statement best describes Scrum?23

A framework within which complex products in complex environments are developed. *Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.*

Definition of Scrum42

A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

What does Scrum proved effective in?50

Scrum proved especially effective in iterative and incremental knowledge transfer.

SECOND PILLAR: Inspection57

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. *Their inspection should not be so frequent that inspection gets in the way of the work.*

What was Scrum initially developed for?48

Scrum was initially developed for managing and developing products.

FIRST PILLAR: Transparency55

Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen.

During the Daily Scrum, the Scrum Master's role is to:12

Teach the Development Team to keep the Daily Scrum within the 15 minute time-box.

What is the PRODUCT OWNER responsible for?70

The PRODUCT OWNER is responsible for maximizing the value of the product resulting from work of the Development Team.

During a Sprint, a Development Team determines that it will not be able to finish the complete forecast. Who should be present to review and adjust the Sprint work selected?2

The Product Owner and the Development Team.

How many people hold the title of Product Owner?75

The Product Owner is *ONE* person, not a committee.

Who is the sole person responsible for managing the Product Backlog?71

The Product Owner is the sole person responsible for managing the Product Backlog.

Who is a servant-leader for the Scrum Team?85

The SCRUM MASTER is a *servant-leader* for the Scrum Team.

Scrum Master RESPONSIBILITY84

The Scrum Master is responsible for *promoting and supporting Scrum* as defined in the Scrum Guide. *Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.*

The Development Team should not be interrupted during the Sprint. The Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity. Based on this, which of the following is FALSE?6

The Sprint Backlog is fully formulated in the Sprint Planning meeting and does not change during the Sprint.

What do the rules of Scrum bind together?47

The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction between them.