Scrum Master Flashcards

Obtain exam requirements

1
Q

Which of the following might the Scrum Team discuss during a Sprint Retrospective?

a) Methods of communication
b) The way the Scrum Team does Sprint Planning
c) Skills needed to improve the Developers ability to deliver
d) It’s Definition of Done
e) All of the above

A

e) All of the above

Tijdens een Sprint Retrospective kan het Scrum Team elk aspect van hun samenwerking en processen bespreken dat invloed heeft op hun effectiviteit en efficiëntie. Dit omvat methoden van communicatie, de manier waarop Sprint Planning wordt uitgevoerd, de vaardigheden die nodig zijn om beter te kunnen leveren, en de Definition of Done. Het doel van de Retrospective is om continu te verbeteren en aanpassingen door te voeren die de prestaties en tevredenheid van het team vergroten. Daarom is het belangrijk om een breed scala aan onderwerpen te overwegen die kunnen bijdragen aan deze verbeteringen.

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

While under development, the environment in which a product will be used changes and emerges. What is the effect on the Product Backlog?

a) There is no effect, because it has to stay the same until the end of the project
b) It is converted into requirements specification to ensure stability
c) It is archived and a new product backlog is created to take its place
d) It evolves to reflect what the product needs to be most valuable

A

d) It evolves to reflect what the product needs to be most valuable

In Scrum is de Product Backlog een dynamisch en levend document. Het moet voortdurend evolueren om de meest waardevolle en relevante werkitems te bevatten, gebaseerd op de veranderende behoeften en inzichten tijdens de ontwikkeling van het product. Dit iteratieve proces stelt teams in staat om snel te reageren op veranderingen en voortdurend de waarde van het product te maximaliseren. De aanpassingen aan de Product Backlog zorgen ervoor dat het team altijd werkt aan de meest waardevolle en prioritaire items.

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

Which of the following are the Developers not responsible for?

a) Monitoring and optimizing the work required to meet the sprint goal at least daily
b) Planning how to meet the Sprint Goal
c) Selecting the Product Owner
d) Resolving internal conflicts
e) Monitoring and increasing productivity

A

c) Selecting the Product Owner

In Scrum zijn de Developers verantwoordelijk voor veel aspecten van hun werk en samenwerking, waaronder het plannen van hun werk, het monitoren van de voortgang, en het optimaliseren van hun productiviteit. Echter, het selecteren van de Product Owner is niet hun verantwoordelijkheid. Dit wordt meestal gedaan door de organisatie, het management of een andere autoriteit binnen het bedrijf, aangezien de Product Owner een cruciale rol speelt in het vertegenwoordigen van de belangen van de stakeholders en het beheren van de Product Backlog.

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

Which topics should be discussed in the Sprint Review?

a) The process
b) Sprint results
c) Coding practices
d) All of the above

A

b) Sprint results

De Sprint Review is gericht op de resultaten van de sprint. Tijdens deze bijeenkomst demonstreert het team het voltooide werk aan de stakeholders en verzamelt feedback. Dit helpt bij het afstemmen van toekomstige werkprioriteiten en bij het maken van aanpassingen aan de Product Backlog. De Sprint Review is een kans voor inspectie en aanpassing op het niveau van het product en de Product Backlog, terwijl de Sprint Retrospective zich richt op het proces en teamdynamiek.

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

Which phrase best describes a Product Owner?

a) Team manager
b) Value optimizer
c) Requirements engineer
d) Go between Developers and customers

A

b) Value optimizer

De rol van de Product Owner is gericht op het maximaliseren van de waarde van het product dat door het Scrum Team wordt ontwikkeld. Dit omvat het definiëren en prioriteren van de Product Backlog-items op basis van waarde, het begrijpen van de behoeften en verwachtingen van de stakeholders, en ervoor zorgen dat het Development Team werkt aan de juiste dingen op het juiste moment. Het optimaliseren van waarde is de kern van wat de Product Owner doet en is de beste beschrijving van hun rol.

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

Which output from the Sprint Planning meeting provides the Developers with a target and overarching direction for the Sprint?

a) The release plan
b) The sprint goal
c) Sprint review minutes
d) The sprint backlog

A

b) The sprint goal

Tijdens de Sprint Planning meeting formuleert het Scrum Team de Sprint Goal. De Sprint Goal is een beknopte verklaring die beschrijft wat het Scrum Team tijdens de sprint wil bereiken. Het biedt een richting en doel voor het team om zich op te concentreren tijdens de sprint. Het is bedoeld als een richtlijn en dient als een focuspunt om ervoor te zorgen dat alle activiteiten en beslissingen tijdens de sprint bijdragen aan het bereiken van dit doel.

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

A Sprint Review is the only time that stakeholders and the Scrum Team come together.

a) True
b) False

A

b) False

Een Sprint Review is een belangrijke gebeurtenis in Scrum waarbij het Scrum Team (waaronder de Product Owner, Scrum Master en Developers) en stakeholders samenkomen om de resultaten van de sprint te inspecteren en feedback te verzamelen. Hoewel de Sprint Review een formele gelegenheid is om te demonstreren wat er tijdens de sprint is bereikt en om input te krijgen van stakeholders, is het niet de enige keer dat ze samenkomen.

Stakeholders kunnen betrokken zijn bij verschillende stadia van het ontwikkelingsproces, zoals het verstrekken van input voor de Product Backlog, het bijwonen van Sprint Planning om prioriteiten te begrijpen, en het verstrekken van feedback tijdens de Sprint zelf. Daarnaast kan er informele communicatie en samenwerking plaatsvinden tussen het Scrum Team en stakeholders gedurende de sprint, niet alleen tijdens de Sprint Review.

Daarom is stelling b) False correct: de Sprint Review is niet de enige keer dat stakeholders en het Scrum Team samenkomen; er zijn verschillende andere gelegenheden voor interactie en betrokkenheid gedurende het gehele ontwikkelingsproces.

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

Who creates a Product Backlog item’s estimate?

a) The Developers alone.
b) The Product Owner with input from the Developers.
c) The most senior people in the organization, including architects and subject matter experts.
d) The Developers after clarifying requirements with the Product Owner
e) The Scrum Master.

A

d) The Developers after clarifying requirements with the Product Owner.

In Scrum zijn de Developers verantwoordelijk voor het schatten van de Product Backlog-items omdat zij degenen zijn die het werk zullen uitvoeren en dus het beste in staat zijn om in te schatten hoeveel inspanning elk item zal kosten. Voordat ze een schatting maken, moeten ze ervoor zorgen dat ze de vereisten volledig begrijpen, wat vaak inhoudt dat ze de vereisten verduidelijken met de Product Owner. Dit helpt hen om realistische en nauwkeurige schattingen te maken.

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

When multiple scrum teams are working on the same project, they should make sure that each team has different Sprint start dates

a) True
b) False

A

b) False

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

During a Sprint , when is new work or further decomposition of work added to the Sprint Backlog

a) During the Daily Scrum after the Developers approves them.
b) When the Product Owner identifies a new work.
c) When the Scrum Master has time to enter them.
d) As soon as possible after they are identified.

A

d) As soon as possible after they are identified.

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

During a Sprint Retrospective, for what is the Scrum Master Responsible?

a) Prioritizing the resulting action items
b) Summarizing and reporting the discussions to management
c) Acting as scribe to capture the Developers answers
d) Facilitating and also participating as a Scrum Team member

A

d) Facilitating and also participating as a Scrum Team member

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

A properly functioning Scrum Team will have at least one Release Sprint and may well have several

a) True
b) False

A

b) False

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

Drawing a trend line through a release burndown chart indicates?

a) When all Sprint Backlog work will be completed and the Scrum Team will be released for other work
b) When the work remaining will likely be completed if nothing changes on the backlog or the Developers
c) Cost of the project
d) When the project will be over if the Product Owner removes work that is equal in effort to any new work that is added

A

b) When the work remaining will likely be completed if nothing changes on the backlog or the Developers

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

Which three activities will a Product Owner likely engage in during a Sprint?

a) Update the Sprint burndown chart
b) Prioritize the Developers activities
c) Run the Daily Scrum
d) Work with the stakeholders
e) Provide feedback
f) Answer questions from the Developers about items in the current Sprint

A

d) Work with the stakeholders
e) Provide feedback
f) Answer questions from, the Developers about items in the current Sprint

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

