Practice Free PSM I Exam Online Questions
When multiple Scrum Teams are working on a single product, what best describes the Definition of Done? Choose the best answer.
- A . When multiple Scrum Teams are working together on a product, they must mutually define and comply with the same Definition of Done.
- B . Each Scrum Team defines and uses its own. The differences are discussed and reconciled during a hardening Sprint.
- C . Each Scrum Team uses its own, but must make their definition clear to all other teams so the differences are known.
- D . The Scrum Masters from each Scrum Team define a common Definition of Done.
A
Explanation:
The correct answer is A. When multiple Scrum Teams work on the same product, they should share a common Definition of Done. This creates transparency across the product and ensures that all Increments are held to the same quality standard. Without one shared Definition of Done, it becomes difficult to inspect the integrated product accurately and determine whether work is truly complete.
Option B is incorrect because Scrum does not recommend separate Definitions of Done later reconciled in a hardening Sprint. Hardening Sprints are not part of Scrum and usually indicate that quality has not been built into normal development.
Option C is also incorrect because merely making different definitions visible does not solve the inconsistency problem. A product needs one integrated standard of completion.
Option D is incorrect because Scrum Masters do not define the Definition of Done on behalf of the teams. It must be mutually understood and used by the Scrum Teams working on that product, taking organizational standards into account.
A shared Definition of Done supports integration, quality, and releasability. It helps all teams contribute to one coherent product Increment rather than producing partially compatible outputs with differing completion standards.
Which two ways of creating Scrum Teams are consistent with Scrum’s values? (choose the best two answers)
- A . Bring all the people together and let them organize into Scrum Teams
- B . Managers personally re-assign current subordinates to new teams.
- C . Existing teams propose how they would like to go about organizing into the new structure.
- D . Managers collaborate to assign individuals to specific teams.
- E . The Chief Product Owner determines the new team structures and assignments.
AC
Explanation:
The best two answers are A and C. These two ways of creating Scrum Teams are consistent with Scrum’s values because they respect the self-organization and empowerment of the people who will be working in the teams. They also foster openness and courage by allowing the people to express their preferences and opinions about the new structure.
B, D and E are not consistent with Scrum’s values because they impose a top-down approach that does not involve the people who will be affected by the change. They also undermine the commitment and focus of the teams by assigning them to work on something they may not be interested in or passionate about.
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.
AD
Explanation:
Explanation of Correct Answer
According to the Scrum Guide1, the only required events in Scrum are Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. These events enable transparency, inspection, and adaptation. The other options are not mandatory in Scrum, although they may be useful in some contexts.
Reference: Scrum Guide
When does a Sprint conclude? (choose the best answer)
- A . When the Product Owner decides enough has been delivered to meet the Sprint Goal.
- B . When the Sprint Retrospective is complete.
- C . When all the tasks are completed by the Developers.
- D . When all Product Backlog items meet their Definition of Done.
B
Explanation:
According to the Scrum Guide, a Sprint concludes when the Sprint Retrospective is complete. This is the last event of the Sprint cycle, where the Scrum Team inspects itself and creates a plan for improvements. The other options are not valid indicators of the conclusion of a Sprint, as they are either irrelevant (such as the Product Owner deciding enough has been delivered) or incomplete (such as all tasks or Product Backlog items being done).
The Product Owner is not collaborating with the Development Team during the Sprint.
What are two valuable actions for a Scrum Master to take? (Choose two.)
- A . Inform the Product Owner’s functional manager.
- B . Stop the Sprint, send the Product Owner to a course and restart.
- C . Bring up the problem in the Sprint Retrospective.
- D . Coach the Product Owner in the values of Scrum and incremental delivery.
- E . Nominate a proxy Product Owner.
C,D
Explanation:
According to the Scrum Guide1, collaboration between the Product Owner and Developers is essential for creating valuable products. The Product Owner is accountable for maximizing value resulting from work by Developers. Developers are accountable for creating a plan for the Sprint, which includes selecting items from Product Backlog that they can complete within a Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Therefore, two valuable actions for a Scrum Master to take if the Product Owner is not collaborating with the Development Team during the Sprint are:
Bring up the problem in the Sprint Retrospective, where the Scrum Team can inspect how they worked together and create a plan for improvements.
Coach the Product Owner in the values of Scrum and incremental delivery, and help them understand their role and responsibilities in collaborating with Developers.
The other options are not valuable actions, as they may undermine trust, respect, and self-organization within the Scrum Team.
Reference: Scrum Guide
What two techniques could the Scrum Master use when the Scrum Team gets caught in an internal disagreement about which development techniques to apply? (Choose two.)
- A . Involve the complete Development Team.
- B . Use coaching techniques; such as open questions and active listening.
- C . Ask an external technical specialist to make the decision.
- D . Send every team member to the company’s HR department to express their concerns.
A,B
Explanation:
According to the Scrum Guide1, the Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. No one tells them how to do their work. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Therefore, when the Scrum Team gets caught in an internal disagreement about which development techniques to apply, two techniques that the Scrum Master could use are:
Involve the complete Development Team, as they are responsible for managing and refining their own work.
Use coaching techniques, such as open questions and active listening, to help the Development Team resolve their conflict and reach a consensus.
The other options are not appropriate, as they may undermine the self-organization and empowerment of the Developers.
Reference: Scrum Guide
Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).
- A . True
- B . False
B
Explanation:
According to the Scrum Guide1, the Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. 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. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Reference: Scrum Guide
True or False: The purpose of a Sprint Is lo produce a valuable useful Inclement.
- A . True
- B . False
A
Explanation:
According to the Scrum Guide, the purpose of a Sprint is to produce a valuable useful Increment that meets the Definition of Done and the Sprint Goal. This means that the Developers work on items from the Product Backlog that deliver value to the stakeholders and align with the product vision. The other option is not valid, as it implies that producing an Increment is not the purpose of a Sprint.
When must a scrum Team release each increment? (choose the best answer)
- A . when the Scrum Team finishes their work
- B . Alter every Sprint. without exception
- C . Whenever the product s tree of detects
- D . When it makes sense to release It.
D
Explanation:
According to the Scrum Guide, a Scrum Team must release each Increment when it makes sense to do so, based on the value and feedback obtained from stakeholders. The decision to release an Increment is made by the Product Owner, who is responsible for maximizing the value of the product and the work of the Development Team. The other options are not valid, as they imply that releasing an Increment is either mandatory (such as after every Sprint), conditional (such as when the product is free of defects), or irrelevant (such as when the Scrum Team finishes their work).
The Product Backlog is ordered by:
- A . The Product Owner with the most valuable items placed at the top.
- B . Risk, where safer items are at the top, and riskier items are at the bottom.
- C . Items are randomly arranged.
- D . Size, where small items ale at the top and large items are at the bottom.
A
Explanation:
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.”
