Scrum Master test 04

Question

Which three of the following are true about Scrum?

Answer 1

Each component of Scrum serves a specific purpose and is essential to Scrum's success.

Answer 2

Scrum is like traditional processes but with self-organization to replace Project Managers

Answer 3

Scrum is a methodology, where you can pick and choose which parts of Scrum you think will work for your environment

Answer 4

Scrum is a framework for developing and maintaining complex products.

Answer 5

Scrum is based on empiricism and lean thinking.

Answer 6

The Developers may not know how many items they can accomplish in a Sprint

Answer 7

The Product Owner may be unable to get gauge the progress toward his/her goals.

Answer 8

The Developers may not know what work is entailed in completing selected Product Backlog items.

Answer 9

The stakeholders may not know what they are inspecting at the Sprint Review.

Answer 10

All of the above.

Answer 11

Sprint Goal

Answer 12

Product Goal

Answer 13

Definition of Done

Answer 14

Product Release Date

Answer 15

Sprint Goal

Answer 16

Product Goal

Answer 17

Definition of Done

Answer 18

Product release date

Answer 19

Product Goal

Answer 20

Definition of Done

Answer 21

Sprint Goal

Answer 22

Commitment

Answer 23

Add them the Definition of Done

Answer 24

There are no NFRS on Scrum Projects

Answer 25

Have a separate Kanban team work on them

Answer 26

Address them during hardening or release Sprints

Answer 27

Pick a tool for the team and tell them to pilot it for three months

Answer 28

Use coaching techniques to get to the root cause of the disagreement

Answer 29

Call a meeting of the Developers' functional managers to make a decision

Answer 30

Involve the entire Scrum Team in the decision-making process

Answer 31

Do whatever it takes to keep the team busy

Answer 32

Identify options to ensure fully integrated increments

Answer 33

Have the Product Owner re-order the work to maintain the velocity of the team

Answer 34

Involve the Developers in the decision-making process

Answer 35

Incorrect, there are only two required topics, what, and how.

Answer 36

Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done?

Answer 37

When is the next release? Who will be working on what? Why should we do it?

Answer 38

What is the budget? What is the scope? What is the timeline?

Answer 39

Why is this Sprint valuable?

Answer 40

What can be Done this Sprint?

Answer 41

How will the chosen work get done?

Answer 42

Who is taking ownership for which story?

Answer 43

What is the duration until the next release?

Answer 44

What is the budget for this Sprint?

Answer 45

Developers

Answer 46

Scrum Master

Answer 47

Product Owner

Answer 48

Scrum Team

Answer 49

Ready for release

Answer 50

Fully integrated

Answer 51

Ready for integration

Answer 52

Product Owner sign-off

Answer 53

Whatever the developers were able to accomplish

Answer 54

Transparency

Answer 55

Inspection

Answer 56

Adaptation

Answer 57

Empiricism

Answer 58

It depends

Answer 59

Less than 10

Answer 60

7 plus or minus 2

Answer 61

Provide Estimates

Answer 62

Order the backlog

Answer 63

Commit to the Sprint

Answer 64

Perform user acceptance

Answer 65

Facilitate meetings

Answer 66

Champion Scrum

Answer 67

Perform release planning

Answer 68

Design the software

Answer 69

It is up to the Product Owner to decide

Answer 70

Complexity

Answer 71

The Developers pull in work in agreement with the Product Owner

Answer 72

Each Scrum Team takes an equal number of items.

Answer 73

The Product Owner should provide each team with its own Product Backlog

Answer 74

The Scrum Team with the highest velocity pulls Product Backlog items first.

Answer 75

Importance

Answer 76

Delivery of all promised requirements

Answer 77

Customer Satisfaction

Answer 78

Delivery within the planned time

Answer 79

Release Frequency

Answer 80

Within allocated budget

Answer 81

Time to Market

Answer 82

It is allowed to grow and change as more is learned about the product and its customers.

Answer 83

It is baselined to follow change management processes.

Answer 84

It contains all foreseeable tasks and requirements from which the Scrum team can develop and maintain a complete project plan.