What are some consequences if the Developers do not have a consistent Definition of Done from Sprint to Sprint?

a) The Developers may not know how many Product Backlog items they can do in a Sprint
b) The Product Owner may not know what he/she is inspecting at the Sprint Review
c) The Product Owner may be unable to gauge the progress toward his/her goals
d) The Developers, may not know what work is entailed in completing selected Product Backlog items
e) All of the above

A

e) All of the above

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

The Developers have forecast an amount of Product Backlog items
they think they can accomplish and a Sprint.
Who determines how the Developers accomplish this work?

a) The various functional managers that the Team members report to
b) Knowledgeable architects or managers
c) The Scrum Master
d) The Developers

A

d) The Developers

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

A Scrum Master is introducing Scrum to new Developers. The Developers have decided that a Retrospective is unnecessary.
What action should the Scrum Master take?

a) Comply with the decision of the self managing team
b) Begin facilitating productive, useful retrospectives
c) Consult with the Product Owner to see how he/she feels about the situation
d) Call a meeting between the Developers and senior management

A

b) Begin facilitating productive, useful retrospectives

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

The Product Owner determines how many Product Backlog items the Developers selects for a Sprint

a) True, accordingly to what was committed to stakeholders
b) True
c) False
d) True, but only after confirmation by the resource manager that the Scrum Team has enough capacity
e) False, the Scrum Master does that
f) False, capacity and commitment are the Project Manager’s responsibility

A

c) False

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

choose as many as apply

What are the benefits of self managing to the Scrum Team?

a) Management can remove a failing resource more easily
b) Increased feeling of accountability
c) Increased commitment
d) Increased creativity

A

b) Increased feeling of accountability
c) Increased commitment
d) Increased creativity

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

Which technique is the least productive way for the Scrum Master to ensure that the Developers communicates effectively with the Product Owner?

a) Teach the Developers to talk in terms of business needs and objectives
b) Act as a go between for them
c) Teach the Product Owner about the technologies employed during the Sprints
d) Monitor communications between them

A

d) Monitor communications between them

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

Every Scrum Team must have a Product Owner and a Scrum Master

a) Yes, and they must be 100% dedicated to each team
b) Yes, and each Scrum Team’s performance may be affected by their degree of participation as influenced by any other responsibilities (e.g. other teams for which they are also the SM or PO)
c) No

A

b) Yes, and each Scrum Team’s performance may be affected by their degree of participation as influenced by any other responsibilities (e.g. other teams for which they are also the SM or PO)

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

The Product Owner must ship each Sprint Increment

a) When it makes sense
b) Whenever the Increment is free of defects
c) Without exception
d) To make sure the Developers ar e done every Sprint

A

a) When it makes sense

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

When should the Sprint Retrospective be held?

a) At the beginning of the last Sprint
b) In the middle of each Sprint
c) Only at the end of the last Sprint
d) At the end of each Sprint

A

d) At the end of each Sprint

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

What are the responsibilities of a Tester Developer (choose 2)

a) There is no specific tester role
b) Everyone is responsible for quality in Scrum
c) Finding bugs to assure quality
d) Checking the work of the Developers

A

a) There is no specific tester role
b) Everyone is responsible for quality in Scrum

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

Who determines when it is appropriate to update the Sprint Backlog during a Sprint

a) The Developers
b) The Product Owner
c) The Project Manager
d) The Scrum Team

A

a) The Developers

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

What does it mean for a Developer to be cross functional?

a) Developers are cross skilled individuals who are able to contribute to do what is necessary to deliver an increment of software
b) Developers are not only developers but also business analysts, architects, developers, and testers
c) Developers are a virtual team drawing from separate teams of business analysts, architects, developers, and testers
d) Developers work closely with business analysts, architects, developers, and testers who are not on the team

A

a) Developers are cross skilled individuals who are able to contribute to do what is necessary to deliver an increment of software

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

What are two ways that architecture and infrastructure are handled in Scrum

a) They are discussed, determined and documented before the actual feature development Sprints
b) They are implemented along with functional development of the product
c) They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small
d) They are built by a separate team through the creation of an architectural runway

A

b) They are implemented along with functional development of the product
c) They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality

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

What is the tactic a Scrum Master should use to divide a group
of Developers into multiple Teams

a) Create teams based on their skills across multiple layers such as database, UI, etc.)
b) Ask the developers to divide themselves into teams
c) Ask the Product Owner to assign the people to
teams

A

b) Ask the developers to divide themselves into teams

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

At the end of a Sprint a Product Backlog item worked on during the
Sprint does not meet the Definition of Done. What two things should happen with the undone Product Backlog item?

a) Put it on the Product Backlog for the Product Owner to decide what to do with
b) Do not include the item in the Increment of this Sprint
c) If the stakeholders agree , the Product Owner can accept it and release it to the users
d) Review the item, add the “Done” part of the estimate to the velocity and create a Story for the remaining work

A

a) Put it on the Product Backlog for the Product Owner to decide what to do with
b) Do not include the item in the Increment of this Sprint

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

Which two ways to organize Developers are consistent with the Scrum values ?

a) Bring all the Developers together and let them self organize
b) Existing teams propose how they would like to go about organizing into the new structure
c) Managers collaborate to assign individuals to specific teams
d) The Chief Product Owner determines the new team structures and assignments
e) Managers personally re-assign current subordinates to new teams

A

a) Bring all the Developers together and let them self organize
b) Existing teams propose how they would like to go about organizing into the new structure

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

How much time is required after a Sprint to prepare for the next Sprint?

A. The break between Sprints is time-boxed to 1 week for 30 day sprints, and usually less for shorter sprints.
B. Enough time for the requirements for the next Sprint to be determined and documented.
C. Enough time for the Development team to finish the testing from the last Sprint.
D. None. A new Sprint starts immediately following the end of the
previous Sprint.
E. All of the above are allowed depending on the situation

A

D. None. A new Sprint starts immediately following the end of the
previous Sprint

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

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

In the Sprint Planning meeting, the Product Owner and the Development Team were unable to reach a clear understanding about the highest order Product Backlog items. Because of this, the Development Team couldn’t figure out how many Product Backlog items it could forecast for the
upcoming Sprint. They were able to agree on a Sprint Goal, however.
Which of the following two actions should the Scrum Master support? (Choose two.)

A. Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
B. Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyse, decompose, and create additional functionality during the Sprint.
C. Continue the Sprint Planning meeting past its time-box until an adequate num ber of Product Backlog items are well enough understood for the Development Team to make a complete forecast. Then start the Sprint.
D. Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
E. Ask everyone to take as much time as needed to analyse the Product Backlog first, and then reconvene another Sprint Planning meeting

A

B. Forecast the most likely Product Backlog items to meet the goal and create a Sprint Backlog based on a likely initial design and plan. Once the time-box for the Sprint Planning meeting is over, start the Sprint and continue to analyse, decompose, and create additional functionality during the Sprint.
D. Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.

If the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.

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

Which answer best describes the topics covered in Sprint Planning?

A. What to do and who will do it.
B. How conditions have changed and how the Product Backlog should evolve.
C. What can be done and how to do it.
D. What went wrong in the last Sprint and what to do differently this Sprint.
E. Who is on the team and what team member roles will be.

A

C. What can be done and how to do it.

Topic One: What can be done this Sprint?
Topic Two: How will the chosen work get done?

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

Which of the following is required by Scrum? (Choose all that apply.)

A. Sprint Retrospective.
B. Members must be stand up at the Daily Scrum.
C. Sprint Burndown Chart.
D. Release planning.
E. All of the above.

A

A. Sprint Retrospective.

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

What is the purpose of a Sprint Review?

A. To take time to judge the validity of the project.
B. To inspect the product increment with the stakeholders and collect feedback on next steps.
C. To review the Scrum Team’s activities and processes during the Sprint.
D. To build team sprint.

A

B. To inspect the product increment with the stakeholders and collect feedback on next steps.

inspect the Increment and adapt the Product Backlog if needed

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

Who determines when it is appropriate to update the Sprint Backlog during a Sprint?

A. The Project Manager.
B. The Development Team.
C. The Scrum Team.
D. The Product Owner

A

B. The Development Team.

The Development Team modifies the Sprint Backlog throughout the Sprint

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

