Last Attempt PSM-I Questions

The correct answers are B and C, because these are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity. The Scrum Guide states that “the Scrum Master serves the Development Team in several ways, including … removing impediments to the Development Team’s progress; facilitating Scrum events as requested or needed; and coaching the Development Team in self-organization and cross-functionality.” Therefore, by removing impediments and facilitating decisions, the Scrum Master helps the Development Team focus on their work and deliver value.

The Scrum Master should ask the person to share the issue with the team as soon as possible, as stated in [5]: “The Scrum Master should encourage transparency and collaboration within the team and with other stakeholders. If there is a concern about data security issues, it should be brought up to the team and discussed openly. The team can then decide how to handle it, whether by creating a Product Backlog item, updating the definition of “Done”, or taking some other action.”

When a Development Team determines that it will not be able to finish the complete forecast, both the Product Owner and the Development Team have to be present when reviewing and adjusting the Sprint work selected, as stated in [6]: “If there is not enough work remaining for all members of a Development Team then they can renegotiate scope with their Product Owner. If there is too much work remaining then they can also renegotiate scope with their Product Owner.”

According to the Scrum Guide1, 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, an Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Therefore, the best description of an increment of working software is additional features in a usable state that complement those delivered in previous iterations.

References: Scrum Guide