game of scrum

8/12/2019 Game of Scrum

1/39

QUESTION: After the Product Backlog has

been created by the Product Owner at thebeginning of a project, items cannot be added to

it or removed from itANSWER: FalseEXPLANATION: The Product Owner can

change the Product Backlog at any time. (What

they cannot add to is the Teams target in thecurrent Sprint.)


2/39

QUESTION: All communication between theTeam and Product Owner is required to go

through the ScrumMasterANSWER: False

EXPLANATION: Direct, open communication

between the Team and the Product Owner is

encouraged, as long as it doesnt disrupt the

Team


3/39

QUESTION: Product Backlog Items the Teamdoes not complete in a Sprint automatically get

added into the next SprintANSWER: False

EXPLANATION: Product Backlog Items the

Team does not complete in a Sprint

automatically get put back to the Product

Backlog, and prioritized by the Product Owner


4/39

QUESTION: During the Sprint, Team members

are permitted to switch tasks with each otherANSWER: TrueEXPLANATION: The Team is free to organize

the work of the Sprint in any way it chooses.


5/39

QUESTION: Every single person on the Team isrequired to have all the development skills

necessary to produce done Product Backlog

Items design, coding, testing, etc.ANSWER: FalseEXPLANATION: The Team as a whole must

have those skills, but each individual member is

not required to have all of them.


6/39

QUESTION: The Sprint Review should be

attended by the Team, Product Owner,

ScrumMaster, as well as other stakeholders (likecustomers or end users)ANSWER: TrueEXPLANATION: The Sprint Review should beattended by anyone whose opinion or input

would be useful to the Product Owner in the

inspection of whats been produced, or theadaptation of the Product Backlog.


7/39

QUESTION: In Scrum, most of the testing is

completed at the end of the project, just beforethe releaseANSWER: FalseEXPLANATION: Leaving important testing until

the end of a project creates significant risk. In

Scrum, we do as much testing as possible each

Sprint, in order to minimize or eliminate thetesting that is left until the end of the project.


8/39

QUESTION: In Scrum, as much testing as

possible is done during each Sprint, to ensurethat defects are found and fixed as early as

possibleANSWER: TrueEXPLANATION: In Scrum, we try to do as

much testing as possible each Sprint, in order to

minimize the testing that is left until the end ofthe project


9/39

QUESTION: In Scrum, the system architectureis finalized at the beginning of the projectANSWER: FalseEXPLANATION: In Scrum, the systemarchitecture is started at the beginning of a

project, but it continues to evolve during the

project, as new requirements emerge, and as the

Team discovers improvements


10/39

QUESTION: In the Sprint Planning meeting, the

Product Owner tells the Team how much theyneed to target in the SprintANSWER: FalseEXPLANATION: In the Sprint Planning meeting,the Team decides how much they can target in

the Sprint, free of pressure from the Product

Owner.


11/39

QUESTION: In the Sprint Retrospective the

Team, ScrumMaster and Product Owner discusshow to improve their process, practices and

way of workingANSWER: True

EXPLANATION: The purpose of the Sprint

Retrospective is for the Team, ScrumMaster and

Product Owner to collaborate and find ways to

improve their process, practices, and way of

working, within the Scrum framework.


12/39

QUESTION: It is recommended that customers,

end users, and other stakeholders be invited tothe Sprint ReviewANSWER: TrueEXPLANATION: The purpose of the Sprint

Review is to inspect and adapt the product

thats being built, and inviting customers, end

users, and other stakeholders to join will givemore and better insights.


13/39

QUESTION: It is recommended that

management should attend the Daily ScrumMeetingANSWER: FalseEXPLANATION: The purpose of the DailyScrum Meeting is for the Team to update each

other on progress, and make blocks visible to

everyone, inside a 15-minute timebox. If

management attends, it may disrupt this.


14/39

QUESTION: Items at the top of the Product Backlog

are typically smaller in size and have more detail than

those at the bottomANSWER: TrueEXPLANATION: On a regular basis, the Product

Owner and Team collaborate to groom the ProductBacklog. Product Backlog Grooming involves looking

at the next 2-3 Sprints worth of Product Backlog,

breaking the larger Product Backlog Items into smaller

pieces, and getting a more detailed understanding ofthe requirements.


15/39


16/39

QUESTION: It is recommended that the Sprint

Review be limited just to the Product Owner,Team and ScrumMasterANSWER: FalseEXPLANATION: The purpose of the SprintReview is to inspect and adapt the product

thats being built, and inviting customers, end

users, and other stakeholders to participate will

give more and better insights


17/39

QUESTION: The Definition of Done is

different for every single Product Backlog Item.

ANSWER: FalseEXPLANATION: The Definition of Done

should be relevant to most of the items on theProduct Backlog. (There may however be a

small number of Product Backlog Items which

because of their unique characteristics require a

one-off Definition of Done.)


18/39

QUESTION: The Definition of Done isdecided solely by the Product Owner.ANSWER: FalseEXPLANATION: The Definition of Done isdecided by the Team in collaboration with the

Product Owner, based on the needs of the

release, and the capabilities of the Team.


19/39

QUESTION: Team members are only required

to go to the Daily Scrum Meeting if they have

blocks to reportANSWER: FalseEXPLANATION: The Daily Scrum Meeting is

mandatory for all members of the Team who

are not on leave that day.


20/39

QUESTION: The purpose of the Sprint Review

is to see working product, find improvements tomake to the product, and know where we are

relative to the goals of the releaseANSWER: TrueEXPLANATION: The main purpose of the

Sprint Review is to see working product, find

improvements to make to the product, and

know where we are relative to the goals of the

release


21/39

QUESTION: The Product Backlog is a list of