The purpose of a Sprint is to produce a done Increment of product.

A. True
B. False

A

A. True

a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created

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

Who creates the definition of “Done”?

A. The Scrum Master as he/she is responsible for the Development Team’s productivity.
B. The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definition.
C. The Product Owner as he/she is responsible for the product’s success.
D. The development organization (or Development Team if none is available from the development organization).

A

D. The development organization (or Development Team if none is available from the development organization).

guidelines of the development organization - the Development Team - the
Development Teams on all the Scrum Teams must mutually define the definition of “Done.”

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

Five new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the other teams.
What should the Scrum Master do?

A. Teach the Product Owner to work with the lead developers on ordering Product Backlog in a way to avoid too much technical and development overlap during a Sprint.
B. Teach them that it is their responsibility to work with the other teams to create an integrated increment.
C. Collect the Sprint tasks from the teams at the end of their Sprint Planning and merge that into a consolidated plan for the entire Sprint.
D. Visit the five teams each day to inspect that their Sprint Backlogs are aligned.

A

Five new Scrum Teams have been created to build one product. A few of the developers on one of the Development Teams ask the Scrum Master how to coordinate their work with the other teams.

From the Nexus guide: Nexus Integration Team Members ensure the Scrum Teams within the Nexus understand and implement the practices and tools needed to detect dependencies, and frequently integrate all artifacts to the definition of “Done.” If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of “Done.”Although other sources say C is the correct answer, check the discussion on scrum.org community. The best reasons not to choose for C is that this will turn the 5 teams in 1 big team and it is not the task of the scrum master, the servant-leader to do this.

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

Which two things should the Development Team do during the first Sprint? (Choose two.)

A. Make up a plan for the rest of the project.
B. Analyze, describe, and document the requirements for the subsequent Sprints.
C. Develop at least one piece of functionality.
D. Analyze, design, and describe the complete architecture and infrastructure.
E. Create an increment of potentially releasable software.

A

C. Develop at least one piece of functionality.

E. Create an increment of potentially releasable software.

during which a “Done”, useable, and potentially releasable product Increment
is created

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

What are three ways Scrum promotes self-organization? (Choose three.)

A. By not allowing documentation.
B. By the Development Team deciding what work to do in a Sprint.
C. By preventing stakeholders from entering the development room.
D. By removing titles for Development Team members.
E. By being a lightweight framework

A

B. By the Development Team deciding what work to do in a Sprint.
D. By removing titles for Development Team members.
E. By being a lightweight framework

B: The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team.
D: Scrum recognizes no titles for Development Team members
E: The team model in Scrum is designed to optimize flexibility, creativity, and productivity

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

What is the key concern when multiple Development Teams are working from the same Product Backlog?

A. Minimizing dependencies between teams.
B. Clear definition of requirements.
C. Meeting original scope projections.
D. Making sure there’s enough work for everyone on every team.
E. Maximizing velocity.

A

A. Minimizing dependencies between teams.

From the Nexus guide: The difference is that more attention is paid to dependencies and interoperation between Scrum Teams

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

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

A. The event must happen at a set time.
B. The event must happen by a given time.
C. The event must take at least a minimum amount of time.
D. The event can take no more than a maximum amount of time

A

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

All events are time-boxed events, such that every event has a maximum
duration

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

Which outcome is expected as Scrum Teams mature?

A. They will improve their definition of “Done” to include more stringent criteria.
B. The Sprint Retrospectives will grow to be longer than 4 hours.
C. There is no need for a time-boxed Sprint, since time-boxes are only for new Scrum Teams.
D. Sprint Reviews will no longer be needed.
E. A Scrum Master is no longer needed since they are a mature team now.

A

A. They will improve their definition of “Done” to include more stringent criteria.

… to include more stringent criteria for higher quality.

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

The Product Owner must release each Increment to production.

A. When it makes sense.
B. To make sure the Development Team is done every Sprint.
C. Whenever the product is free of defects.
D. Without exception.

A

A. When it makes sense.

regardless of whether the Product Owner decides to release it.

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

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

A. To gather status and progress information to report to management.
B. To write down any changes to the Sprint Backlog, including adding new items, and tracking progress on the burn-down.
C. He or she does not have to be there; he or she only has to ensure the Development Team has a Daily Scrum.
D. To make sure every team member answers the three questions.

A

C. 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 ensures that the Development Team has the meeting

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

You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the front-end, one for the middle tier, one for the back-end, and one for
the interfaces and services.
This resembles what is known as component teams. But you have read
that it’s a good idea to have teams organized by feature.
What are the advantages of keeping component teams while starting Scrum?

A. There’s less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.
B. Component teams generally have the skills needed to create a working Increment of software that provides business value.
C. Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.
D. There are fewer cross-team dependencies than working in feature teams.

A

The correct advantages of keeping component teams while starting Scrum are:

A. There’s less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.
C. Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.

Let’s explain why the other options (B and D) are not correct:

B. Component teams generally have the skills needed to create a working Increment of software that provides business value.

This is not necessarily true. Component teams often specialize in a specific layer of the software, like the front-end or back-end, but may lack the end-to-end skills needed to deliver a complete, business-valuable Increment independently. Scrum encourages feature teams precisely because they have all the skills needed to deliver a complete Increment.

D. There are fewer cross-team dependencies than working in feature teams.

This is incorrect. Component teams often result in more cross-team dependencies because each team is dependent on other teams to deliver a complete feature. In contrast, feature teams can often deliver complete features with fewer dependencies on other teams.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
48
Q

How should Product Backlog items be chosen when multiple Scrum Teams work from the same Product Backlog?

A. The Scrum Team with the highest velocity pulls Product Backlog items first.
B. The Development Teams pull in work in agreement with the Product Owner.
C. The Product Owner should provide each team with its own Product Backlog.
D. Each Scrum Team takes an equal number of items.
E. The Product Owner decides

A

B. The Development Teams pull in work in agreement with the Product Owner.

solely up to the Development Team. Only the Development Team can assess
what it can accomplish

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

How often should Development Team membership change?

A. As needed, while taking into account a short term reduction in productivity.
B. Never, because it reduces productivity.
C. As needed, with no special allowance for changes in productivity.
D. Every Sprint to promote shared learning.

A

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

Development Teams are structured and empowered by the organization to organize and manage their own work. The resulting synergy optimizes the Development Team’s overall efficiency and effectiveness

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

Who should make sure everyone on the Development Team does his or her tasks for the Sprint?

A. The Project Manager.
B. The Product Owner.
C. The Scrum Master.
D. The Development Team.
E. All of the above.

A

D. The Development Team.

They are self-organizing. No one (not even the Scrum Master) tells the Development Team how

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

When is it most appropriate for a Development Team to change the definition of “Done”?

A. During Spring Planning.
B. Prior to starting a new Sprint.
C. During the Sprint Retrospective.
D. Prior to starting a new project

A

C. During the Sprint Retrospective.

by improving work processes or adapting the definition of “Done”, if appropriate

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

The Daily Scrum is an event that happens every day. What would be three key concerns if the frequency were to be lowered to every two or three days? (Choose three.)

A. Opportunities to inspect and adapt the Sprint Backlog are lost.
B. Impediments are raised and resolved more slowly.
C. The Product Owner cannot accurately report progress to the stakeholders.
D. Too much work is spent updating the Scrum board before the meeting.
E. The Scrum Master loses the ability to update the Gantt chart properly

A

A. Opportunities to inspect and adapt the Sprint Backlog are lost.
B. Impediments are raised and resolved more slowly.
(C.) The Product Owner cannot accurately report progress to the stakeholders.

Lowering the frequency of the Daily Scrum to every two or three days would introduce several key concerns. The most significant ones are:

A. Opportunities to inspect and adapt the Sprint Backlog are lost - Daily Scrums allow the team to frequently review and adjust the Sprint Backlog based on the current progress and any new information. If this opportunity is reduced, the team may miss timely adjustments that can improve the chances of meeting the Sprint Goal.

B. Impediments are raised and resolved more slowly - One of the main purposes of the Daily Scrum is to identify impediments as soon as possible so they can be addressed quickly. If the meetings are less frequent, there may be delays in identifying and resolving issues, which can hinder progress and reduce productivity.

