Scrum Updated PSM-I Exam Questions and Answers by franky

The best answer is C. When multiple Scrum Teams are working on a single product, they must mutually define and comply with the same Definition of Done1. This ensures that the product has a consistent level of quality and that the Increments delivered by different teams can be integrated seamlessly. Having different Definitions of Done for each team can lead to confusion, rework, and technical debt. The Scrum Guide says that the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product2. Therefore, it is not something that can be decided by the Scrum Masters alone (B) or left to each team’s discretion (A and D).

The correct answers are A, B, and D, because these techniques would be most helpful in this situation. Consulting with the Development Team may help identify the root causes of the impediments and possible solutions. Prioritizing the list and working on them in order may help reduce the backlog and focus on the most important or urgent issues. Alerting management to the impediments and their impact may help escalate the problems and get support from the organization.

a burndown chart is a graphical representation of work left to do versus time. It is very useful for predicting when all of the work will be completed. It is often used in agile software development methodologies such as Scrum. However, burndown charts can be applied to any project containing measurable progress over time. A release burndown chart tracks progress across multiple Sprints towards a product release. It shows how much work remains in the Product Backlog at any given time during the release cycle. A trend line through a release burndown chart indicates when the work remaining will likely be completed if nothing changes on the Product Backlog or the Development Team.

According to the Scrum Guide1, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with domain, practices, and people involved. The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint. Therefore, two appropriate topics for discussion during a Sprint Retrospective are:

• Identifying high priority process improvements for the next Sprint.
• How the team collaborates.

The other options are not relevant or appropriate for the Sprint Retrospective.

References: Scrum Guide