Agile Scrum Guide

Front 1

When does the Development Team participate in Product Backlog Refinement?

Back 1

Anytime during the Sprint.

Front 2

What does code coverage show?

Back 2

Code being exercised by tests.

Front 3

Definition of SCRUM

Back 3

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

Front 4

3 things SCRUM is...

Back 4

 Lightweight
 Simple to understand
 Difficult to master

Front 5

What is empiricism? (SCRUM's founding principle.)

Back 5

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

Front 6

What are the 3 pillars that uphold empirical process control?

Back 6

transparency, inspection, and adaptation

Front 7

define transparency for SCRUM

Back 7

Significant aspects of the process must be visible to those responsible for the outcome.

Front 8

name some examples of transparency aspects for SCRUM

Back 8

 A common language referring to the process must be shared by all participants; and,
 Those performing the work and those accepting the work product must share a common definition of "Done".

Front 9

define Inspection for SCRUM

Back 9

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.

Front 10

what are the four formal events for inspection and adaptation in SCRUM?

Back 10

 Sprint Planning
 Daily Scrum
 Sprint Review
 Sprint Retrospective

Front 11

What does a SCRUM team consist of?

Back 11

The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.

Front 12

Two terms that describe SCRUM teams.

Back 12

self-organizing and cross-functional

Front 13

What is a self-organizing team in SCRUM terms?

Back 13

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

Front 14

What is a cross-functional team in SCRUM terms?

Back 14

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

Front 15

Why do SCRUM teams deliver products incrementally and iteratively?

Back 15

to maximize opportunities for feedback

Front 16

What do incremental deliveries of "done" ensure in SCRUM?

Back 16

a potentially useful version of working product is always available

Front 17

What is the responsibility of the product owner in SCRUM?

Back 17

maximizing the value of the product and the work of the Development Team

Front 18

What does the product owner manage in SCRUM?

Back 18

the sole person responsible for managing the Product Backlog

Front 19

What is involved in Product Management backlog?

Back 19

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

Front 20

Can the product owner be a committee in SCRUM?

Back 20

No.
Note: The Product Owner can represent the desires of a committee in the Product Backlog, but the person managing the Product Backlog is one person.

Front 21

What does the Product Owner need in order to succeed?

Back 21

the entire organization must respect the Product Owner's decisions

Front 22

Who are and what do the Development Team members do in SCRUM?

Back 22

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.

Front 23

What do the Development Team members create in SCRUM?

Back 23

they create the Increment

Front 24

Who manages and organizes the Development Team's work in SCRUM?

Back 24

Development Teams are structured and empowered by the organization to organize and manage their own work.

Front 25

What does a self-organizing Development Team look like in SCRUM?

Back 25

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.

Front 26

What does a cross-functional Development Team look like in SCRUM?

Back 26

Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment.

Front 27

What are the titles on a Development Team in SCRUM?

Back 27

Scrum recognizes no titles for Development Team members other than Developer.

Front 28

How are sub-teams organized for the Development Team in SCRUM?

Back 28

Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis

Front 29

What is the downside of having more than nine Development Team members on a SCRUM team?

Back 29

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

Front 30

Describe the role of the SCRUM master.

Back 30

The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.

Front 31

Describe the various ways the SCRUM master serves the Product Owner.

Back 31

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

Front 32

Describe the various ways the SCRUM master serves the Development Team.

Back 32

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

Front 33

Describe the various ways the SCRUM Master serves the organization

Back 33

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

Front 34

Why are all events in SCRUM time-boxed?

Back 34

so that every event has a maximum duration

Front 35

How does one adjust a Sprint length in SCRUM?

Back 35

Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened.

Front 36

Within the Sprint, what are the purpose of Events in SCRUM?

Back 36

each event in Scrum is a formal opportunity to inspect and adapt something

Front 37

Define Sprint for SCRUM.

Back 37

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.

Front 38

How long after the prior Sprint does a new Sprint begin in SCRUM?

Back 38

A new Sprint starts immediately after the conclusion of the previous Sprint.

Front 39

What events are contained in a Sprint in SCRUM?

Back 39

the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective

Front 40

What changes to the Sprint are/n't allowed?

Back 40

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

Front 41

What is the longest Sprint duration?

Back 41

Each Sprint may be considered a project with no more than a one-month horizon.

Front 42

What should each Sprint have to be successful?

Back 42

Each Sprint has a definition of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product.

Front 43

Why should a Sprint be no longer than a month?

Back 43

When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints also limit risk to one calendar month of cost.

Front 44

When can a Sprint be cancelled?

Back 44

A Sprint can be cancelled before the Sprint time-box is over.

Front 45

Who can cancel a Sprint?

Back 45

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.

Front 46

Give some examples of why a Sprint might be cancelled.

Back 46

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.

Front 47

What happens to completed/"done" product items when a Sprint is cancelled?

Back 47

If part of the work is potentially releasable, the Product Owner typically accepts it.

Front 48

What happens to incomplete Product Backlog Items when a Sprint is cancelled?

Back 48

All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.

Front 49

What is the maximum time allotted to Sprint planning?

Back 49

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

Front 50

What questions does Sprint planning answer?

Back 50

 What can be delivered in the Increment resulting from the upcoming Sprint?
 How will the work needed to deliver the Increment be achieved?

Front 51

What does the Development Team do during a Sprint Planning session?

Back 51

works to forecast the functionality that will be developed during the Sprint

Front 52

What does the Product Owner do during a Sprint Planning session?

Back 52

discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal

Front 53

What are the inputs to the Sprint Planning meeting?

Back 53

Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team

Front 54

Who picks the number of items in the Product Backlog for input into a Sprint?

Back 54

Only the Development Team can assess what it can accomplish over the upcoming Sprint.

Front 55

What is the Sprint Goal?

Back 55

an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment

Front 56

What is the Sprint Backlog?

Back 56

the Product Backlog items selected for this Sprint plus the plan for delivering them

Front 57

Describe a Sprint Review.

Back 57

when the Scrum Team and stakeholders inspect the outcome of the Sprint and figure out what to do in the upcoming Sprint.

Front 58

Who is required to attend the Daily Scrum?

Back 58

The Development Team.

Front 59

Scrum Master is a "management" position?

Back 59

True. (It is a Manager "servant" position!) The Scrum Master manages the Scrum process. If the Scrum Master is not a management position, he or she may not have the influence to remove impediments. The Scrum Master does not manage the team.

Front 60

What happens if the Development team determines it has too little or too much work?

Back 60

it may renegotiate the selected Product Backlog items with the Product Owner. The Development Team may also invite other people to attend in order to provide technical or domain advice.

Front 61

What should the Development Team be able to do by the end of the Sprint Planning Session?

Back 61

explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment

Front 62

What is the Sprint Goal to the Development Team?

Back 62

It provides guidance to the Development Team on why it is building the Increment.

Front 63

What should happen if the work turns out to be different than the Development Team expected?

Back 63

they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint

Front 64

What is the Daily Scrum?

Back 64

The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours

Front 65

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

Back 65

to reduce complexity

Front 66

What should each team member explain during the Daily Scrum?

Back 66

 What did I do yesterday that helped the Development Team meet the Sprint Goal?
 What will I do today to help the Development Team meet the Sprint Goal?
 Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

Front 67

What does the Development Team often do right after the Daily Scrum?

Back 67

often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint's work

Front 68

What is the Scrum Master's role in the Daily Scrum?

Back 68

The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.

Front 69

Who conducts the Daily Scrum?

Back 69

The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum.

Front 70

Which rule of the Daily Scrum does the Scrum Master enforce?

Back 70

that only Development Team members participate in the Daily Scrum

Front 71

What are the benefits of the Daily Scrum?

Back 71

Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team's level of knowledge. This is a key inspect and adapt meeting.

Front 72

Why is the Sprint Review held?

Back 72

to inspect the Increment and adapt the Product Backlog if needed

Front 73

What is a Sprint Review?

Back 73

an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration

Front 74

What is the time-box for a Sprint Review (on a one-month Sprint)?

Back 74

Four hours

Front 75

What is the Scrum Master's role in a Sprint Review?

Back 75

The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches all to keep it within the time-box.

Front 76

What are the elements of a Sprint Review?

Back 76

 Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
 The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done";
 The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
 The Development Team demonstrates the work that it has "Done" and answers questions about the Increment;
 The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date (if needed);
 The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
 Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
 Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.

Front 77

What is the purpose of a Sprint Retrospective?

Back 77

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint

Front 78

What is the time-box for a Sprint Retrospective (for a one-month Sprint)?

Back 78

three hours

Front 79

What is the role of the Scrum Master in the Sprint Retrospective?

Back 79

The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches all to keep it within the time-box. The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process.

Front 80

What elements take place in a Sprint Retrospective?

Back 80

 Inspect how the last Sprint went with regards to people, relationships, process, and tools;
 Identify and order the major items that went well and potential improvements; and,
 Create a plan for implementing improvements to the way the Scrum Team does its work.

Front 81

What should the Scrum Team have identified by the end of the Sprint Retrospective?

Back 81

the Scrum Team should have identified improvements that it will implement in the next Sprint

Front 82

Do Scrum Teams have to wait until the Sprint Retrospective to implement changes?

Back 82

Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.

Front 83

What are the Scrum Artifacts

Back 83

The Product Backlog, Product Increment

Front 84

What are the Scrum Activities

Back 84

Product Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective

Front 85

What is the Product Backlog?

Back 85

The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.

Front 86

Who is responsible for the Product Backlog?

Back 86

The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.

Front 87

When is the Product Backlog complete?

Back 87

A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves.

Front 88

What attributes do product backlog items have?

Back 88

description, order, estimate and value

Front 89

When do requirements stop changing for a Scrum Team?

Back 89

Requirements never stop changing, so a Product Backlog is a living artifact. Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.

Front 90

If multiple Scrum Teams are working on the same product, how many Product Backlogs are there?

Back 90

One Product Backlog is used to describe the upcoming work on the product. A Product Backlog attribute that groups items may then be employed.

Front 91

What goes into Product Backlog refinement?

Back 91

an ongoing process of adding detail, estimates, and order to items in the Product Backlog

Front 92

Who works on Product Backlog refinement

Back 92

The Product Owner & the Development Team

Front 93

How much capacity should the Development Team devote to Product Backlog refinement?

Back 93

no more than 10%

Front 94

When can the Product Owner update the Product Backlog?

Back 94

at their discretion - at any time

Front 95

Who is responsible for all estimates?

Back 95

the Development Team

Front 96

Can the Product Owner participate in estimates?

Back 96

The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate.

Front 97

When does the Product Owner reveal the progress towards goal reporting they track?

Back 97

Always - This information is made transparent to all stakeholders.

Front 98

Name some trending tools for measuring progress towards goal reporting.

Back 98

burn-downs, burn-ups, or cumulative flows

Front 99

Should predictive models be used in progress tracking for Scrum Teams?

Back 99

Only what has happened may be used for forward-looking decision-making.

Front 100

What does the Development Team mean by "Sprint Backlog?"

Back 100

The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a "Done" Increment.

Front 101

What should the Sprint Backlog be used for?

Back 101

The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum.

Front 102

Who can modify the Sprint Backlog?

Back 102

The Development Team as they work through the plan and learn more about work needed to achieve the Sprint Goal.

Front 103

Where does new work the Development Team learns about go during a Sprint?

Back 103

in the Sprint Backlog

Front 104

What is the increment?

Back 104

The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.

Front 105

What must happen to the increment at the end of a Sprint?

Back 105

the new Increment must be "Done," which means it must be in useable condition and meet the Scrum Team's definition of "Done."

Front 106

If the Product Owner doesn't intend to use the increment at the end of a Sprint, must it be in usable condition?

Back 106

It must be in usable condition regardless of whether the Product Owner decides to actually release it.

Front 107

What is the Scrum Master's role with artifacts?

Back 107

The Scrum Master must work with the Product Owner, Development Team, and other involved parties to understand if the artifacts are completely transparent.

Front 108

What practices can the Scrum Master use if transparency is incomplete?

Back 108

the Scrum Master must help everyone apply the most appropriate practices in the absence of complete transparency. A Scrum Master can detect incomplete transparency by inspecting the artifacts, sensing patterns, listening closely to what is being said, and detecting differences between expected and real results.
The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change. Transparency doesn't occur overnight, but is a path.

Front 109

What is the important part of "done" for a Scrum team?

Back 109

Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency.

Front 110

Does the definition of "done" stay the same for each Sprint?

Back 110

As Scrum Teams mature, it is expected that their definitions of "Done" will expand to include more stringent criteria for higher quality.

Front 111

Should the definition of "done" for a product or system differ by Scrum Team?

Back 111

Any one product or system should have a definition of "Done" that is a standard for any work done on it.

Front 112

When do Development Team members take ownership of Sprint Backlog items?

Back 112

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

Front 113

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

Back 113

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

Front 114

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

Back 114

Nail down the complete architecture and infrastructure.
Develop a plan for the rest of the project.

Front 115

When is a system's architecture decided?

Back 115

Throughout the project, as understanding emerges and the Development Team learns more about the project.

Front 116

What relationship does Scrum have to technical practices?

Back 116

Scrum Development Teams with excellent technical practices will likely be more successful.

Front 117

What are two (2) reasons to automate the software build process?

Back 117

Automation improves the quality of software by making builds less error-prone.
To get feedback on changes to the code early and often.

Front 118

What happens during Sprint 0?

Back 118

There is no such thing as Sprint 0.
Scrum does not include the concept of a Sprint 0. "Sprint 0" has become a phrase misused to describe the planning that occurs prior to the first sprint.

Front 119

What is code coverage?

Back 119

The degree to which the system under test has been exercised by tests.

Front 120

Which is a benefit of establishing naming standards for code?

Back 120

To make the code more readable.

Front 121

What does a test written with Test Driven Development represent?

Back 121

A technical requirement that must be satisfied.
Since the test exists before the code that makes it pass, the test acts a requirement of the system under test.

Front 122

What are two (2) ways a Development Team can ensure a good application architecture?

Back 122

The Development Team should have a set of guiding architecture principles that every Development Team member understands and follows when writing code
The Development Team plans some time each Sprint to discuss the architecture needed for the features planned in that Sprint.

Front 123

The definition of "Done" describes the work that must be completed for every Product Backlog item before it can be deemed releasable. What should the Development Team do when, during the Sprint, it finds out that a problem outside of their control blocks them from doing all this work?

Back 123

Immediately raise the issue to the Scrum Master as an impediment.

Front 124

What are some shortcomings of code coverage as a measurement for how well a system or product is tested? (choose 3 answers)

Back 124

Code coverage does not ensure that the most important or highest risk areas of the code are being exercised by tests.
Code coverage does not necessarily provide functional coverage
Could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing coverage.

Front 125

Who is responsible for registering the work estimates during a Sprint?

Back 125

The Development Team

Front 126

What is the Sprint Review?

Back 126

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

Front 127

What is Scrum to Agile?

Back 127

Scrum is the most broadly used project management method used in Agile.

Front 128

What are the items in the Agile Manifesto?

Back 128

We value:
Individuals and Interactions over Processes and Tools
Working Software over Comprehensive Documentation
Customer Collaboration over Contract Negotiation
Responding to Change over Following a Plan

Front 129

What is the Vision Statement?

Back 129

The Vision Statement provides a concise description of the goals of the project which help the team stay focused on what is important from the organization point of view.

Front 130

What is the Product Roadmap?

Back 130

The Product Roadmap is an initial visual timeline of major product features to be delivered and is normally created by the Product Owner.

Front 131

What are Stories?

Back 131

Stories are requirements that have been turned into deliverable features.

Front 132

Who writes Stories?

Back 132

Stories are normally written by the Product Owner based on requirements that come from the customer.

Front 133

Where are Stories housed?

Back 133

Stories are housed in the Product Backlog.

Front 134

Give an overview of the activities in a Sprint

Back 134

1. Sprint Planning Meetings take place to decide what will go into a Sprint. The Product Owner decides the Priority of the requirements (stories).
2. The Stories make up the Sprint Backlog.
3. The Team breaks down these Stories into Tasks.
4. The Team agrees to deliver these Tasks during the Sprint.
5. The Team holds a daily 15 minute Scrum to collaborate with each other.
6. At the end of the Sprint, the Team demonstrates the completed stories (tasks) to the customer in the Sprint Demo in the Sprint Review meeting.
7. The last activity is the Sprint Retrospective where the team reviews the Sprint and looks for ways of improving (lessons learned).
8. During All: The Scrum Master makes sure the Scrum process is followed entirely and offers coaching to everyone involved.

Front 135

If there is more than one Scrum Team working on a single project, how is "done" defined?

Back 135

Each Scrum Team will define its own definition of "done" and deliver its items based on that definition. The integration of each team's definitions should be capable of creating potentially releasable increments at the project level.

Front 136

What does a project burndown chart show?

Back 136

The project burndown chart shows the amount of remaining work, instead of amount of completed work; therefore, the line for actual performance goes downward as we proceed and the faster it goes down, the happier we will be!

Front 137

What does the vertical axis on a burndown typical represent?

Back 137

The vertical axis typically shows the Product Backlog - the remaining work.

Front 138

What does the horizontal axis on a burndown chart typically represent?

Back 138

The horizontal axis typically shows the time that has passed - either the time from the beginning or the number of sprints passed.

Front 139

Why is a line representing a uniform distribution of line added to a burndown chart?

Back 139

The line acts as planned progress.

Front 140

If the actual burndown progress is mostly above the planned progress line, what does this mean?

Back 140

This means that we are behind our planned progress.

Front 141

If the actual burndown progress is mostly below the progress line, what does this mean?

Back 141

This means that we are mostly ahead of schedule.

Front 142

Are burndown charts done only at the project level?

Back 142

No. Burndown charts can and should also be done at the Sprint level.

Front 143

Does Sprint Progress have to be represented in a burndown chart?

Back 143

No. As long as the progress is documented and openly visible to everyone.

Front 144

What is a Product Owner's responsibility?

Back 144

Optimizing the value of the work the Development Team does.

Front 145

Can exploratory tests be automated?

Back 145

No.

Front 146

Who refines the Product Backlog?

Back 146

The Development Team and the Product Owner.

Front 147

If an outside issue is preventing a Development Team from doing all of their work, what should they do?

Back 147

Immediately raise the issue to the Scrum Master as an impediment.

Front 148

What is test first development?

Back 148

Designing the tests before satisfying them.

Front 149

When does the Development Team participate in Product Backlog Refinement?

Back 149

Anytime during the Sprint.

Front 150

What does code coverage show?

Back 150

Code being exercised by tests.