C. The Product Owner cannot accurately report progress to the stakeholders - Although the Daily Scrum is primarily for the Development Team, it indirectly supports the Product Owner by providing up-to-date information on the team’s progress. Less frequent meetings can lead to outdated information, making it harder for the Product Owner to give accurate and current progress reports to stakeholders.

Concerns D and E are not relevant in the context of Scrum practices:

D. Too much work is spent updating the Scrum board before the meeting - This is not a key concern because the Scrum board should be continuously updated as work progresses, not just before meetings.

E. The Scrum Master loses the ability to update the Gantt chart properly - This concern is not applicable as Gantt charts are not a typical tool used within Scrum, which focuses on more agile and iterative tracking methods.

Therefore, the three key concerns are A, B, and C.

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

Which statement best describes Scrum?

A. A defined and predictive process that confirms to the principles of Scientific Management.
B. A complete methodology that defines how to develop software.
C. A cookbook that defines best practices for software development.
D. A framework within which complex products in complex environments are developed

A

D. A framework within which complex products in complex environments are developed

Scrum is a framework for developing, delivering, and sustaining complex products

54
Q

Which Scrum Values are exhibited by not building Product Backlog items that have low business value? (Choose three.)

A. Economic Value Added.
B. Respect.
C. Focus.
D. Earned Value.
E. Courage

A

B. Respect.
C. Focus.
E. Courage

the values of commitment, courage, focus, openness and respect

55
Q

Who creates a Product Backlog item’s estimate?

A. The Development Team after clarifying requirements with the Product Owner.
B. The Product Owner with input from the Development Team.
C. The most senior people in the organization, including architects and subject matter experts.
D. The Scrum Master.
E. The Development Team, alone.

A

A. The Development Team after clarifying requirements with the Product Owner.

The Development Team is responsible for all estimates. 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.

56
Q

Who starts the Daily Scrum?

A. The person coming in last. This encourages people to be on time and helps to stay within the time-box.
B. Who ever the Development Team decides should start.
C. The person who has the token.
D. The Scrum Master. This ensures that the Development Team has the meeting and stays within the time-box.
E. The person who last broke the build

A

B. Who ever the Development Team decides should start.

but the Development Team is responsible for conducting the Daily Scrum.

57
Q

What two factors are best considered when establishing the Sprint length? (Choose two.)

A. The organization has mandated similar length sprints.
B. The level of uncertainty over the technology to be used.
C. The frequency at which team formation can be changed.
D. The risk of being disconnected from the stakeholders.

A

B. The level of uncertainty over the technology to be used.
D. The risk of being disconnected from the stakeholders.

Sprints also limit risk

58
Q

What are two responsibilities of testers in a Development Team? (Choose two.)

A. Verifying the work of programmers.
B. Everyone in the Development Team is responsible for quality.
C. Tracking quality metrics.
D. Finding bugs.
E. Scrum has no “tester” role.

A

B. Everyone in the Development Team is responsible for quality.
E. Scrum has no “tester” role.

Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person

59
Q

What is the role of management in Scrum?

A. To facilitate the Scrum Teams with insights and resources that help them improve.
B. To monitor the Development Team’s productivity.
C. To identify and remove people that aren’t working hard enough.
D. To continually monitor staffing levels of the Development Team

A

A. To facilitate the Scrum Teams with insights and resources that help them improve.

Scrum Teams are self-organizing
Any answer that contradicts self-organizing is wrong

60
Q

Which technique is the best way the Scrum Master can ensure that the Development Team communicates effectively with the Product Owner?

A. Monitor communications between them and facilitate direct collaboration.
B. Teach the Development Team to talk in terms of business needs and objectives.
C. Teach the Product Owner about the technologies employed during the Sprints.
D. Act as a go-between for them.

A

A. Monitor communications between them and facilitate direct collaboration.

Facilitating Scrum events as requested or needed.

61
Q

Which phrase best describes a Product Owner?

A. Go-between development team and customers.
B. Value optimizer.
C. Requirements engineer.
D. Team manager.

A

B. Value optimizer.

The Product Owner is responsible for maximizing the value of the product

62
Q

During a Sprint Retrospective, for what is the Product Owner responsible?

A. Participating as a Scrum Team member.
B. Summarizing and reporting the discussions to the stakeholders that he/she represents in the Scrum Team.
C. Capturing requirements for the Product Backlog.
D. The Product Owner should not take part in Sprint Retrospectives.

A

A. Participating as a Scrum Team member.

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself

63
Q

Marian is the Product Owner envisioning a project for a new release of her product. She made a projection of a release date based upon a sustained velocity of 17 completed units of work per Sprint.
Over the first 3 Sprints, the average velocity was 13 for work that the Development Team estimated as 90% done. The Development Teams, feeling the need to meet the plan, figured that a velocity of 17 was within their reach.
A good way to continue is:

A. The Development Team makes sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.
B. Add enough people to the Development Team for the deadline to be made.
C. The opportunity to inspect and adapt is lost. Opaqueness has replaced transparency. Predictability has dropped below zero. The produced software is not usable. As the rules of Scrum have not been respected, it is the Scrum Master’s duty to assess whether repair is possible, or a restart with a more
reliable team. If not, the Scrum Master should cancel the project.
D. The Development Team should remind Marian to find funding for enough Release Sprints in which the remaining work can be done.

A

A. The Development Team makes sure that all of the selected scope per Sprint is as “Done” as possible. The undone work is estimated and added to the Sprint Backlog of the next Sprint, so it doesn’t mess up the Product Backlog.

A is the best answer because the other answers do not make sense. Work that is not completed should be assessed and prioritised against outstanding product backlog items before they are pulled onto the sprint backlog

64
Q

Multiple Scrum Teams working on the same product or system all select work from the same Product Backlog.

A. True
B. False

A

A. True

Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.

65
Q

For the purpose of transparency, when does Scrum say a new increment of working software must be available?

A. After the acceptance testing phase.
B. Before the release Sprint.
C. Every 3 Sprints.
D. At the end of every Sprint.
E. When the Product Owner asks to create one.

A

D. At the end of every Sprint.

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

66
Q

What is a Development Team responsible for? (Choose two.)

A. Resolving internal team conflicts.
B. Reporting productivity.
C. Selecting the Product Owner.
D. Organizing the work required to meet the Sprint Goal.

A

A. Resolving internal team conflicts.
D. Organizing the work required to meet the Sprint Goal.

Scrum Teams are self-organizing

67
Q

A Scrum Master is essentially the same thing as a traditional PM (Project Manager).
A. True
B. False

A

B. False

In scrum there is no role called project manager

68
Q

What is the time-box for the Sprint Planning meeting?

A. 4 Hours for a monthly Sprint.
B. 8 Hours for a monthly Sprint.
C. Monthly.
D. Whenever it is done.

A

B. 8 Hours for a monthly Sprint.

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

69
Q

For which is the Scrum Master responsible?

A. Managing the performance of the Scrum Team.
B. The meetings and the objectives that a Scrum Team sets for itself.
C. The Scrum framework being adopted and used properly.
D. Keeping track of resource allocation.

A

C. The Scrum framework being adopted and used properly.

The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide.

70
Q

Which of these may a Development Team deliver at the end of a Sprint?

A. Failing unit tests, to identify acceptance tests for the next Sprint.
B. An increment of software with minor known bugs in it.
C. An increment of working software that is “done”.
D. A single document, if that is what the Scrum Master asked for.

A

C. An increment of working software that is “done”.

a “Done”, useable, and potentially releasable product Increment is created

71
Q

Currently, your Development Teams are organized to address a single layer only (for example, front end, middle tier, back end, and interfaces).
What are three things to consider when deciding to move away from such component teams toward feature teams? (Choose three.)

A You cannot do Scrum without feature teams.
B Productivity may suffer when making this kind of move.
C Getting support from the business side first helps.
D Feature teams have less communication overhead.
E With feature teams, it is easier to calculate the productivity per team.

A

B Productivity may suffer when making this kind of move.
C Getting support from the business side first helps.
D Feature teams have less communication overhead.

Om deze vraag correct te beantwoorden, moeten we de context van Scrum en het verschil tussen component teams en feature teams begrijpen. In Scrum bevorderen feature teams de creatie van waardevolle, werkende software over verschillende lagen of componenten heen, in plaats van te focussen op slechts één aspect van de technologie stack. Laten we de opties analyseren:

