PSM-I Free Practice Test

What does n mean tor a scrum Team to be cross-function at? (choose the best answer)

1. A. The Scrum Team includes skilled individuals who together have all the skins necessary to create value each sprint
2. B. Developers on the Scrum Team work closely with business analysis architects developers, and testers who are not on the team
3. C. The Scrum Team includes not only developers but also business analysts, architects, and testers
4. D. The Scrum Team is a virtual team drawing from separate teams of business analysts, architects, developers, and testers

Correct Answer: A
According to the Scrum Guide, a Scrum Team is cross-functional if it includes skilled individuals who together have all the skills necessary to create value each Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of cross-functionality, as they either imply that the Developers work in silos or rely on external people (such as business analysts, architects, testers, or separate teams).

When might a Sprint be abnormally cancelled?

1. A. When the Development Team feels that the work is too hard.
2. B. When the Sprint Goal becomes obsolete.
3. C. When the sales department has an important new opportunity.
4. D. When it becomes clear that not everything will be finished by the end of the Sprint.

Correct Answer: B
According to the Scrum Guide1, a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
References: Scrum Guide

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

1. A. Monthly.
2. B. 8 hours for a one-month Sprint
3. C. Whenever ills done
4. D. 4 hours for a one-month Sprint

Correct Answer: B
According to the Scrum Guide, the timebox for a Sprint Planning event is 8 hours for a one-month Sprint, proportionally shorter for shorter Sprints. The other options are not valid, as they are either too long (such as monthly), too vague (such as whenever it’s done), or too short (such as 4 hours for a one-month Sprint).

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

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

Correct Answer: D
The correct answer is D, because there is no gap between Sprints in Scrum. The Scrum Guide states that “a new Sprint starts immediately after the conclusion of the previous Sprint.” Therefore, there is no time required after a Sprint to prepare for the next Sprint.

The Product Backlog is ordered by:

1. A. The Product Owner with the most valuable items placed at the top.
2. B. Risk, where safer items are at the top, and riskier items are at the bottom.
3. C. Items are randomly arranged.
4. D. Size, where small items ale at the top and large items are at the bottom.

Correct Answer: A
The Product Backlog is ordered by the Product Owner with the most valuable items placed at the top, as stated in [6]: “The Product Owner is responsible for ordering items on their product backlog based on their value to customers and users. Value can be measured by various factors, such as business value, customer satisfaction, risk reduction, learning opportunities, etc. The most valuable items are placed at the top of the product backlog so that they can be delivered sooner by the development team.”