Scrum Updated PSM-I Exam Questions and Answers by edwin

The correct answers are B and C because security is part of product quality and should be addressed within the Scrum Team’s ongoing work, not delegated away or deferred to a later phase. Option B is correct because security concerns can and should be made visible in the Product Backlog when there is specific work needed to address them. This ensures transparency and allows the team to inspect, prioritize, and act on those concerns as part of product development.

Option C is also correct because if security is necessary for an Increment to be complete and releasable, it belongs in the Definition of Done. This ensures that security expectations are consistently applied every Sprint rather than treated as optional or postponed.

Option A is incorrect because Scrum does not rely on handing responsibility to a separate department. Option D is incorrect because delaying security work undermines transparency and increases risk. Option E is incorrect because security should not be isolated into one future Sprint as a separate cleanup effort. Scrum promotes integrating quality, including security, continuously into development so each Increment is usable and meets appropriate standards.

There are no activities that a Product Owner would typically undertake in the phase between the end of the current Sprint and the start of the next Sprint, because there is no such phase. The next Sprint starts immediately after the current Sprint, without any gaps or breaks. The other options are either activities that occur during a Sprint (such as refining the Product Backlog) or activities that are not consistent with Scrum (such as working with Quality Assurance departments or updating project plans).

A Product Owner releases each Increment when it makes sense, as stated in [2]: “The Product Owner decides when to release an Increment. This can be done at any time during or after a Sprint. The Product Owner may choose to release an Increment when it delivers enough value to customers or users, when it meets a market opportunity, when it reduces risk or uncertainty, or when it aligns with other business goals.”

A Product Backlog item is considered complete when it meets the Definition of Done, as stated in [5]: “When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.”