PSM 1 - 57 questions

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

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

When can a Development Team cancel a Sprint?

• It can't. Only Product Owners can cancel Sprints.
• When functional expectations are not well understood.
• When the Product Owner is absent too often.
• When the selected Product Backlog items for the Sprint become unachievable.
• When a technical dependency cannot be resolved.

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

• The Sprint Backlog.
• The Sprint Goal
• The release plan.
• Sprint Review minutes.

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

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

When is a Sprint over?

• When the Product Owner says it is done.
• When all Product Backlog items meet their definition of ג€Doneג€.
• When all the tasks are completed.
• When the time-box expires.

True or False: Scrum has a role called `Project Manager`.

• True
• False

What are two effective ways for the Scrum Team to make non-functional requirements visible? (Choose two.)

• Put them on a separate list on the Scrum board, available for all to see.
• Add them to the Product Backlog to ensure transparency.
• 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.
• Add them to the definition of ג€Doneג€ so the work is taken care of every Sprint.

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

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

During Sprint Planning the Product Owner and the Developers are unable to reach an understanding about the highest order Product Backlog items. Because of this, the Developers are unable to determine how many Product Backlog items they can forecast for the upcoming Sprint. However, the Product Owner and theDevelopers are able to agree on a Sprint Goal.Which of the following actions should the Scrum Master support? (Choose two.)

• Cancel the Sprint. Send the entire team to an advanced Scrum training and then start a new Sprint.
• Forecast the Product Backlog items that are most likely to meet the Sprint Goal and create the Sprint Backlog. Conclude Sprint Planning and start the development work. Continue to analyze, decompose, and create additional functionality during the Sprint.
• Continue the Sprint Planning event past its timebox until an adequate number of Product Backlog items are well enough understood for the Developers to make a complete forecast. Then start the Sprint.
• During the next Sprint Retrospective discuss why this happened and what changes will make it less likely to recur.
• Ask everyone to take as much time as needed to analyze the Product Backlog first, and then reconvene another Sprint Planning meeting.

Who can cancel a Sprint?

• The Scrum Team.
• The Scrum Master.
• The Product Owner.
• The Stakeholders.