Practice Free PSM I Exam Online Questions
Question #41
Which two things should the Development Team do during the first Sprint? (Choose two.)
- A . Make up a plan for the rest of the project.
- B . Analyze, describe, and document the requirements for the subsequent Sprints.
- C . Develop at least one piece of functionality.
- D . Define the major product features and release plan architecture
- E . Create an increment of potentially releasable software.
Correct Answer: CE
CE
Explanation:
According to the Scrum Guide, the Development Team should do two things during the first Sprint: develop at least one piece of functionality and create an increment of potentially releasable software. These are the goals of every Sprint, regardless of its order. The other options are not things that the Development Team should do during the first Sprint, as they are either out of scope (such as making a plan for the rest of the project or defining major product features and release plan architecture) or unnecessary (such as analyzing, describing, and documenting requirements for subsequent Sprints).
CE
Explanation:
According to the Scrum Guide, the Development Team should do two things during the first Sprint: develop at least one piece of functionality and create an increment of potentially releasable software. These are the goals of every Sprint, regardless of its order. The other options are not things that the Development Team should do during the first Sprint, as they are either out of scope (such as making a plan for the rest of the project or defining major product features and release plan architecture) or unnecessary (such as analyzing, describing, and documenting requirements for subsequent Sprints).
Question #42
When is the Sprint Backlog created?
- A . At the beginning of the project.
- B . During the Sprint Planning meeting.
- C . Prior to the Sprint Planning meeting.
- D . During the Sprint.
Correct Answer: B
B
Explanation:
The correct answer is B, because the Sprint Backlog is created during the Sprint Planning meeting. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.”
B
Explanation:
The correct answer is B, because the Sprint Backlog is created during the Sprint Planning meeting. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.”
Question #43
How should a Scrum Team deal with non-functional requirements? (choose the best answer)
- A . Manage them during the Integration Sprint prior to the Release Sprint.
- B . Assign them to the lead developers on the team.
- C . Ensure every Increment meets them.
- D . Make sure the release department understands these requirements, but it is not the Scrum Team’s responsibility.
Correct Answer: C
C
Explanation:
The best answer is C. Ensure every Increment meets them. Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs1. NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release1. The Scrum Team should ensure that every Increment meets the NFRs, as they are part of the product requirements and affect the value delivery and customer satisfaction.
C
Explanation:
The best answer is C. Ensure every Increment meets them. Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs1. NFRs are persistent qualities and constraints typically revisited as part of the definition of done (DoD) for each Iteration, PI, or release1. The Scrum Team should ensure that every Increment meets the NFRs, as they are part of the product requirements and affect the value delivery and customer satisfaction.
Question #44
Which of the following are topics for the Developers to discuss at the Daily scrum as they inspect their progress toward the Sprint Goal? (choose the best three answers)
- A . what have we learned since yesterday, and now should we modify our plan to increase our ability to meet the Sprint Goal?
- B . Are mere any impediments Clocking progress toward the sprint Goal?
- C . What will I be working on tomorrow?
- D . Are mere any decisions that need to be made to maintain progress toward the sprint Goal?
- E . Why were you late?
- F . How many hours Old I spend on the project yesterday
- G . win todays work negatively impact our ability to meet the sprint Goal for the Split following this one?
Correct Answer: A, B, D
A, B, D
Explanation:
Three topics for the Developers to discuss at the Daily Scrum as they inspect their progress toward the Sprint Goal are:
What have we learned since yesterday, and how should we modify our plan to increase our ability to meet the Sprint Goal?
Are there any impediments blocking progress toward the Sprint Goal?
Are there any decisions that need to be made to maintain progress toward the Sprint Goal?
These topics are suggested by [6]: “The structure of the meeting is set by the Developers and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based.”
A, B, D
Explanation:
Three topics for the Developers to discuss at the Daily Scrum as they inspect their progress toward the Sprint Goal are:
What have we learned since yesterday, and how should we modify our plan to increase our ability to meet the Sprint Goal?
Are there any impediments blocking progress toward the Sprint Goal?
Are there any decisions that need to be made to maintain progress toward the Sprint Goal?
These topics are suggested by [6]: “The structure of the meeting is set by the Developers and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based.”
Question #45
A product Increment must be released to production at the end of each Sprint.
- A . True
- B . False
Correct Answer: B
B
Explanation:
The correct answer is B, because a product Increment does not have to be released to production at the end of each Sprint. The Scrum Guide states that “at the end of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’. An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.” Therefore, a product Increment must be potentially releasable, but the decision to release it is up to the Product Owner.
B
Explanation:
The correct answer is B, because a product Increment does not have to be released to production at the end of each Sprint. The Scrum Guide states that “at the end of a Sprint, the new Increment must be ‘Done,’ which means it must be in useable condition and meet the Scrum Team’s definition of ‘Done’. An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.” Therefore, a product Increment must be potentially releasable, but the decision to release it is up to the Product Owner.
Question #46
A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example, set up conference calls) before the Daily Scrum.
What action should the Scrum Master take?
- A . Allow the Development Team to self-manage and determine for itself what to do.
- B . Set up the meeting and tell the Development Team that is how it will be done.
- C . Ask the Development Team members to alternate who is responsible for meeting setup.
- D . Inform management and ask them to solve it.
Correct Answer: A
A
Explanation:
According to the Scrum Guide1, only people who are actively working on items in the Sprint Backlog participate in updating it during a Sprint; this includes tracking progress made on those items. This is typically done by Developers updating their remaining work every day after their Daily Scrum. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving their Sprint Goal. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, the Scrum Master should allow the Development Team to self-manage and determine for itself what to do regarding the logistical challenges of meeting in different locations.
Reference: Scrum Guide
A
Explanation:
According to the Scrum Guide1, only people who are actively working on items in the Sprint Backlog participate in updating it during a Sprint; this includes tracking progress made on those items. This is typically done by Developers updating their remaining work every day after their Daily Scrum. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving their Sprint Goal. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, the Scrum Master should allow the Development Team to self-manage and determine for itself what to do regarding the logistical challenges of meeting in different locations.
Reference: Scrum Guide
Question #47
What is the function or purpose of management in Scrum? (choose the best answer)
- A . To identify and remove people that are not working hard enough.
- B . To present the Scrum Teams with insights and resources that help them improve.
- C . To monitor the productivity of the Developers.
- D . To continually monitor staffing levels of the Scrum Team.
Correct Answer: B
B
Explanation:
The correct answer is
B. To present the Scrum Teams with insights and resources that help them improve. According to the Scrum Guide1, “The role of management in Scrum is to support the Product Owner with insights and information into high-value product and system capabilities.” Management also helps the Scrum Team by providing an environment that fosters agility, learning, and collaboration2. Management does not directly control or monitor the work of the Developers, nor does it interfere with the self-organization and autonomy of the Scrum Team3. Management’s function in Scrum is to enable and empower the Scrum Team to deliver value and continuously improve.
B
Explanation:
The correct answer is
B. To present the Scrum Teams with insights and resources that help them improve. According to the Scrum Guide1, “The role of management in Scrum is to support the Product Owner with insights and information into high-value product and system capabilities.” Management also helps the Scrum Team by providing an environment that fosters agility, learning, and collaboration2. Management does not directly control or monitor the work of the Developers, nor does it interfere with the self-organization and autonomy of the Scrum Team3. Management’s function in Scrum is to enable and empower the Scrum Team to deliver value and continuously improve.
Question #48
When is it most appropriate for a Scrum Team to change the Definition of Done? (choose the best answer)
- A . During Product Backlog refinement.
- B . During the Sprint Retrospective.
- C . During Sprint Planning.
- D . Prior to starting a new project.
Correct Answer: B
B
Explanation:
According to the Scrum Guide, the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product1. The Definition of Done is created by the Developers and it is used to assess when work is complete on the product Increment1.
The Scrum Guide also states that the Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and becomes more stringent as the Scrum Team matures1. Therefore, it is important for the Scrum Team to regularly inspect and adapt the Definition of Done to reflect their current situation and needs.
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint1. The Sprint Retrospective focuses on three questions: What went well in the Sprint? What could be improved? What will we commit to improve in the next Sprint?1 These questions can help the Scrum Team identify potential changes to the Definition of Done that would increase the quality and value of the product.
Option A is incorrect because Product Backlog refinement is not a formal Scrum event, but rather an ongoing activity that can happen at any time during the Sprint1. Product Backlog refinement is mainly concerned with adding detail, estimates, and order to Product Backlog items1. Changing the Definition of Done during Product Backlog refinement could cause confusion and inconsistency among the Developers and the Product Owner.
Option C is incorrect because Sprint Planning is a time-boxed event that initiates a Sprint by defining a Sprint Goal and selecting Product Backlog items that deliver one coherent function1. Sprint Planning is based on the current state of the Product Backlog and the latest Definition of Done1. Changing the Definition of Done during Sprint Planning could disrupt the flow of the event and affect the scope and feasibility of the Sprint.
Option D is incorrect because prior to starting a new project is not a specific time in Scrum. Scrum does not prescribe any phases or stages for a project, but rather an empirical approach that relies on frequent inspection and adaptation of both the product and the process1. Changing the Definition of Done before starting a new project could be premature and irrelevant, as the Scrum Team may not have enough information or experience to define what ‘Done’ means for their product.
Reference: 1: The Scrum Guide
B
Explanation:
According to the Scrum Guide, the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product1. The Definition of Done is created by the Developers and it is used to assess when work is complete on the product Increment1.
The Scrum Guide also states that the Definition of Done may vary significantly per Scrum Team, depending on the context. The Definition of Done evolves over time and becomes more stringent as the Scrum Team matures1. Therefore, it is important for the Scrum Team to regularly inspect and adapt the Definition of Done to reflect their current situation and needs.
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint1. The Sprint Retrospective focuses on three questions: What went well in the Sprint? What could be improved? What will we commit to improve in the next Sprint?1 These questions can help the Scrum Team identify potential changes to the Definition of Done that would increase the quality and value of the product.
Option A is incorrect because Product Backlog refinement is not a formal Scrum event, but rather an ongoing activity that can happen at any time during the Sprint1. Product Backlog refinement is mainly concerned with adding detail, estimates, and order to Product Backlog items1. Changing the Definition of Done during Product Backlog refinement could cause confusion and inconsistency among the Developers and the Product Owner.
Option C is incorrect because Sprint Planning is a time-boxed event that initiates a Sprint by defining a Sprint Goal and selecting Product Backlog items that deliver one coherent function1. Sprint Planning is based on the current state of the Product Backlog and the latest Definition of Done1. Changing the Definition of Done during Sprint Planning could disrupt the flow of the event and affect the scope and feasibility of the Sprint.
Option D is incorrect because prior to starting a new project is not a specific time in Scrum. Scrum does not prescribe any phases or stages for a project, but rather an empirical approach that relies on frequent inspection and adaptation of both the product and the process1. Changing the Definition of Done before starting a new project could be premature and irrelevant, as the Scrum Team may not have enough information or experience to define what ‘Done’ means for their product.
Reference: 1: The Scrum Guide
Question #49
(When might a Sprint be cancelled? Choose the best answer.)
- A . When the Sprint Goal becomes obsolete.
- B . When the sales department has an important new opportunity.
- C . When the Developers determine the product plan is infeasible.
- D . When it becomes clear that not everything will be finished by the end of the Sprint.
Correct Answer: A
A
Explanation:
A Sprint may be cancelled only if the Sprint Goal becomes obsolete. This makes Option A the correct answer. The Scrum Guide is very clear that only the Product Owner has the authority to cancel a Sprint, although that decision may be influenced by stakeholders, the Developers, or the Scrum Master. The reason for cancellation is not general disruption, poor forecasting, or the appearance of new work. It is specifically tied to the Sprint Goal no longer having value or relevance.
Option B is incorrect because a new business opportunity does not automatically justify cancelling a Sprint. Scrum is designed to handle change without disrupting the Sprint unless the Sprint Goal itself is no longer valid.
Option C is incorrect because feasibility concerns should be addressed through collaboration and adaptation, but they do not by themselves define the cancellation rule.
Option D is incorrect because not finishing all selected work is not a reason to cancel a Sprint. Scrum accepts uncertainty, and the team inspects and adapts. The Sprint Goal remains the key commitment, and as long as it is still relevant, the Sprint should continue.
A
Explanation:
A Sprint may be cancelled only if the Sprint Goal becomes obsolete. This makes Option A the correct answer. The Scrum Guide is very clear that only the Product Owner has the authority to cancel a Sprint, although that decision may be influenced by stakeholders, the Developers, or the Scrum Master. The reason for cancellation is not general disruption, poor forecasting, or the appearance of new work. It is specifically tied to the Sprint Goal no longer having value or relevance.
Option B is incorrect because a new business opportunity does not automatically justify cancelling a Sprint. Scrum is designed to handle change without disrupting the Sprint unless the Sprint Goal itself is no longer valid.
Option C is incorrect because feasibility concerns should be addressed through collaboration and adaptation, but they do not by themselves define the cancellation rule.
Option D is incorrect because not finishing all selected work is not a reason to cancel a Sprint. Scrum accepts uncertainty, and the team inspects and adapts. The Sprint Goal remains the key commitment, and as long as it is still relevant, the Sprint should continue.
Question #50
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.
- B . Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
- 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.
- D . Add them to the definition of “Done” so the work is taken care of every Sprint.
Correct Answer: B,D
B,D
Explanation:
The correct answers are B and D, because adding non-functional requirements to the Product Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of ‘Done’ ensures that they are met every Sprint and do not accumulate technical debt.
Reference: Suggested Reading for Professional Scrum Master™ I
B,D
Explanation:
The correct answers are B and D, because adding non-functional requirements to the Product Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of ‘Done’ ensures that they are met every Sprint and do not accumulate technical debt.
Reference: Suggested Reading for Professional Scrum Master™ I