HH SCRUM Master
Category: Scrum Team 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:
* 3 teams of 4, 3 and 3 people (each team is cross-functional) * 2 teams of 6 and 4 people (the professionals after a short meeting decided this is the best variant) [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.]
Category: Scrum Events What happens when a Sprint is cancelled? Select three.
* Any completed and "Done" Product Backlog items are reviewed * If part of the work is potentially releasable, the Product Owner typically accepts it * All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog [When a Sprint is cancelled, ]
Category: Scrum Artifacts What are Product Backlog features? Select three.
* As long as a product exists, its Product Backlog also exists * It is dynamic * It is never complete [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.]
Category: Scrum Theory What should be taken into the account for the Definition of "Done"? Select two the most appropriate items.
* Definition of "Done" of other Scrum Teams working on the same Product * Conventions, standards and guidelines of the Organization [If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."]
Category: Scrum Artifacts How does Definition of "Done" help to the Scrum Team? Select three most applicable items.
* DoD is used to assess when work is complete on the product Increment 8 Guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning * DoD ensures artifact transparency
Category: Scrum Team 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 [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.]
Category: Scrum Team What are the two essential features a Scrum Team should possess?
* It should have all competencies needed to accomplish the work without depending on others not part of the team * It should choose how best to accomplish their work, rather than being directed by others outside the team [Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.]
Category: Scrum Team What does Product Backlog management include? Select three most applicable items.
* Optimizing the value of the work the Development Team performs * Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next * Ordering the items in the Product Backlog to best achieve goals and missions [Product Backlog management includes: * Clearly expressing Product Backlog items; * Ordering the items in the Product Backlog to best achieve goals and missions; * Optimizing the value of the work the Development Team performs; * Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, * Ensuring the Development Team understands items in the Product Backlog to the level needed.]
Category: Scrum Team How does the Scum Master serve to the Organization? Select three most appropriate answers.
* Planning Scrum implementations within the organization * Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization * Leading and coaching the organization in its Scrum adoption [The Scrum Master serves the organization in several ways, including: * Leading and coaching the organization in its Scrum adoption; * Planning Scrum implementations within the organization; * Helping employees and stakeholders understand and enact Scrum and empirical product development; * Causing change that increases the productivity of the Scrum Team; and, * Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.]
Category: Scrum Team What are three the most applicable characteristics of the Product Owner?
* Product Value Maximizer * Lead Facilitator of Key Stakeholder Involvement * Product Marketplace Expert
Category: Scrum Team How does the Scum Master serve to the Development Team? Select three most appropriate answers.
* Removing impediments to the Development Team's progress * Helping the Development Team to create high-value products * Coaching the Development Team in self-organization and cross-functionality [The Scrum Master serves the Development Team in several ways, including: * Coaching the Development Team in self-organization and cross-functionality; * Helping the Development Team to create high-value products; * Removing impediments to the Development Team's progress; * Facilitating Scrum events as requested or needed; and, * Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.]
Category: Scrum Theory What comprises Scrum?
* Scrum Teams * Roles * Events * Artifacts * Rules [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.]
Category: Scrum Team What are the characteristics of a Development Team? Select three most appropriate choices.
* Scrum recognizes no sub-teams in the Development Team * Scrum recognizes no titles for Development Team members other than Developer * Accountability belongs to the Development Team as a whole [Development Teams have the following characteristics: * They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; * Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; * Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule; * Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule; and, * Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.]
Category: Scrum Theory What are the formal Scrum events for inspection and adaptation?
* Sprint Planning * Daily Scrum * Sprint Review * Sprint Retrospective [Scrum prescribes four formal events for inspection and adaptation:]
Category: Scrum Artifacts Who is allowed to make changes in the Product Backlog?
* The Product Owner * The Development Team, but with permission of the Product Owner [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.]
Category: Scrum Events Who participates in the Sprint Review? Select all applicable variants.
* The Scrum Master * The Product Owner * The Development Team * 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.]
Category: Scrum Events Select the two meetings in which people outside from the Scrum Team are allowed to participate.
* The Sprint Review * The Sprint Planning [The Development Team may invite other people to attend the Sprint Planning in order to provide technical or domain advice. The Product Owner is responsible for inviting the Key Stakeholders to the Sprint Review meeting]
Category: Scrum Events What are the questions the Sprint Planning answers? Select two.
* What can be delivered in the Increment resulting from the upcoming Sprint? * How will the work needed to deliver the Increment be achieved?
Category: Scrum Theory What is Scrum?
A framework within which people can address complex adaptive problems, while delivering valuable products.
Category: Scrum Events What is the result of the Sprint Review?
A revised Product Backlog that defines the probable Product Backlog items for the next Sprint [The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.]
Category: Scrum Theory If an inspector determines that one or more aspects of a process deviate outside acceptable limits when an adjustment must be made?
As soon as possible to minimize further deviation [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.]
Category: Scrum Team What are the three main qualities the team model in Scrum is designed to optimize?
Creativity Flexibility Productivity [The team model in Scrum is designed to optimize flexibility, creativity, and productivity.]
Category: Scrum Events What happens during the Sprint? Select three answers.
During the Sprint: * No changes are made that would endanger the Sprint Goal; * Quality goals do not decrease; and, * Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
Category: Scrum Theory Scrum is founded on
Empiricism [Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.]
Category: Scrum Events The Development Team does not have to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
False [By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.]
Category: Scrum Theory Definition of "Done" is created during the first Sprint and remains unchanged until the Product release.
False [During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.]
Category: Scrum Theory Scrum recommends using only those Scrum components and rules which suit most for a particular project.
False [Each component within the Scrum framework serves a specific purpose and is essential to Scrum's success and usage.]
Category: Scrum Events Is it allowed to skip the Daily Scrum if there is nothing interesting to tell about?
False [Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.]
Category: Scrum Theory All the Scrum Teams working on the same product should have the same Sprint length.
False [False. Scrum does not require having aligned Sprints for multiple teams.]
Category: Scrum Theory it is normal to have a "hardening" Sprint to remove all technical debt and prepare the Product for upcoming release.
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.]
Category: Scrum Theory It is a good practice to have from time to time a special technical Sprint that consists only of tasks removing the technical debt without implementing any new functionality.
False [It is prohibited. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done."]
Category: Scrum Events Scrum does not allow additional meetings that are not defined in Scrum
False [Scrum allows additional meetings if they facilitate achieving the Sprint Goal.]
Category: Scrum Events The Daily Scrum time-box depends on the size of the Development team.
False [The Daily Scrum is a 15-minute time-boxed event for the Development Team of any size.]
Category: Scrum Artifacts The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later.
False [The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal. As new work is required, the Development Team adds it to the Sprint Backlog.]
Category: Scrum Team It is a good practice to have at least two Product Owners on big projects.
False [The Product Owner is one person, not a committee, but the Product Owner may represent the desires of a committee in the Product Backlog.]
Category: Scrum Team The Scrum Master is focused primarily on the Scrum Team and usually does not care about those outside the Scrum Team.
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.]
Category: Scrum Theory If an item in the Sprint Backlog cannot be finished by the end of the Sprint (it turned out there is a lot more work to do than it was estimated), the Sprint is cancelled.
False [The Sprint is cancelled only in the case if the Sprint Goal became obsolete. If some work could not be done, the Sprint Backlog should be re-negotiated between the Product Owner and Development Team.]
Category: Scrum Events Only the Product Owner and the Development team participate In the Sprint Planning . There is nothing to do for the Scrum Master.
False [The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.]
Category: Scrum Theory How frequently scrum users should inspect Scrum artifacts and progress toward a Sprint Goal?
Frequently, but it should not get in the way of the work [Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of the work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work.]
Category: Scrum Theory What does Cone of Uncertainty show?
How much it is known about the Product over time [The Cone of Uncertainty describes the evolution of the amount of uncertainty during a project.]
Category: Scrum Theory What does Burn-down Chart show?
How much work remains till the end of the Sprint [Burn-down chart shows the evolution of remaining effort against time.]
Category: Scrum Theory What are the three pillars that uphold Scrum?
Inspection Adaptation Transparency [Scrum is founded on empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. Three pillars uphold every implementation of empirical process control: transparency, inspection, and adaptation.]
Category: Scrum Events What is the Sprint Retrospective?
It is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint
Category: Scrum Artifacts What is the order of items in the Product Backlog?
Less valuable and most unclear items at the bottom [The Product Owner is responsible for placing the most valuable and clear items at the top of the Product Backlog.]
Category: Scrum Artifacts What part of the capacity of the Development Team does Product Backlog refinement consume?
Not more than 10% [Product Backlog refinement usually consumes no more than 10% of the capacity of the Development Team.]
Category: Scrum Events How much time does the Sprint Planning take?
Not more than 8 hours
Category: Scrum Events Sort Scrum events in the right order.
Sprint Planning Daily Scrum Sprint Review Sprint Retrospective [A sprint begins with Sprint Planning, then there are several Daily Scrum meetings following by Sprint Review and then Sprint Retrospective.]
Category: Scrum Events Please, select a time-box for each Scrum event.
Sprint Planning............[8 hours or less] Daily Scrum .................[15 Minutes] Sprint Retrospective...[4 Hours or less] Sprint Review..............[3 Hours or less] [ * Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. * The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. * Sprint Review is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter. * Sprint Retrospective is a three-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.]
Category: Scrum Artifacts Who is responsible for tracking the total work remaining in the Sprint Backlog to project the likelihood of achieving the Sprint Goal?
The Development Team [At any point in time in a Sprint, the total work remaining in the Sprint Backlog can be summed. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. By tracking the remaining work throughout the Sprint, the Development Team can manage its progress.]
Category: Scrum Theory Who is responsible for creation of the Definition of "Done"?
The Development Team [If the definition of "done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of "done" appropriate for the product. If there are multiple Scrum Teams working on the system or product release, the development teams on all of the Scrum Teams must mutually define the definition of "Done."]
Category: Scrum Artifacts Who creates the increment?
The Development Team [Only members of the Development Team create the Increment.]
Category: Scrum Artifacts Who is allowed to change the Sprint Backlog during the Sprint?
The Development Team [Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.]
Category: Scrum Artifacts Who is responsible for all estimates in the Product Backlog?
The Development Team [The Development Team is responsible for all estimates in the Product Backlog. The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate.]
Category: Scrum Events Who is allowed to participate in the Daily Scrum?
The Development Team [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]
Category: Scrum Artifacts What could be a source of requirements for any changes to be made to the product?
The Product Backlog [The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.]
Category: Scrum Artifacts What is the Sprint Backlog?
The Product Backlog items selected for this Sprint plus the plan for delivering them [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.]
Category: Scrum Events Who has the authority to cancel the Sprint?
The Product Owner [Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.]
Category: Scrum Artifacts Who is responsible for the Product Backlog?
The Product Owner [The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.]
Category: Scrum Team Who is responsible for managing the Product Backlog?
The Product Owner [The Product Owner is the sole person responsible for managing the Product Backlog.]
Category: Scrum Artifacts Who is responsible for the monitoring of the remaining work towards the Project Goal?
The Product Owner [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.]
Category: Scrum Team The Scrum Master does the following regarding the Daily Scrum (select all applicable variants):
The Scrum Master * Ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. * Teaches the Development Team to keep the Daily Scrum within the 15-minute time-box. * Enforces the rule that only Development Team members participate in the Daily Scrum.
Category: Scrum Artifacts Who is responsible for coping with incomplete artifact transparency?
The Scrum Master [The Scrum Master's job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change.]
Category: Scrum Events Who participates in the Sprint Planning? Select three.
The Scrum Master The Product Owner The Development Team [The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.]
Category: Scrum Events Who is responsible for crafting the Sprint Goal?
The Scrum Team [After the Development Team forecasts the Product Backlog items it will deliver in the Sprint, the Scrum Team crafts a Sprint Goal.]
Category: Scrum Team The Scrum Team consists of
The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master
Category: Scrum Artifacts What are the Scrum Artifacts? Select all applicable items.
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.
Category: Scrum Artifacts What belongs solely to the Development Team?
The Sprint Backlog [Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.]
Category: Scrum Events What provides guidance to the Development Team on why it is building the Increment?
The Sprint Goal [The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.]
Category: Scrum Events Please, check all opportunities to inspect and adapt.
The Sprint Retrospective The Sprint Planning The Daily Scrum The Sprint Review [Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection.]
Category: Scrum Events In which meetings the Key Stakeholders are allowed to participate?
The Sprint Review [The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However, any member of the Scrum Team can interact with them any time,]
Category: Scrum Events What is the input to the Sprint Planning? Select four.
The input to the Sprint Planning is: A. The Product Backlog B. The latest product Increment C. Projected capacity of the Development Team during the Sprint D. Past performance of the Development Team
Category: Scrum Events The purpose of the Sprint Retrospective is to (select three):
The purpose of the Sprint Retrospective is to: * Inspect how the last Sprint went with regards to people, relationships, process, and tools; * Identify and order the major items that went well and potential improvements; and, * Create a plan for implementing improvements to the way the Scrum Team does its work.
Category: Scrum Artifacts What is the Increment?
The sum of all the Product Backlog items completed during the Sprint and the value of the increments of all previous Sprints [The Increment is the sum of all the Product Backlog items completed during the Sprint "and" the value of the increments of all previous Sprints.]
Category: Scrum Events During each Sprint Retrospective the Scrum Team revises the Definition of Done.
True [During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of "Done" as appropriate.]
Category: Scrum Artifacts All Development Teams working on the same Product should use the same Product Backlog.
True [Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.]
Category: Scrum Theory Scrum does not describe agile processes and techniques.
True [Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.]
Category: Scrum Events Other people than the Scrum Team can attend the Sprint Planning in order to provide technical or domain advice.
True [The Development Team may also invite other people to attend in order to provide technical or domain advice.]
Category: Scrum Team Could the Product Owner and the Scrum Master be a part of the Development Team?
True [Yes if they are also executing the work of the Sprint Backlog.]
Category: Scrum Events What are the three main questions each member of the Development Team should answer at the Daily Scrum?
What will I do today to help the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? What did I do yesterday that helped the Development Team meet the Sprint Goal? [During the Daily Scrum, the Development Team members explain:]
Category: Scrum Events 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?
Yes, if the remaining work is also estimated, maybe in bigger units