Scrum Master

What happens when a Sprint is cancelled?

- 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

The Scrum Team consists of

- Development Team - Scrum Master - Product Owner

What are Product Backlog features?

- It is never complete - As long as a product exists, its Product Backlog also exists - It is dynamic

What does Product Backlog management include?

- Optimizing the value of the work the Development Team performs - Ordering the items in the Product Backlog to best achieve goals and missions - Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next 1) Clearly expressing Product Backlog items; Ordering the items in the Product Backlog to best achieve goals and missions; 2) Optimizing the value of the work the Development Team performs; 3) Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, 4) Ensuring the Development Team understands items in the Product Backlog to the level needed.

Select the five Scrum Values

-Courage -Openness -Respect -Commitment -Focus

What comprises Scrum (select four)?

1) Roles 2) Rules 3) Artifacts 4) Events

What is Scrum?

A framework within which people can address complex adaptive problems, while delivering valuable products.

What is the essence of Scrum?

A small team of people that is highly flexible and adaptive

What are the three pillars that uphold Scrum?

Adaption Transparency Inspection 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.

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, when must an adjustment 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.

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.

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.

What does the word "development" mean in the context of Scrum?

Complex work that can include all the suggested options and even more When the words "develop" and "development" are used in the Scrum Guide, they refer to complex work including software and hardware development, development and releasing of products and enhancements, development and sustaining product operational environments, research and identifying of viable markets and technologies, and even more.

What are the characteristics of a Development Team?

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, regardless of the work being performed by the person; Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and, Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

How does Definition of "Done" help the Scrum Team?

DoD is used to assess when work is complete on the product Increment DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning DoD ensures artifact transparency

Definition of Done can be reviewed and adapted during each Sprint Retrospective

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done", if appropriate and not in conflict with product or organizational standards.

Scrum is founded on

Empiricism

The Scrum Master does the following regarding the Daily Scrum

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 If others are present at the Daily Scrum, ensures that they do not disrupt the meeting

The Daily Scrum always should take exactly 15 minutes. For example, if your team managed doing it in 5 minutes, you should spend 10 more minutes on some useful team activity like Product Backlog refinement, but not more.

False

The Sprint Backlog is created at the Sprint Planning. It is prohibited to add new work into the Sprint Backlog later by the Development Team.

False

How frequently should scrum users inspect Scrum artifacts and progress toward a Sprint Goal?

Frequently, but it should not get in the way of the work

What does Cone of Uncertainty show?

How much is known about the Product over time

What does Burn-down Chart show?

How much work remains till the end of the Sprint

What are the questions the Sprint Planning answers?

How will the work needed to deliver the Increment be achieved? What can be delivered in the Increment resulting from the upcoming Sprint?

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

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

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.

What is the order of items in the Product Backlog?

Less valuable and most unclear items at the bottom

Is it allowed to skip the Daily Scrum if there is nothing interesting to talk about?

No. 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.

What part of the capacity of the Development Team does Product Backlog refinement usually consume?

Not more than 10%

What belongs solely to 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.

Check all the formal opportunities to inspect and adapt

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.

What are the Scrum Artifacts?

Product Backlog Sprint Backlog Increment

What is the input to the Sprint Planning?

Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team.

Who participates in the Sprint Planning?

Product Owner Development Team Scrum Master

What are the three most applicable characteristics of the Product Owner?

Product Value Maximizer Lead Facilitator of Key Stakeholder Involvement Product Marketplace Expert

Where can Scrum be used?

Scrum has been used to develop software, hardware, embedded software, networks of interacting function, autonomous vehicles, schools, government, marketing, managing the operation of organizations and almost everything we use in our daily lives, as individuals and societies. Scrum has been used extensively, worldwide, to: Research and identify viable markets, technologies, and product capabilities; Develop products and enhancements; Release products and enhancements, as frequently as many times per day; Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and, Sustain and renew products.

How long should the Sprint Planning be?

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. There is no need to decompose all the Items in the Sprint Backlog. It can be done only for the first days of the Sprint.

Who creates the increment?

The Development Team

Who is responsible for all estimates in the Product Backlog?

The Development Team

Select the two meetings in which people outside the Scrum Team are allowed to participate.

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

Who is allowed to make changes in the Product Backlog?

The Development Team, but with permission of the Product Owner The Product Owner

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.

Who is allowed to participate in the Daily Scrum?

The Development Team. The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

What could be a source of requirements for any changes to be made to the product?

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.

What is the Sprint Backlog?

The Product Backlog items selected for this Sprint plus the plan for delivering them

Who has the authority to cancel the Sprint?

The Product Owner

Who is responsible for monitoring progress toward high-level goals?

The Product Owner

Who is responsible for the Product Backlog?

The Product Owner

Who is responsible for managing the Product Backlog?

The Product Owner is the sole person responsible for managing the Product Backlog.

Who is responsible for promoting and supporting Scrum?

The Scrum Master

Who participates in the Sprint Review?

The Scrum Master The Development Team The Product Owner The Key Stakeholders

The Scrum Master is focused primarily on the Scrum Team and usually does care about those outside the Scrum Team.

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.

How does the Scrum Master serve the Development Team?

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.

How does the Scrum Master help the Product Owner?

The Scrum Master serves the Product Owner in several ways, including: Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible; 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.

How does the Scrum Master serve the Organization?

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.

Who is responsible for crafting the Sprint Goal at the Sprint Planning?

The Scrum Team

What provides guidance to the Development Team on why it is building the Increment?

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.

In which meetings the Key Stakeholders are allowed to participate?

The Sprint Review

What are the time-boxes for the Sprint Review and the Sprint Retrospective?

The Sprint Review is at most a four-hour meeting for one-month Sprints. The Sprint Retrospective is at most a three-hour meeting for one-month Sprints.

What is the result of the Sprint Review?

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.

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

What are the three main qualities the team model in Scrum is designed to optimize?

The team model in Scrum is designed to optimize flexibility, creativity, and productivity.

All Development Teams working on the same Product should use the same Product Backlog.

True

What are the three questions the Scrum Guide gives as an example that can be used at the Daily Scrum?

What did I do yesterday that helped the Development Team meet the Sprint Goal? 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?

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 The Scrum Guide requires only the work planned for the first days of the Sprint is decomposed by the end of the Sprint Planning, often to units of one day or less. However, 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.

Could the Product Owner and the Scrum Master be a part of the Development Team?

Yes. Scrum does not prohibit the Product Owner or the Scrum Master do development work. However, it is not the best practice because it could create a conflict of interest.