tasks to be completed in the current SprintANSWER: FalseEXPLANATION: The list of tasks to be

completed in the current Sprint is the SprintBacklog. The Product Backlog is an ordered list

of features, functionality, and other work that

needs to be completed in the future.


22/39

QUESTION: The Product Owner can change

the future Product Backlog based on what theyobserve or feedback they receive in the Sprint

ReviewANSWER: TrueEXPLANATION: The Product Owner can

change the future Product Backlog at any time.

What they cannot change is the Teams target inthe current Sprint


23/39

QUESTION: The Product Owner decides the

Product Backlog content and prioritization, and

the Team decides how much to target in theSprintANSWER: TrueEXPLANATION: The Product Owner decides

the Product Backlog content and prioritization,

and the Team decides how much to target in the

Sprint. The Team should provide input to theProduct Owner on the content and

prioritization of the Product Backlog


24/39

QUESTION: The Product Owner is allowed to

make a change to the target of the Sprint, butonly if the Team agreesANSWER: FalseEXPLANATION: The Product Owner is not

allowed to change the target of the Sprint; their

only options are to terminate the current Sprint

and start a new one, or wait until the nextSprint


25/39

QUESTION: The Product Owner must remaincompletely silent in the Sprint Planning MeetingANSWER: FalseEXPLANATION: The Product Owner is allowed

to speak freely during the Sprint Planning

Meeting (unless they are doing so in a way that

is harmful or disruptive.)


26/39

QUESTION: Product Backlog Grooming is for

getting a better understanding of features in the

current Sprint

ANSWER: FalseEXPLANATION: Product Backlog Grooming

involves looking ahead to the next 2-3 Sprintsworth of Product Backlog, breaking the larger

Product Backlog Items into smaller pieces, and

getting a more details understanding of therequirements.


27/39

QUESTION: The Product Owner should create

the Product Backlog with input from any and all

of the following: customers, end users,stakeholders, and the TeamANSWER: TrueEXPLANATION: To create and prioritize the

Product Backlog effectively, the Product Owner

will need lots of input and advice from

customers and end users, stakeholders, andespecially from the Team. A great ScrumMaster

will help facilitate this.


28/39

QUESTION: The purpose of the Daily Scrum

Meeting is for the Team to update the ProductOwner and Management on progress and

blocksANSWER: FalseEXPLANATION: The purpose of the Daily

Scrum Meeting is for the Team to update each

other on progress and blocks. After the

meeting, the ScrumMaster will help with

removing the blocks.


29/39

QUESTION: The purpose of the Sprint Backlog

and Burndown Chart is to enable theScrumMaster to monitor the TeamANSWER: FalseEXPLANATION: The Team is responsible forself-organizing to achieve the target they set for

the Sprint, and the purpose of the Sprint

Backlog and Burndown Chart is to enable the

Team to self-organize and give them continuous

visibility during the Sprint.


30/39

QUESTION: The ScrumMaster offers theirassistance only when a Team member asks for

help.ANSWER: FalseEXPLANATION: The ScrumMaster should offer

assistance any time they see an opportunity to

serve the Team


31/39

QUESTION: The Team works together in theSprint Planning Meeting to decide how much to

target in the SprintANSWER: True

EXPLANATION: The Team works together in

the Sprint Planning Meeting to decide how

much to target in the Sprint, and that target is

shared among the members of the Team.


32/39

QUESTION: The ScrumMaster is responsiblefor assigning tasks to the TeamANSWER: FalseEXPLANATION: The Team is responsible forself-organizing, and this includes together

deciding who should work on which tasks

during the Sprint


33/39

QUESTION: The Product Backlog is an ordered

list of features, functionality, and other workthat needs to be completed in the futureANSWER: TrueEXPLANATION: The Product Backlog is anordered list of features, functionality, and other

work that needs to be completed in the future,

to maximize ROI


34/39

QUESTION: The ScrumMaster is responsible

for making sure everyone knows and followsthe practices of ScrumANSWER: TrueEXPLANATION: One of the first things aScrumMaster will do is teach Scrum to the

Team, Product Owner, and stakeholders.

Everyone needs to understand the principlesand practices of Scrum, for it to be successful.


35/39

QUESTION: The ScrumMaster is responsible

for managing the Team to hit its target at theend of the SprintANSWER: FalseEXPLANATION: The ScrumMaster does notmanage the Team the Team is responsible for

self-organizing during the Sprint. If they fail to

do this effectively, it will be visible, and theScrumMaster should help them learn how.


36/39

QUESTION: The ScrumMaster is responsiblefor protecting the Team from outside

distractions, disruption, or interferenceANSWER: TrueEXPLANATION: The ScrumMaster is

responsible for serving as a bodyguard for the

Team, protecting them from outside

distractions, disruption, or interference


37/39

QUESTION: The Sprint Backlog tracks howlong each Team member has spent so far on

each taskANSWER: FalseEXPLANATION: The Sprint Backlog tracks how

much work remains for each task being worked

on or planned for in the Sprint.


38/39

QUESTION: The Sprint Planning Meeting istimeboxed to 8 hours for a 1 month Sprint, and

4 hours for a 2 week SprintANSWER: TrueEXPLANATION: The Sprint Planning Meeting is

timeboxed to these lengths to ensure that

planning is completed in a reasonable amount of

time, and to help the Team learn to do this.


39/39

QUESTION: The Sprint Retrospective is only

required if the Team is having difficulties;otherwise, it is optionalANSWER: FalseEXPLANATION: No Sprint is perfect, and aSprint Retrospective is mandatory for every

Sprint, to enable the Team, Product Owner, and

ScrumMaster to identify improvements to ourway of working in future Sprints.

game of scrum

Documents