Answer 85

It provides just enough information to enable a Scrum team to start the design phase of a product.

Answer 86

Business Analyst

Answer 87

Requirements Specialist

Answer 88

Value Optimizer

Answer 89

Team Velocity

Answer 90

Competitive Research

Answer 91

Customer Feedback

Answer 92

Unit Testing Results

Answer 93

Product Vision

Answer 94

MoSCoW Analysis

Answer 95

Product Backlog Order

Answer 96

Customer Feedback via Frequent Releases

Answer 97

User Acceptance Testing

Answer 98

Current Value

Answer 99

Team Velocity

Answer 100

Time to Market

Answer 101

Ability to Innovate

Answer 102

Scrum does not use evidence-based metrics

Answer 103

The team can work without the Product Owner for one Sprint if they are mature

Answer 104

A new Product Owner should be assigned

Answer 105

The Scrum Master should play the role

Answer 106

Work on technical user stories only

Answer 107

The Scrum Master

Answer 108

The Development Lead

Answer 109

Whoever is accountable for the product ROI

Answer 110

The entire team

Answer 111

Agile Program Manager

Answer 112

Portfolio Manager

Answer 113

Value Maximizer

Answer 114

Scope Minimizer

Answer 115

Servant Leader

Answer 116

Sprint Burndown Chart

Answer 117

Release Burndown Chart

Answer 118

Any means necessary to reflect work finished and work remaining

Answer 119

Cumulative Flow Diagram

Answer 120

Sprint Backlog

Answer 121

It is never baselined, it is a living artifact

Answer 122

Release Plan

Answer 123

Product Roadmap

Answer 124

The Shareholders

Answer 125

The Customer

Answer 126

The Chief Product Owner

Answer 127

Once a Year

Answer 128

Once a Month

Answer 129

Frequently as needed

Answer 130

Cancel the Sprint and start over

Answer 131

Add the features to the Product Backlog

Answer 132

Add the feature to the current Sprint

Answer 133

Discuss with the team the correct approach

Answer 134

Delivery of all promised requirements

Answer 135

Customer Satisfaction

Answer 136

Delivery within the planned time

Answer 137

Release Frequency

Answer 138

Within allocated budget

Answer 139

Time to Market

Answer 140

Ease of use by customers

Answer 141

Velocity of Developers

Answer 142

Percentage of functionality used by customers

Answer 143

Cost per feature delivered

Answer 144

Customer Satisfaction

Answer 145

Be available to the Scrum team for questions

Answer 146

Provide Project Status Reports

Answer 147

Create and clarify valuable requirements with customers

Answer 148

Value points are never used in Scrum

Answer 149

Value points are not mandatory but are a best practice for providing transparency in the order of the Product Backlog

Answer 150

Value points are the only way to ensure value is being measured in the Product

Answer 151

Let the team decide

Answer 152

It depends

Answer 153

Immediately following the first Sprint.

Answer 154

It depends on how many issues were raised at the Retrospective.

Answer 155

After the Sprint Backlog has been created.

Answer 156

Once the customer accepts the first Sprint Increment.

Answer 157

Leave it up to the stakeholder to decide if they should accept it.

Answer 158

Add it to the Product Backlog for prioritization by the Product Owner.

Answer 159

Remove it from the Sprint Review.

Answer 160

Change the Definition of Done during the Sprint.

Answer 161

Give the team partial credit for their effort and add it to the next Sprint Backlog.

Answer 162

Sprint Retrospectives

Answer 163

Standing up at the Daily Scrum

Answer 164

Burndown Charts

Answer 165

Release Planning Meetings

Answer 166

All of the above

Answer 167

Backlog Refinement

Answer 168

Daily Scrum

Answer 169

Sprint Review

Answer 170

Sprint Retrospective

Answer 171

Release Planning

Answer 172

Whenever they can't complete the forecast

Answer 173

With permission from the Scrum Master

Answer 174

If a key resource leaves the team

Answer 175

All of the above

Answer 176

