news-agile - Tumblr blog

news-agile · 5 years

Text

Scrum Quiz

What is Scrum?

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

-----

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.

-----

Who is responsible for managing the Product Backlog?

The Product Owner

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

-----

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.

-----

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.

-----

How much time does the Sprint Planning take?

Not more than 8 hours.

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.

-----

How does the Scrum Master serve the Organization?

- Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization - Planning Scrum implementations within 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.

-----

Who is allowed to make changes in the Product Backlog?

- The Development Team, but with permission of the Product Owner - 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.

-----

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.

-----

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.

-----

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.

-----

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

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.

-----

What comprises Scrum ?

- Rules - Artifacts - Roles - Events

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. The rules of Scrum bind together the events, roles, and artifacts, governing the relationships and interaction between them.

-----

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.

-----

Scrum does not allow additional meetings that are not defined in Scrum.

False

Scrum allows additional meetings if they achieving the Sprint Goal

-----

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 - Create a plan for implementing improvements to the way the Scrum Team does its work

-----

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

-----

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

Yes

Yes if they are also executing the work of the Sprint Backlog.

-----

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.

-----

The Scrum Master does the following regarding the Daily Scrum:

- Ensures that the Development Team has the meeting - 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

-----

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

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.

-----

The Scrum Team consists of

- The Development Team - The Product Owner - The Scrum Master

-----

What are the Scrum Artifacts?

- Product Backlog - Sprint Backlog - Increment

-----

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?

The structure of the Daily Scrum is set by the Development Team and can be conducted in different ways if it focuses on progress toward the Sprint Goal. Some Development Teams will use questions, some will be more discussion based. Here is an example of what might be used: 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?

-----

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

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

-----

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.

-----

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.

-----

Who participates in the Sprint Review?

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

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

-----

Where Scrum can be used?

- Development of almost everything we use in our daily lives as individuals and societies - Research and identifying of viable markets, technologies, and product capabilities - Development and sustaining of Cloud and other operational environments - Development of products and enhancements - Managing the operation of an organization - Development of software and hardware

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.

-----

What does Product Backlog management include?

- Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next - Optimizing the value of the work the Development Team performs - 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.

-----

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

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

-----

During each Sprint Retrospective the Scrum Team reviews the Definition of Done and changes it if necessary.

True

During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by adapting the definition of “Done” as appropriate.

-----

What happens during the Sprint?

- Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned - Quality goals do not decrease - No changes are made that would endanger the Sprint Goal

-----

Select the two meetings in which people outside 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

-----

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

Not more than 10%

-----

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.

-----

Who is allowed to change the Sprint Backlog during the Sprint?

The Development Team

-----

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

-----

What are the formal Scrum events for inspection and adaptation?

- The Sprint Planning - The Daily Scrum - The Sprint Retrospective - The Sprint Review

-----

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

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

-----

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.

-----

What are Product Backlog features?

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

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.

-----

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.

-----

What are the three pillars that uphold Scrum?

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

-----

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.

-----

Who participates in the Sprint Planning?

- The Development Team - The Scrum Master - The Product Owner

-----

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.

True

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.

#scrum

1 note · View note