Scrum Master
What are Product Backlog features? Select three. It is never complete It is dynamic As long as a product exists, its Product Backlog also exists A Product Backlog could be closed when it contains no items to include into the next Sprint When the final version of a product is rolled out, its Product Backlog is dismissed
A Product Backlog is never complete. The earliest development of it only lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. As long as a product exists, its Product Backlog also exists.
How much time does the Sprint Planning take? Not more than 8 hours From 4 to 8 hours As much as it is necessary to make task break-down and estimations for all items in the Sprint Backlog Not more than 4 hours
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
What are the three main qualities the team model in Scrum is designed to optimize? Flexibility Productivity Creativity Agility Responsibility Competence
The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Imagine you are a Scrum Master. There are 10 professionals (developers and QAs) and the Product Owner. How to distribute people between development teams? Choose all applicable variants: 2 teams of 6 and 4 people (the professionals after a short meeting decided this is the best variant) 1 team of 10 people (because there is no reason to divide) 3 teams of 4, 3 and 3 people (each team is cross-functional) 2 teams of 6 and 4 people (because it is good to have all the QAs in a separate team)
Number of people in a Development Team should be between 3 and 9. Each team should be cross-functional and self-organized. Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
it is normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release. True or False?
False It is not normal. Development Teams deliver an Increment of product functionality every Sprint. This Increment is usable, so a Product Owner may choose to immediately release it. So, there is nothing to prepare. Each increment contains only "Done" functionality that could be released immediately.
The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team. True or False?
False. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren't. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.
If an inspector determines that one or more aspects of a process deviate outside acceptable limits when an adjustment must be made? The deviations should be discussed at the Daily Scrum and then an adjustment must be made As soon as possible to minimize further deviation After clarifying all the details with the Product Owner After Scrum Master approval
If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.
What are the Scrum Artifacts? Select all applicable items. Sprint Backlog Product Backlog The Sprint Goal Increment The list of removed impediments
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.
What comprises Scrum? Reports Roles Burn-down charts Events Rules Scrum Teams Artifacts
The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum's success and usage.
Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice. True or False?
True. The Development Team may also invite other people to attend in order to provide technical or domain advice.
Could the Sprint Planning be finished if only work planned for the first days of the Sprint is decomposed to units of one day or less? No, all items in the Sprint Backlog should be decomposed to units of one day or less by the end of the Sprint Planning Yes, if the remaining work is also estimated, maybe in bigger units
Yes, if the remaining work is also estimated, maybe in bigger units
Who is responsible for crafting the Sprint Goal? The Product Owner The Scrum Master The Scrum Team The Development Team The Key Stakeholders
After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.
How does Definition of "Done" help to the Scrum Team? Select three most applicable items. Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning DoD ensures artifact transparency DoD helps to calculate velocity of the Scrum Team DoD helps in inspection and adaptation DoD is used to assess when work is complete on the product Increment
DoD is used to assess when work is complete on the product Increment Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning DoD ensures artifact transparency
Who participates in the Sprint Review? Select all applicable variants. The Development Team The Scrum Master The Product Owner The Organization CEO The Key Stakeholders
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value.
Who is allowed to make changes in the Product Backlog? The Product Owner The Development Team, but with permission of the Product Owner The Key Stakehodlers Anyone
The Product Owner is the sole person responsible for the Product Backlog. However, he or she can delegate some work related to product backlog management to the Development Team.
Who is responsible for the monitoring of the remaining work towards the Project Goal? The Product Owner The Scrum Master and The Development Team The Product Owner and The Development Team The Scrum Master The Development Team The Scrum Team
The Product Owner tracks total work remaining at least every Sprint Review. The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal. This information is made transparent to all stakeholders.
Who is allowed to participate in the Daily Scrum? The Development Team The Scrum Master The Key Stakeholders The Product Owner
The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum. Other people could attend the meeting, but cannot participate.
How does the Scum Master help to the Product Owner? Select three most appropriate answers. Facilitating Scrum events as requested or needed Understanding product planning in an empirical environment Finding techniques for effective Product Backlog management Introducing cutting edge development practices Leading and coaching the organization in its Scrum adoption
The Scrum Master serves the Product Owner in several ways, including: Finding techniques for effective Product Backlog management; Helping the Scrum Team understand the need for clear and concise Product Backlog items; Understanding product planning in an empirical environment; Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; Understanding and practicing agility; and, Facilitating Scrum events as requested or needed.