There are no tester roles on Scrum

Answer 177

Everyone on the Team is responsible for quality

Answer 178

Updating the defect log

Answer 179

Performing acceptance testing

Answer 180

Preventing and finding defects

Answer 181

When the timebox expires

Answer 182

When the Sprint Backlog is complete

Answer 183

Whenever the Product Owner decides

Answer 184

When the tasks are complete

Answer 185

Implement SAFE

Answer 186

Create teams based upon skills sets and/or location

Answer 187

Ask the developers to divide themselves into teams.

Answer 188

Divide teams by features

Answer 189

It must be established before Sprint Planning

Answer 190

During Sprint Planning

Answer 191

During the Sprint

Answer 192

A Sprint Goal is not necessary

Answer 193

Estimate of work remaining over the rest of the Sprint

Answer 194

Performance of the Developers.

Answer 195

Hours spent on backlog items.

Answer 196

The level of effort accomplished to date.

Answer 197

Facilitate decision making and removing impediments.

Answer 198

Ensuring high value items are prioritized.

Answer 199

Preventing change to the Sprint Backlog.

Answer 200

Making sure meetings start and end on time.

Answer 201

Defines what is takes to get an Increment of work ready for release.

Answer 202

Helps the Developers forecast what they can accomplish in a Sprint.

Answer 203

Creates transparency as to what was accomplished at the Sprint Review.

Answer 204

Is a checklist for what needs to be included in technical documentation.

Answer 205

Ensure developers accomplish all their tasks.

Answer 206

Cancel them

Answer 207

Hold them every other Sprint

Answer 208

Facilitate effective Sprint Retrospectives

Answer 209

Escalate to management

Answer 210

The technical lead.

Answer 211

People with the skills necessary to create a releasable Increment.

Answer 212

At least one developer and tester.

Answer 213

Each team members focuses on their area of specialty: UI, Data, QA.

Answer 214

Each member designs, codes, and tests functionality from beginning to end.

Answer 215

The manager to whom he/she reports is responsible, because he/she has authority for hiring and firing

Answer 216

The Scrum Team is responsible because it is a self-managing Team.

Answer 217

Scrum Master is responsible because he/she needs to remove impediments

Answer 218

Product Owner is responsible because he/she controls the return on investment (ROI) of the work

Answer 219

Who is on the team and what team member roles will be

Answer 220

Why is this Sprint valuable, what can be done and how to do it

Answer 221

How conditions have changed and how the Product Backlog should evolve

Answer 222

What went wrong in the last Sprint and what to do differently this Sprint

Answer 223

Prior to starting a new project

Answer 224

During Sprint Planning

Answer 225

Whenever needed

Answer 226

During the Sprint Retrospective

Answer 227

Prior to starting a new Sprint

	Erstellt von Marko Luzanin vor 8 Monate

Nächster

Scrum Master test 04

Beschreibung

Zusammenfassung der Ressource

Frage 1

Frage 2

Frage 3

Frage 4

Frage 5

Frage 6

Frage 7

Frage 8

Frage 9

Frage 10

Frage 11

Frage 12

Frage 13

Frage 14

Frage 15

Frage 16

Frage 17

Frage 18

Frage 19

Frage 20

Frage 21

Frage 22

Frage 23

Frage 24

Frage 25

Frage 26

Frage 27

Frage 28

Frage 29

Frage 30

Frage 31

Frage 32

Frage 33

Frage 34

Frage 35

Frage 36

Frage 37

Frage 38

Frage 39

Frage 40

Frage 41

Frage 42

Frage 43

Frage 44

Frage 45

Frage 46

Frage 47

Frage 48

Frage 49

Frage 50

Frage 51

Frage 52

Frage 53

Frage 54

Frage 55

Frage 56

Frage 57

Frage 58

Frage 59

Frage 60

Frage 61

Frage 62

Frage 63

Frage 64

Frage 65

Frage 66

Frage 67

Frage 68

Frage 69

Frage 70

Frage 71

Frage 72

Frage 73

Frage 74

Frage 75

Frage 76