Opties:
A. You cannot do Scrum without feature teams.

Dit is niet correct. Hoewel feature teams een best practice kunnen zijn in Scrum, is het niet onmogelijk om Scrum te doen met component teams, hoewel het uitdagender kan zijn.

B. Productivity may suffer when making this kind of move.

Dit is correct. Het veranderen van de teamstructuur kan leiden tot een tijdelijke daling van de productiviteit, omdat teamleden zich moeten aanpassen aan nieuwe rollen, verantwoordelijkheden en samenwerkingspatronen.

C. Getting support from the business side first, helps.

Dit is correct. Het hebben van steun van de zakelijke kant kan de transitie vergemakkelijken, aangezien er vaak veranderingen in de manier van werken en prioriteiten nodig zijn die de business kan beïnvloeden.

D. Feature teams have less communication overhead.

Dit is correct. Feature teams hebben minder communicatieoverhead omdat teamleden van verschillende disciplines samenwerken binnen hetzelfde team, wat de communicatie en samenwerking bevordert.

E. With feature teams, it is easier to calculate the productivity per team.

Dit is niet correct. Het berekenen van productiviteit kan variëren afhankelijk van de meetmethoden en het is niet per definitie makkelijker of moeilijker met feature teams.

Juiste antwoorden:
De drie juiste dingen om te overwegen bij de overgang van component teams naar feature teams zijn:

B. Productivity may suffer when making this kind of move.

Het is belangrijk om te erkennen dat er een leercurve en aanpassingsperiode kan zijn, wat tijdelijk de productiviteit kan beïnvloeden.

C. Getting support from the business side first, helps.

Ondersteuning van de zakelijke kant is cruciaal om ervoor te zorgen dat de veranderingen effectief worden doorgevoerd en om weerstand te minimaliseren.

D. Feature teams have less communication overhead.

Door multidisciplinaire teams te vormen, kan de communicatie en samenwerking binnen het team verbeteren, wat vaak resulteert in minder overhead en snellere besluitvorming.

Door deze overwegingen in acht te nemen, kan een organisatie beter voorbereid zijn op de uitdagingen en voordelen van de overgang naar feature teams binnen een Scrum-framework.

72
Q

A Development Team is required to deliver a done increment by the end of a Sprint. Select two statements that explain what ‘done’ means. (Choose two.)

A. All work the Development Team is willing to do.
B. Ready for integration.
C. No work left from the definition of “Done”.
D. Whatever the Product Owner defines as quality.
E. All work to create software that is ready to be released to end users.

A

C. No work left from the definition of “Done”.
E. All work to create software that is ready to be released to end users.

The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.”

73
Q

How should a Development Team deal with non-functional requirements?

A. Ensure every Increment meets them.
B. Make sure the release department understands these requirements, but it is not the Development Team’s responsibility.
C. Handle them during the Integration Sprint preceding the Release Sprint.
D. Assign them to the lead developers on the team.

A

A. Ensure every Increment meets them.

The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.”

74
Q

How much of the Sprint Backlog must be defined during the Sprint Planning event?
A. Just enough tasks for the Scrum Master to be confident in the Development Team’s understanding of the Sprint.
B. The entire Sprint Backlog must be identified and estimated by the end of the Sprint Planning meeting.
C. Enough so the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.
D. Just enough to understand design and architectural implications.

A

C. Enough so the Development Team can create its best forecast of what it can do, and to start the first several days of the Sprint.

However, enough work is planned during Sprint Planning for the Development Team to forecast what it believes it can do in the upcoming Sprint

Waarom is dit correct?
In de Sprint Planning wordt het werk voor de aankomende Sprint gepland. Het Development Team moet voldoende details uitwerken voor de geselecteerde Product Backlog-items (PBIs) om een realistische inschatting te maken van wat ze kunnen voltooien tijdens de Sprint. Dit betekent dat het team de eerste dagen van de Sprint kan starten zonder vertraging, terwijl verdere details kunnen worden uitgewerkt naarmate het werk vordert. Deze aanpak zorgt voor een goede balans tussen planning en flexibiliteit, wat essentieel is in Scrum.

75
Q

A Development Team asks their Product Owner to re-order the Product Backlog. The team is waiting for an external supplier to deliver a specific software component. Without that component there won’t be enough work in the next Sprint to occupy the full team. The Product Owner asks the Scrum Master for help.
What would be good advice to give the Product Owner?

A. Remind the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.
B. Tell the Product Owner to re-order the Product Backlog so the work involving the external component can be planned in a separate sprint.
C. Tell the Product Owner that the Product Backlog should be ordered to maximize utilization of the Development Team

A

A. Remind the Product Owner that his primary concern is the flow of value reflected in the ordering of the Product Backlog.

Maybe the best reason not to choose B or C is the word “Tell”

76
Q

Where are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

A. Put them on a separate list on the Scrum board, available for all to see.
B. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
C. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
D. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.
E. Add them to the definition of “Done” so the work is taken care of every Sprint.

A

B. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
E. Add them to the definition of “Done” so the work is taken care of every Sprint.

Do not introduce non-scrum artifacts

77
Q

What is the typical size for a Scrum Team?
A. 9.
B. Minimum of 7.
C. 7 plus or minus 2.
D. 10 or fewer.

A

D. 10 or fewer.

A Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. Generally smaller teams communicate better and are more productive

78
Q

Scrum has a role called “project manager.”
True
False

A

False

A Scrum Team has a Scrum Master, a Product Owner and Developers. As a whole they have all controls needed.

79
Q

When does the next Sprint begin?
(choose the best answer)

A. When the Product Owner is ready.
B. Immediately after the conclusion of the previous Sprint.
C. Next Monday.
D. Immediately following the next Sprint Planning.

A

B. Immediately after the conclusion of the previous Sprint.

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

80
Q

The length of a Sprint should be:
(choose the best answer)

A. Short enough to keep the business risk acceptable to the Product Owner.
B. Short enough to be able to synchronize the development work with other business events.
C. One month or less.
D. All of the above

A

D. All of the above

All of these choices are appropriate considerations in determining the length of a Sprint.

81
Q

The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.
(Which one the following answers is FALSE?)

A. As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges.
B. The Product Owner can help clarify or optimize the Sprint when asked by the Developers.
C. The Developers may work with the Product Owner to add or remove work if they find themselves with more or less capacity than expected.
D. The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.

A

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

The Sprint Backlog makes visible all of the work that the Developers identify as necessary to meet the Sprint Goal. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.

82
Q

When many Scrum Teams are working on a single product, what best describes the Definition of Done?
(choose the best answer)

A. Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.
B. It depends.
C. All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.

A

C. All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.

The Increment must be valuable and useful. This means that when many Scrum Teams are working on a single product, they are expected to adhere to a single Definition of Done for the Increment.

83
Q

When should a Developer on a Scrum Team be replaced?
(choose the best answer)

A. Never, it reduces productivity.
B. Every Sprint to promote shared learning.
C. As needed, while taking into account a short-term reduction in productivity.
D. As needed, with no special allowance for changes in productivity.

A

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

Scrum Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.

84
Q

The Product Backlog is ordered by:
(choose the best answer)

A. Size, where small items are at the top and large items are at the bottom.
B. Items are randomly arranged.
C. Risk, where safer items are at the top, and riskier items are at the bottom.
D. Least valuable items at the top to most valuable at the bottom.
E. Whatever is deemed most appropriate by the Product Owner.

A

E. Whatever is deemed most appropriate by the Product Owner.

The Product Owner is accountable for effective Product Backlog management. The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.

85
Q

Who is on the Scrum Team?
(choose the best three answers)

A. Project Manager.
B. Developers.
C. The Product Owner.
D. The Scrum Master.

A

B. Developers.
C. The Product Owner.
D. The Scrum Master.

The Scrum Team consists of the Scrum Master, the Product Owner and Developers. The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal.

86
Q

Which Scrum events are timeboxed?
(choose the best three answers)

A. Refinement.
B. Release Retrospective.
C. Sprint Review.
D. Sprint Planning.
E. Sprint Retrospective.
F. Release Testing.
G. Sprint Testing.

A

C. Sprint Review.
D. Sprint Planning.
E. Sprint Retrospective.

