PSM-I Exam Dumps : Professional Scrum Master I

The correct answer is D because every Sprint, including the first Sprint, should result in at least one valuable and useful Increment. Scrum is based on empiricism and incremental delivery. That means the team should not spend the first Sprint only on planning, documenting, or designing future work. Instead, they should create something usable that moves the product forward and provides an opportunity for inspection and adaptation.

Option A is incorrect because Scrum does not require detailed upfront analysis and documentation for later Sprints before producing value. Option B is incorrect because while some architecture and feature thinking may happen, Scrum does not make large upfront design the objective of the first Sprint. Option C is incorrect because Scrum avoids trying to fully plan the whole project in advance in complex environments. Instead, planning evolves over time as the team learns.

The key Scrum expectation is that each Sprint produces an Increment that meets the Definition of Done. This allows stakeholders to inspect real progress, provides early feedback, and reduces risk. The first Sprint is not an exception. It should deliver something useful, even if small, to begin empirical product development immediately.

The correct answer is D, because the recommended size for a Development Team is 3 to 9 members. The Scrum Guide states that “fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful.”

The best answers are B and C because the Scrum Master serves both the Product Owner and the Scrum Team by helping address quality concerns in a constructive, transparent, and Scrum-consistent way. Quality in Scrum is not handled outside the team or delegated only to testers. When a stakeholder raises a concern about low quality, the issue should be made visible and addressed through the Product Backlog, the Definition of Done, and direct collaboration within the Scrum Team.

Option B is correct because quality expectations and stakeholder concerns should be reflected in Product Backlog items when appropriate, and the Developers need to understand those concerns clearly. Option C is also correct because the Scrum Master helps the Product Owner find an effective way to work with the Developers and address the issue empirically.

Option A is incorrect because acceptable quality standards are not solely for Developers to decide in isolation. Option D is incorrect because Scrum does not create a separate tester role responsible for quality. Option E is too passive and delayed. A significant quality concern should be addressed promptly, not simply postponed to the Sprint Retrospective.