Practice Free PSM I Exam Online Questions
Why is the Daily Scrum held at the same time and same place?
- A . The consistency reduces complexity.
- B . The place can be named.
- C . The Product Owner demands it.
- D . Rooms are hard to book and this lets it be booked in advance.
A
Explanation:
According to the Scrum Guide, the Daily Scrum is held at the same time and same place to reduce complexity and promote consistency. The other options are not valid reasons for holding the Daily Scrum at the same time and same place, as they are either irrelevant (such as naming the place) or incorrect (such as being demanded by the Product Owner or booking rooms in advance).
What is the recommended size for a Scrum Team? (Choose the best answer.)
- A . At least 7.
- B . 9
- C . 10 or fewer.
- D . 7 plus or minus 3.
C
Explanation:
The recommended size for a Scrum Team is 10 or fewer people, as stated in the Scrum Guide: “The recommended size of a Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.”
What is the role of management in Scrum?
- A . To facilitate the Scrum Teams with insights and resources that help them improve.
- B . To monitor the Development Team’s productivity.
- C . To identify and remove people that aren’t working hard enough.
- D . To continually monitor staffing levels of the Development Team.
A
Explanation:
The correct answer is A, because the role of management in Scrum is to facilitate the Scrum Teams with insights and resources that help them improve. The Scrum Guide states that “the organization respects their self-organization by not telling them how they should do their work.” Therefore, management should support the Scrum Teams by providing them with an environment that fosters collaboration, learning, and innovation.
Who determines how work is performed during the Sprint?
- A . Architects.
- B . The Development Team.
- C . The Scrum Master.
- D . Subject matter experts.
- E . Development Team managers.
B
Explanation:
The correct answer is B, because the Development Team determines how work is performed during the Sprint. The Scrum Guide states that “development Teams are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.” Therefore, the Development Team has the autonomy and responsibility to organize and manage its own work.
What enhances the transparency of an increment?
- A . Doing all work needed to meet the definition of “Done”
- B . Reporting Sprint progress to the stakeholders daily
- C . Keeping track of and estimating all undone work to be completed in a separate Sprint.
- D . Updating Sprint tasks properly in the electronic tracking tool.
A
Explanation:
he correct answer is A, because doing all work needed to meet the definition of “Done” enhances the transparency of an increment. The Scrum Guide states that “when a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means.” Therefore, by meeting the definition of “Done”, an increment becomes transparent to all stakeholders and ready for release.
When does a Developer become accountable for an item in the sprint Backlog? (choose the best answer)
- A . During the Daily Scrum
- B . Never am Developers on the Scrum Team share accountability tor items in the
- C . As soon as a Developer on the Scrum Team can accommodate more work
- D . At Sprint Planning when all of the Sprint Backlog items are split evenly across the Developers
B
Explanation:
A Developer becomes accountable for an item in the Sprint Backlog never as Developers on the Scrum Team share accountability for items in the Sprint Backlog, as stated in the Scrum Guide: “The Developers can select whatever items they want as long as they feel they can complete the work by the end of the Sprint. The Scrum Team is responsible for all estimates. The Product Owner may influence the Developers by helping them understand and select trade-offs, but the people who will perform the work make the final estimate.”
A new Developer is having continuing conflicts with existing members or the scrum Team, which is impacting the delivery of the Increment It necessary, who is responsible for removing the Developer from the Scrum Team? (choose the best answer)
- A . The Scrum Master is responsible, they remove impediments
- B . The Product Owner is responsible, they control the return on investment (ROI)
- C . The hiring manager is responsible, they hired the Developer
- D . The Scrum Team is responsible
D
Explanation:
According to the Scrum Guide, the Scrum Team is responsible for removing a Developer from the Scrum Team if necessary, as they are self-managing and accountable for creating valuable Increments. The other options are not valid, as they imply that someone else outside the Scrum Team has the authority to remove a Developer (such as the Scrum Master, the Product Owner, or the hiring manager), which is not consistent with Scrum values and principles.
What is the time-box for the Sprint Review?
- A . As long as needed.
- B . 2 hours for a monthly Sprint.
- C . 4 hours for a monthly Sprint.
- D . 4 hours and longer as needed.
- E . 1 day
C
Explanation:
According to the Scrum Guide1, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-box for the Sprint Review is four hours for a one-month Sprint.
Reference: Scrum Guide
Which two of the following are appropriate topics for discussion during a Sprint Retrospective? (Choose two.)
- A . Identifying high priority process improvements for the next Sprint.
- B . The order of items in the Product Backlog.
- C . How the team collaborates.
- D . Documenting acceptance criteria for items in the next Sprint.
A, C
Explanation:
According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
Therefore, two appropriate topics for discussion during a Sprint Retrospective are:
Identifying high priority process improvements for the next Sprint.
How the team collaborates.
The other options are not relevant or appropriate for the Sprint Retrospective.
Reference: Scrum Guide
When Goes a Developer become accountable for the value 01 a Product BacKlog item selected for
the Sprint’ (choose the best answer)
- A . Never The entire Scrum Team is accountable for creating value every Sprint.
- B . At the Sprint Planning Evented
- C . Whenever a team member can accommodate more worn.
- D . During the Daily scrum
B
Explanation:
According to the Scrum Guide, a Developer becomes accountable for the value of a Product Backlog item selected for the Sprint at the Sprint Planning event. This is when the Developers select items from the Product Backlog that they can commit to complete within a Sprint. The Developers are then responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they either imply that Developers are not accountable for value (such as never or whenever), or that they become accountable at a different time (such as during the Daily Scrum).