The Scrum Guide states that the Sprint Planning, Sprint Retrospectives, and Sprint Reviews are timeboxed events. Sprints are fixed length events of one month or less to create consistency, and the Daily Scrum is a 15-minute event.

87
Q

Who is responsible for managing the progress of work during a Sprint?
(choose the best answer)

A. The Product Owner.
B. The most junior member of the team.
C. The Developers.
D. The Scrum Master.

A

C. The Developers.

The Developers use the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.

88
Q

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?
(choose the best answer)

A. The Scrum Master
B. The Project Manager
C. The Product Owner
D. The Developers

A

C. The Product Owner

The Product Owner is the sole person responsible for ordering the Product Backlog. Their responsibilities include making the Product Backlog visible, transparent, and clear to all.

89
Q

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?
(choose the best answer)

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

A

D. All of the above.

90
Q

When does a Sprint conclude?
(choose the best answer)

A. When the Sprint Retrospective is complete.
B. When all the tasks are completed by the Developers.
C. When the Product Owner decides enough has been delivered to meet the Sprint Goal.
D. When all Product Backlog items meet their Definition of Done.

A

A. When the Sprint Retrospective is complete.

The Sprint is a container for the following timeboxed events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Sprints are fixed length events of one month or less to create consistency, and a new Sprint starts immediately after the conclusion of the previous Sprint.

The Sprint Retrospective concludes the Sprint, and is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter

Though not typical, a Sprint can end if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to end the Sprint prematurely.

91
Q

During a Sprint, a Developer determines that the Scrum Team will not be able to complete the items in their forecast. Who should be present to review and adjust the Product Backlog items selected?
(choose the best answer)

A. The Scrum Master, the project manager, and the Developers
B. The Developers.
C. The Product Owner and the Developers.
D. The Product Owner and all stakeholders.

A

C. The Product Owner and the Developers.

During the Sprint, scope may be clarified and re-negotiated between the Product Owner and the Developers as more is learned. It is important to be transparent when challenges arise since ultimately the entire Scrum Team is accountable for creating a valuable, useful Increment.

92
Q

The CEO asks the Developers to add a “very important” item to a Sprint that is in progress. What should the Developers do?
(choose the best answer)

A. Add the item to the Sprint Backlog for the next Sprint.
B. Add the item to the current Sprint Backlog and do whatever amount of work is necessary to meet the Sprint Goal while satisfying the CEO.
C. Discuss the item with the other members of the Scrum Team so the team can decide what to do.
D. Add the item to the current Sprint Backlog, drop an item of similar size, and reduce the Sprint Goal.

A

C. Discuss the item with the other members of the Scrum Team so the team can decide what to do.

The items selected for a Sprint have been selected as most valuable with the Product Owner during Sprint Planning. 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 Developers.

93
Q

What is the function or purpose of Management in Scrum?
(choose the best answer)

A. Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery.
B. Continually monitor staffing levels of the Scrum Team.
C. Identify and remove people that are not working hard enough.
D. Monitor the progress of the Developers on the Scrum Team.

A

A. Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery.

Management has no official role or accountability on a Scrum Team. However, management external to the Scrum Team is relevant in setting the vision and strategy to guide the overall direction of the organization.

94
Q

The timebox for a Daily Scrum is?
(choose the best answer)

A. 15 minutes.
B. 15 minutes for a 4-week sprint. For shorter Sprints it is usually shorter.
C. Two minutes per person.
D. 4 hours.
E. The same time of day every day

A

A. 15 minutes.

The Daily Scrum is always a 15-minute event. Because it is a short event, the timebox is not influenced by the Sprint length.

95
Q

True or False: It is mandatory that the product Increment be released to production at the end of each Sprint.
* True
* False

A

False

The product Increment should be usable at the end of every Sprint, but it does not have to be released.

96
Q

The timebox for the Sprint Planning event is?
(choose the best answer)

A. Monthly.
B. Whenever it is done.
C. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.
D. 4 hours.

A

C. 8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.

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

97
Q

The Developers should have all the skills needed to:
(choose the best answer)

A. Turn the Product Backlog items they select into an Increment of a useful and valuable product.
B. Complete the project as estimated when the date and cost are committed to the Product Owner.
C. Do all of the development work, except for specialized testing that requires additional tools and environments.

A

A. Turn the Product Backlog items they select into an Increment of a useful and valuable product.

The Developers are a group of professionals who do the work of delivering an Increment of done product at the end of each Sprint. As a team, Developers have all of the skills necessary to create a product Increment.

98
Q

True or False: When multiple Scrum Teams work together on the same product, each team should maintain a separate Product Backlog.
* True
* False

A

False

Products have one Product Backlog, regardless of how many Scrum Teams are used. Any other setup makes it difficult for the Developers to determine what they should work on.

99
Q

Who creates the Definition of Done?
(choose the best answer)

A. The Product Owner since they are responsible for the product’s success.
B. The Scrum Master since they are responsible for the productivity of the Developers.
C. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
D. The Scrum Team, in a collaborative effort where the result is the common denominator of all members’ definitions.

A

C. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

If the Definition of Done for an Increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

100
Q

Which of the following services is appropriate for a Scrum Master in regard to the Daily Scrum?
(choose the best answer)

A. Facilitate in a way that ensures each team member has a chance to speak.
B. Lead the discussions of the Developers.
C. Ensure that all 3 questions have been answered.
D. All answers apply.
E. Teach the Developers to keep the Daily Scrum within the 15 minute timebox.

A

E. Teach the Developers to keep the Daily Scrum within the 15 minute timebox.

The Scrum Master ensures that the Developers have the event, but the Developers are responsible for conducting the Daily Scrum. The Scrum Master teaches the Developers to keep the Daily Scrum within the 15-minute timebox. The Scrum Master enforces the rule that only members participate in the Daily Scrum.

101
Q

Which statement best describes Scrum?
(choose the best answer)

A. A cookbook that defines best practices for software development.
B. A defined and predictive process that conforms to the principles of Scientific Management.
C. A framework for creating complex products in complex environments.
D. A complete methodology that defines how to develop software.

A

C. A framework for creating complex products in complex environments.

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

102
Q

When does a Developer become the sole owner of an item on the Sprint Backlog?
(choose the best answer)

A. At the Sprint Planning event.
B. During the Daily Scrum.
C. Never. All Sprint Backlog items are “owned” by the Developers on the Scrum Team.
D. Whenever a team member can accommodate more work.

A

C. Never. All Sprint Backlog items are “owned” by the Developers on the Scrum Team.

The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, and the set of Product Backlog items selected for the Sprint are collectively owned by the Developers. No individual Developer can claim ownership over an item as this would block communication and collaboration. The Sprint Backlog is updated by the Developers throughout the Sprint as more is learned.

103
Q

How much work must the Developers complete for each Sprint?
(choose the best answer)

A. All development work and at least some testing.
B. Enough so that the Increment meets the Definition of Done.
C. As much as it can fit into the Sprint.
D. Analysis, design, programming, testing and documentation.

A

B. Enough so that the Increment meets the Definition of Done.

The purpose of each Sprint is to deliver useful and valuable Increments that adhere to the Scrum Team’s current Definition of Done.

104
Q

True or False: The Scrum Team must choose at least one high priority process improvement item, identified during the Sprint Retrospective, and place it in the Sprint Backlog.
* True
* False

A

False

An earlier version of the Scrum Guide prescribed the practice of placing one improvement in the Sprint Backlog. This was removed in the 2020 update to the Scrum Guide because it was felt to be too prescriptive. However, if this practice provides value to you then you should adopt it. It is simply not prescribed anymore, but can still be valuable.

105
Q

Which statement best describes a Product Owner’s responsibility?
(choose the best answer)

A. Directing the Developers.
B. Maximizing the value of the work the Scrum Team does.
C. Managing the project and ensuring that the work meets the commitments to the stakeholders.
D. Keep stakeholders from distracting the Developers.

A

B. Maximizing the value of the work the Scrum Team does.

The Product Owner is accountable for maximizing the value of the product and the work of the Scrum Team.

106
Q

Which of the following are examples of a Scrum Team practicing Scrum poorly or not exhibiting traits of a self-managing Scrum Team?
(choose the best three answers)

