Pass the Scrum Professional Scrum Master PSM-I Questions and answers with CertsForce

According to the Scrum Guide, management external to the Scrum Team is not involved in the Daily Scrum at all. The Daily Scrum is an internal event for the Development Team to inspect their progress toward the Sprint Goal and plan their work for the next 24 hours. The other options are not valid ways for management to be involved in the Daily Scrum, as they are either intrusive (such as giving an update or speaking on behalf of others) or unnecessary (such as being represented by the Product Owner or the Scrum Master).

The best answer is B. The need for the team to learn based on doing work and measuring results.

The Sprint length should be chosen based on the complexity and volatility of the product and the environment, as well as the team’s capability and Definition of Done. The Sprint length should enable the team to deliver a usable Increment of value that meets the feedback needs of the stakeholders and the business. The Sprint length should also allow the team to inspect and adapt their work processes and practices based on the outcomes of the Sprint.

The other options are not valid reasons for choosing the Sprint length. The organization’s mandate, team formation, and release schedule should not dictate the Sprint length, but rather be aligned with it. The Scrum Team should have the autonomy to choose the Sprint length that best suits their product and context.

You can learn more about how to choose the right Sprint length from these sources: How Long A Sprint Should Be?, How to Choose the Right Sprint Length in Scrum, What is a Sprint?, Determining the Sprint Length, and Sprint Length: What’s the Right Length?.

The correct answer is A, because keeping component teams while starting Scrum may cause less initial disruption than organizing into new teams. As they start using Scrum, they will discover what works best for them and how to potentially re-organize towards feature teams. However, component teams may face some challenges in delivering a working Increment of software that provides business value every Sprint, as they may depend on other teams or layers.

According to the Scrum Guide1, the Sprint Backlog is the property of the Developers and no one else can tell them which items they should work on. The Developers can select any item from the Product Backlog that they forecast they can complete within a Sprint. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, no one owns a Sprint Backlog item, but the entire Development Team is accountable for it.

References: Scrum Guide

The correct answer is B, because the Sprint Backlog is created during the Sprint Planning meeting. The Scrum Guide states that “the Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.”

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.

A cross-functional Development Team is one that includes cross-skilled individuals who are able to contribute to do what is necessary to deliver an increment of software, as stated in the Scrum Guide1: “Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.”

The correct answer is F, because all of the Scrum Values are affected by a lack of trust in the Scrum Team. Trust is essential for the Scrum Team to work effectively and deliver value. Without trust, the Scrum Team may lose focus, respect, openness, courage, and commitment.

According to the Scrum Guide, the Sprint Backlog may include any items that are a decomposition of the selected Product Backlog items, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is the Developers’ plan for the Sprint, and it contains all the work that they forecast they can do to achieve the Sprint Goal and create a “Done” Increment. The other options are not valid, as they are either too specific (such as user stories or tasks) or too vague (such as tests).

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.