Free Professional Scrum Master I Practice Questions

According to the Scrum Guide 1 , the Sprint Planning meeting has a time-box of eight hours or less for a one-month Sprint. The Scrum Master ensures that the meeting is time-boxed and keeps the Scrum Team focused on the objective. If the Development Team cannot forecast how many Product Backlog items it can complete, it should still start the Sprint and work on the most likely items to meet the Sprint Goal. The Sprint Backlog can be updated throughout the Sprint as more is learned. The Scrum Master should also support the team to discuss the reasons for the lack of clarity in the Product Backlog items and how to prevent it from happening again in the next Sprint Retrospective.

According to the Scrum Guide 1 , collaboration between the Product Owner and Developers is essential for creating valuable products. The Product Owner is accountable for maximizing value resulting from work by Developers. Developers are accountable for creating a plan for the Sprint, which includes selecting items from Product Backlog that they can complete within a Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Therefore, two valuable actions for a Scrum Master to take if the Product Owner is not collaborating with the Development Team during the Sprint are:

Bring up the problem in the Sprint Retrospective, where the Scrum Team can inspect how they worked together and create a plan for improvements.

Coach the Product Owner in the values of Scrum and incremental delivery, and help them understand their role and responsibilities in collaborating with Developers.

The other options are not valuable actions, as they may undermine trust, respect, and self-organization within the Scrum Team.

According to the Scrum Guide, two intended outcomes of the Daily Scrum are identification of impediments that may prevent the Developers from achieving the Sprint Goal and a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint Goal. These outcomes help the Developers to inspect their progress, plan their work, and collaborate effectively. The other options are not intended outcomes of the Daily Scrum, as they are either irrelevant (such as updating a Scrum board) or inappropriate (such as providing a status report or an update of completed tasks).

The correct answers are D and E, because these are two activities that a Product Owner can engage in during a Sprint. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Therefore, the Product Owner can answer questions from the Development Team about items in the current Sprint, and work with the stakeholders to understand their needs and expectations.

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.