A. The Developers are collaboratively selecting their own work during the Sprint.
B. The Developers are working within the boundaries of their organizations functional description and nicely handing off work from analyst to developer to tester to integration.
C. Stakeholders attend the Daily Scrum to check on the Scrum Team’s progress.
D. The Developers have all the skills they need to create a valuable, useful Increment.
E. The Developers create their own Sprint Backlog, reflecting all work that is required to meet the Definition of Done.
F. The Developers invite external stakeholders to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog.

A

B. The Developers are working within the boundaries of their organizations functional description and nicely handing off work from analyst to developer to tester to integration.
C. Stakeholders attend the Daily Scrum to check on the Scrum Team’s progress.
F. The Developers invite external stakeholders to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog.

  • The Daily Scrum is for the Developers. It should not be used by external stakeholders to check progress.
  • During Sprint Planning the Scrum Team should be crafting the Sprint Goal based on the set of Product Backlog items selected for the Sprint. The Developers identify the necessary work to meet the Sprint Goal.
  • Scrum Team members do not have titles, and no sub-teams; such as testing, architecture, or operations are recognized. Accountability belongs with the Scrum Team as a whole, regardless of whether team members have specialized skills.
107
Q

Scrum is a proven and complete software development process.

  1. True.
  2. False.
A

This is false for three reasons:
1. Scrum is not a process or a methodology. Scrum is a lightweight framework.
2. Scrum can be used to develop any product, not just a software product.
3. Scrum self-describes as an incomplete framework.

This is explained in the Scrum Guide: Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. The Scrum framework is purposefully incomplete.

108
Q

Which of the following statements are true about the Scrum master role?

  1. The Scrum master cannot be one of the developers on the team.
  2. The Scrum master cannot also be the team’s product owner.
  3. The Scrum master cannot be one of the product’s stakeholder.
  4. The Scrum master can be a stakeholder and a developer at the same time.
A

Option 4 is correct.

There are no rules in the Scrum Guide that say a person cannot take on multiple roles or accountabilities at the same time. In fact, in small startups it’s not uncommon for the Scrum master to also be a stakeholder while also helping with development. Furthermore, if the product owner got sick, that person might even take on product owner accountabilities temporarily as well.

The only guidance the Scrum Guide provides about a Scrum master or product owner assuming development responsibilities to help build a product is that if so, they must participate in the daily Scrum as a developer: If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate [in the Daily Scrum] as Developers.

109
Q

The Scrum team is assembled, but the IT department has been slow to provision resources like laptops, software, build tools and test environments. The team does not want to start the first sprint next week given the lack of preparedness. How would you as the Scrum master recommend the team proceed?

  1. Explain to the organization that Sprint 0 exists to allow the team to get prepared for development.
  2. Ask the team to work toward the development of a small, valuable increment despite the lack of preparedness.
  3. Declare this an infrastructure sprint where developers simply configure their tools and software.
  4. Delay the start of the sprint until the organization can properly provision the required tools and infrastructure.
A

Option 2 is correct.

There is no such thing as an infrastructure sprint or a Sprint 0 in Scrum.

Every sprint must attempt to develop an increment of value that will be part of the final product.

No organization is ever sufficiently prepared to begin development. If Scrum teams wait for all their required tools to be provisioned and available before they started to work, it’s unlikely that any work will get done.

110
Q

A developer has completed a feature that, when integrated into the codebase, will create a valuable and usable increment. Completion of the sprint goal depends upon it. When should the developer integrate their work into the product?

  1. During the daily Scrum, after achieving consensus with the other developers.
  2. After the development sprint finishes with the consent of the Scrum master.
  3. Immediately so long as the work meets the team’s definition of done.
  4. During the sprint review so stakeholders can witness the integration.
A

Option 3 is correct.

If a developer completes any work that meets the definition of done, immediately integrate that work into the product. In fact, a developer doesn’t need anyone’s permission to integrate their work into the product. Integration, and ensuring that work does indeed integrate, is essential. If the work cannot be integrated into the product being built, it is not useful and it does not create a valid increment.

If a piece of work is complete and can be successfully integrated into the final product, it should be integrated immediately. Waiting serves no purpose and contradicts Scrum’s adherence to lean thinking.

111
Q

A developer has identified a troublesome and worrying security vulnerability in the codebase and has asked you, the Scrum master, what to do about it. Which of the following actions do you instruct the developer to take?

  1. Make this issue a top priority item in tomorrow’s daily Scrum.
  2. Discuss the issue with the product owner and plan to fix the issue in the next sprint.
  3. Discuss the issue with other developers right away.
  4. Raise the issue as a priority item during the next sprint planning meeting.
A

Option 3 is correct.

A serious security flaw in the codebase should be raised immediately with the development team.

Scrum provides a number of events, such as the daily Scrum and the sprint retrospective, to encourage discussion. However, these events should never preclude pragmatic or essential discussions between members of the team.

If an emergency arises, address it immediately. Don’t wait for a scheduled Scrum event to adapt to changing conditions.

112
Q

Under which circumstance are developers allowed to discuss product development directly with stakeholders?

  1. Developers can speak directly with stakeholders during the sprint retrospective.
  2. Developers can speak directly with stakeholders so long as the product owner is present.
  3. Developers can speak directly with stakeholders with permission from the Scrum master.
  4. Developers are not allowed to speak directly with stakeholders.
  5. Developers can speak directly with stakeholders at any time.
A

Option 5 is correct.

There are no rules in Scrum that restricts when a developer can talk to a stakeholder.

One of the Scrum pillars is transparency. One of the Scrum values is openness. What does it say about an organization’s transparency and openness if it restricts when a developer can talk to a stakeholder?

The product owner is responsible to speak with stakeholders and discover which features and functionality they value most.

However, there is nothing in the Scrum Guide that restricts discussions with developers about the sprint backlog, product backlog, sprint goal or anything else. In fact, Scrum encourages them.

113
Q

Human Resources has just hired the three new programmers that are required to sustain development progress. However, these programmers have arrived right in the middle of a four-week sprint.

As the Scrum master, when do you advise these programmers to join the development effort?

  1. At the moment they arrive.
  2. At the end of the current sprint, but before the next sprint begins.
  3. At the following day’s daily Scrum.
  4. During the next sprint planning event.
A

Option 1 is correct.

If your project needs programmers to assist in the development effort, why would you wait even one minute to add them to the team and get them contributing to the development effort?

Note that there is no delay in Scrum between the time when one sprint ends and the next sprint begins. When one sprint ends, the next sprint starts immediately.

114
Q

You have a well-functioning team of four developers. What impact will the addition of three new developers likely have on the existing team members’ productivity?

  1. Individual productivity will increase permanently.
  2. Individual productivity will increase over the short term.
  3. Individual productivity will decrease permanently.
  4. Individual productivity will decrease over the short term.
A

Option 4 is correct.

The onboarding process of new team members often pulls existing developers away from their normal routines. They spend time with new developers to explain the product, help them connect to GitHub, set up a printer and even find the restroom.

In the long run, individual productivity should go back to normal, but in the short term it will decrease.

115
Q

Developers are frustrated because peripheral tasks including quality control, user acceptance testing and documentation take away from their core development efforts, and subsequently put the project’s progress at risk.

How would you advise the team to move forward?

  1. Instruct the Scrum team to create a subteam dedicated to QA, UAT testing and documentation
  2. Tell the Scrum team to outsource QA, UAT and documentation to a third party.
  3. Have the product owner remove quality control, testing and documentation from the definition of done.
  4. Advise the Scrum team that they are responsible for all aspects of delivering a product increment.
A

Option 4 is correct.

There are no subteams in Scrum, nor are there any hierarchies of developers.

The Scrum Guide is clear about this: Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals.

If a backlog item requires documentation, or the definition of done requires a set of user acceptance tests (UATs), then it’s up to the individual development team members to complete those tasks.

The developers of the Scrum team are responsible for the end-to-end development of all features in the product backlog. This includes full compliance to any non-functional requirements that the definition of done demands.

116
Q

Unforeseen circumstances have reduced developer productivity, and halfway through the sprint it is clear that the sprint plan must change drastically for the team to achieve the sprint goal. What guidance would you, as the Scrum master, provide to the team?

  1. Tell the developers to cancel the development sprint and start a new sprint planning session.
  2. Instruct the developers to regroup and update the sprint plan as soon as possible.
  3. Advise the developers to dedicate time during the next daily Scrum to update the sprint goal.
  4. Tell the developers the sprint plan cannot change, and they must continue to work as planned toward the sprint goal.
