ExamGecko
Home Home / Scrum / PSM I

Scrum PSM I Practice Test - Questions Answers

Question list
Search
Search

Related questions











When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?

A.
Yes, but only for Scrum Teams whose work has dependencies.
A.
Yes, but only for Scrum Teams whose work has dependencies.
Answers
B.
Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
B.
Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done.
Answers
C.
No, each Scrum Team stands alone.
C.
No, each Scrum Team stands alone.
Answers
D.
No, that is far too hard and must be done in a hardening Sprint.
D.
No, that is far too hard and must be done in a hardening Sprint.
Answers
Suggested answer: B

When can a Development Team cancel a Sprint?

A.
It can't. Only Product Owners can cancel Sprints.
A.
It can't. Only Product Owners can cancel Sprints.
Answers
B.
When functional expectations are not well understood.
B.
When functional expectations are not well understood.
Answers
C.
When the Product Owner is absent too often.
C.
When the Product Owner is absent too often.
Answers
D.
When the selected Product Backlog items for the Sprint become unachievable.
D.
When the selected Product Backlog items for the Sprint become unachievable.
Answers
E.
When a technical dependency cannot be resolved.
E.
When a technical dependency cannot be resolved.
Answers
Suggested answer: A

Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?

A.
The Sprint Backlog.
A.
The Sprint Backlog.
Answers
B.
The Sprint Goal
B.
The Sprint Goal
Answers
C.
The release plan.
C.
The release plan.
Answers
D.
Sprint Review minutes.
D.
Sprint Review minutes.
Answers
Suggested answer: B

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

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

When is a Sprint over?

A.
When the Product Owner says it is done.
A.
When the Product Owner says it is done.
Answers
B.
When all Product Backlog items meet their definition of "Done".
B.
When all Product Backlog items meet their definition of "Done".
Answers
C.
When all the tasks are completed.
C.
When all the tasks are completed.
Answers
D.
When the time-box expires.
D.
When the time-box expires.
Answers
Suggested answer: D

Scrum has a role called "Project Manager".

A.
True
A.
True
Answers
B.
False
B.
False
Answers
Suggested answer: B

What 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.
A.
Put them on a separate list on the Scrum board, available for all to see.
Answers
B.
Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
B.
Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
Answers
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.
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.
Answers
D.
Add them to the definition of "Done" so the work is taken care of every Sprint.
D.
Add them to the definition of "Done" so the work is taken care of every Sprint.
Answers
Suggested answer: B, D

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

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.
A.
Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
Answers
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 analyze,decompose, and create additional functionality during the 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 analyze,decompose, and create additional functionality during the Sprint.
Answers
C.
Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the DevelopmentTeam to make a complete forecast. Then start the Sprint.
C.
Continue the Sprint Planning meeting past its time-box until an adequate number of Product Backlog items are well enough understood for the DevelopmentTeam to make a complete forecast. Then start the Sprint.
Answers
D.
Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
D.
Discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur.
Answers
E.
Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.
E.
Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.
Answers
Suggested answer: B, D

Which answer best describes the topics covered in Sprint Planning?

A.
What to do and who will do it.
A.
What to do and who will do it.
Answers
B.
How conditions have changed and how the Product Backlog should evolve.
B.
How conditions have changed and how the Product Backlog should evolve.
Answers
C.
What can be done and how to do it.
C.
What can be done and how to do it.
Answers
D.
What went wrong in the last Sprint and what to do differently this Sprint.
D.
What went wrong in the last Sprint and what to do differently this Sprint.
Answers
E.
Who is on the team and what team member roles will be.
E.
Who is on the team and what team member roles will be.
Answers
Suggested answer: C
Total 250 questions
Go to page: of 25