Scrum Professional Scrum Master PSM-I New Questions

The correct answers are B and D. The Scrum Master is accountable for the Scrum Team’s effectiveness and helps the team improve its practices within the Scrum framework. One important way this happens is by facilitating Scrum Team decisions. That makes Option B correct. The Scrum Master does not make decisions for the team, but helps create the conditions for effective collaboration, self-management, and sound decision-making. This support improves the team’s ability to inspect, adapt, and work productively.

Option D is also correct because the Scrum Master serves the Scrum Team by causing the removal of impediments to the Scrum Team’s progress. Impediments reduce flow, create delays, and lower effectiveness. By helping remove those obstacles, the Scrum Master enables the team to focus on creating valuable Increments.

Option A is incorrect because ordering the Product Backlog is the Product Owner’s accountability, not the Scrum Master’s. Option C is too narrow. While the Scrum Master helps ensure Scrum events are positive, productive, and within the timebox, simply starting and ending meetings on time is not one of the two primary ways they help maximize team productivity. Their deeper contribution is enabling effectiveness and removing barriers.

The correct answer is B, because the time-box for the Sprint Planning meeting is 8 hours for a monthly Sprint. The Scrum Guide states that “Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.”

According to the Scrum Guide, the Product Owner has the final say on the order of the Product Backlog, as he or she is responsible for maximizing the value of the product and the work of the Development Team. The other roles do not have this authority, although they may provide input and suggestions to the Product Owner.

According to the Scrum Guide, 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 Sprint. The topics that are appropriate for discussion are those that relate to how the team does its work, such as team relations, Definition of Done, and processes, tools, communication, collaboration, quality, etc. The other options are not appropriate topics for discussion in a Sprint Retrospective, as they belong to other Scrum events (such as arranging the Sprint Backlog for the next Sprint in the Sprint Planning or evaluating the value of work in the Product Backlog in the Sprint Review).