A

Option 2 is correct.

If circumstances change and the developers must update their plan, they should do it immediately.

During the sprint, the sprint goal cannot change, nor can the Scrum master or developers cancel a sprint on a whim.

They can change the sprint plan, however. In fact, they should update the plan throughout the sprint as conditions change and more is learned about the product they are developing.

Developers should not wait for a scheduled event such as the daily Scrum to adapt their plan if it’s necessary.

Here’s what the Scrum Guide says about this: The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning.

117
Q

The Scrum framework is purposefully incomplete

  1. True
  2. False
A

True

The Scrum framework is purposefully incomplete

Only defining the parts required to implement scrum theory. Scrum is built upon by the collective intelligence of the people using it. Rather than providing people with detailed instructions, the rules of the scrum guide their relationscripts and interactions.

118
Q

The result of the Sprint Review is…

  1. Incomplete Product Backlog Items have been reviewed and returned to the top of the Product Backlog.
  2. A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
  3. The Increment has been demonstrated to Stakeholders
  4. Acceptance (or rejection) of all Product Backlog Items
A

2) A revised Product Backlog that defines the probable Product Backlog items for the next Sprint

As a a result of the Sprint Review, the Product Backlog may be adjusted to meet new opportunities.

119
Q

During Sprint Planning, every task must be estimated so the Developers can be sure they have the capacity to complete them in the Sprint

True
False

A

False

While many Scrum Teams do this, it is not required by Scrum. Estimation is not mentioned in the Scrum Guide.
Selecting how much can be completed within a Sprint may be challenging.
However, the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.

120
Q

During the Daily Scrum, the Developers must answer the “3 questions”

True or False?

A

False

The “3 questions” are a popular, but optional practices the Developers may use at the Daily Scrum. There are many other practices that can be used instead.

121
Q

The Scrum Master is a management role.

True or False?

A

True

The Scrum Master is a manager, but for the Scrum framework, rather than for the people in the Scrum Team.

122
Q

What happens when a Sprint Goal becomes obsolete?

  1. The Sprint may be cancelled by the Product Owner.
  2. The Product Owner, the Developers, and the Scrum Master negotiate what to do next.
  3. The Sprint continues without any changes.
  4. The Developers decide what to do next.
A
  1. The Sprint may be cancelled by the Product Owner.

The Product Owner has the authority to cancel a Sprint if the Sprint Goal becomes obsolete, although this is generally a rare occurance.

123
Q

Which of the following is a benefit of working inside timeboxes?

  1. It helps to limit work-in-progress.
  2. It helps the Product Owner know which attribute of the “Iron Triangle”to adjust.
  3. It ensures that all planned items will be finished.
  4. It increases the Scrum Team’s velocity.
A
  1. It helps to limit work-in-progress.

When working inside timeboxes, it is best to limit work-in-progress and get items done before moving on. Limiting work-in-progress is a lean concept that helps to manage waste.

124
Q

A Scrum Team must be 10 or fewer people

True or False?

A

False

Team size is recommended, rather than mandated by Scrum. This was always true even before the 2020 update. Here is the current guidance from the Scrum Guide:
“The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Team.”

125
Q

The Scrum Master must facilitate the Daily Scrum

True or False?

A

False

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team.
– The Scrum Guide

126
Q

Among the Developers, there is nobody with significant testing expertise. They should…

Select 2 answers.

  1. Raise this as an impediment which may require the assistance of the Scrum Master to resolve
  2. Produce an Increment that will be tested by a dedicated test team after the Sprint to guarantee the quality
  3. Quality is the responsibility of the Developers and they should undertake testing themselves to the best of their abilities
  4. Request for a specialist tester to join them and queue testing for them to do when they arrive in a later Sprint
A

1) Raise this as an impediment which may require the assistance of the Scrum Master to resolve
3) Quality is the responsibility of the Developers and they should undertake testing themselves to the best of their abilities

If we stop every time we hit a problem when developing a product we would rarely move forward. Developers should practise the “art of the possible” and do what they can to keep going. Leaving the testing for later or another team will increase risk and mean we do not produce Done Increments.
If this has become an Impediment then the Scrum Master has the responsibility to get involved.

127
Q

Which statement best describes a cross-functional team?

  1. All members of the team have all the skills required to create the Product
  2. The team has a good mix of skills
  3. The team has all competencies needed to accomplish the work
A

3) The team has all competencies needed to accomplish the work

Dit is echt een instinker. Goed lezen!

Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.
– The Scrum Guide
This means the team as a whole needs all the skills. It does not mean every person has to have all the skills.

128
Q

Who can do the work to ensure the Product Backlog is refined to a state that it is
useful?

Select 2 answers.

  1. The Developers, with support from the Product Owner who is still accountable for it
  2. The Product Owner
  3. Stakeholders
  4. The Business Analyst
A
  1. The Developers, with supportfrom the Product Owner who is still accountable for it
  2. The Product Owner

Ook goed lezen

The Developers who will be doing the work are responsible for the sizing.
The Product Owner may influence the Developers by helping them understand and select trade-offs.
– The Scrum Guide

129
Q

What factors will increase complexity? Select all that apply.

a) Larger number of people on the project
b) Longer duration of the project
c) Batching of a large number of features into one big release

A

All the provided factors (a, b, and c) will increase complexity in a project.

a) Larger number of people on the project - As the number of people involved in a project increases, so does the complexity of communication, coordination, and integration of work. More team members often lead to more potential for misunderstandings, miscommunications, and dependencies that need to be managed.

b) Longer duration of the project - The longer a project lasts, the more opportunities there are for changes in requirements, priorities, team composition, and external conditions. This can lead to increased complexity in managing the project timeline, scope, and resources.

c) Batching of a large number of features into one big release - Releasing a large number of features at once can create significant complexity in terms of integration, testing, and deployment. It increases the risk of defects, integration issues, and the potential need for rework, making it harder to ensure a smooth and successful release.

130
Q

Select all that apply. Empiricism provides:

a) Frequent feedback opportunities to obtain information that can be used to plan better and eliminate the uncertainty.
b) Frequent opportunities to discuss possibilities
c) Frequent opportunities to make informed decision thus reducing risk

A

The correct options are:

b) Frequent opportunities to discuss possibilities
c) Frequent opportunities to make informed decisions thus reducing risk

Scrum does embrace uncertainty and focuses on managing it through continuous inspection and adaptation rather than eliminating it entirely. Given this understanding, let’s reassess the options:

a) Frequent feedback opportunities to obtain information that can be used to plan better and eliminate the uncertainty - This option implies eliminating uncertainty, which is not the goal of Scrum. Scrum aims to manage and navigate uncertainty, not necessarily eliminate it.

b) Frequent opportunities to discuss possibilities - This option aligns with Scrum practices, where team members frequently come together to inspect progress, discuss options, and adapt their plans.

c) Frequent opportunities to make informed decisions thus reducing risk - This option correctly captures the essence of empiricism in Scrum. By gathering frequent feedback and making decisions based on that feedback, teams can reduce risk and make more informed decisions.

131
Q

Scrum effectively limits the risk of unknowingly doing something wrong by

a) Having a detailed and extensive risk management plan.
b) Having multiple checkpoints and a thorough review by
senior management at those checkpoints.
c) Using short iterations called sprints

A

c) Using short iterations called sprints

Scrum effectively limits the risk of unknowingly doing something wrong by:

c) ** Using short iterations called sprints** - In Scrum, work is divided into short, time-boxed iterations known as sprints, typically lasting two to four weeks. This approach allows teams to frequently inspect and adapt their work, identify issues early, and make necessary adjustments. By breaking the work into smaller chunks and regularly reviewing progress, Scrum helps to manage risk and ensure that any mistakes or missteps are caught and corrected quickly.

The other options do not align with Scrum principles:

a) Having a detailed and extensive risk management plan - While risk management is important, Scrum relies more on empirical process control and frequent inspection and adaptation rather than extensive upfront planning.

b) Having multiple checkpoints and a thorough review by senior management at those checkpoints - Scrum emphasizes team self-organization and continuous improvement through regular team reviews (e.g., Daily Scrums, Sprint Reviews) rather than relying on hierarchical reviews by senior management.

132
Q

Leeg mag weg

A