PSM-I Exam Dumps : Professional Scrum Master I

An example of an Increment is a valuable, useful set of product features, as stated in [4]: “An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, each Increment must be usable.”

According to the Scrum Guide 1 , during each Daily Scrum, each Developer answers three questions:

What did I do yesterday that helped meet our Sprint Goal?

What will I do today to help meet our Sprint Goal?

Do I see any impediment that prevents me or our Development Team from meeting our Sprint Goal?

The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward achieving their Sprint Goal and producing a usable Increment. The Developers can start with any one person and proceed in any order.

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.