SCRUMM a dub dub

What are two ways a Scrum Master serves to enable effective Scrum Teams?

- By removing impediments that hinder the Scrum Team. - By facilitating Developer decision-making.

A Scrum Team consists of the following:

- Product Owner - Developers - Scrum Master

Which of the following are examples of a Scrum Team practicing Scrum poorly or not exhibiting traits of a self-managing Scrum Team?

- The Developers invite external stakeholders to the Sprint Planning to ask them how to turn a Product Backlog item into an Increment via a complete and detailed Sprint Backlog. - The Developers are working within the boundaries of their organizations functional description and nicely handing off work from analyst to developer to tester to integration. - Stakeholders attend the Daily Scrum to check on the Scrum Team's progress.

Match each responsibility with the role who should do it 1. Meet the definition of done 2. Remove obstacles 3. Create the sprint backlog 4. Prioritize the product backlog

1. Developer 2. Scrum Master 3. Developer 4. Product Owner

What is the typical size for a Scrum Team?

10 or fewer.

The timebox for a Daily Scrum is?

15 minutes.

The timebox for the Sprint Planning event is?

8 hours for a monthly Sprint. For shorter Sprints it is usually shorter.

To create focus which of the following are most important to have ready when Sprint Planning begins?

A Product Goal communicated by the Product Owner. A Product Backlog with the most important items ready for discussion.

Which statement best describes Scrum?

A framework for creating complex products in complex environments.

Difference between product owner and project manager

A traditional project manager is responsible for all aspects of a project; costs, resources, execution, release, planning, capacity. Scrum is a framework for complex product development, regardless of whether the work is organized in projects. The Product Owner is accountable for maximizing the value of the product and the work performed, this is complemented by the specific accountabilities of the Developers and the Scrum Master.

When many Scrum Teams are working on a single product, what best describes the Definition of Done?

All Scrum Teams must have a Definition of Done that makes their combined Increment valuable and useful.

The Product Owner will often monitor and share progress of the Product Backlog by using which method?

Any practice based on trends of work completed and upcoming work.

What variables should a Product Owner consider when ordering the Product Backlog?

Anything that informs them to achieve the product's goals and to optimize the value delivered.

When should a Developer on a Scrum Team be replaced?

As needed, while taking into account a short-term reduction in productivity. Scrum Teams typically go through some steps before achieving a state of increased performance. Changing membership typically reduces cohesion, affecting performance and productivity in the short term.

When can the Product Backlog be updated?

At any time when done by the Product Owner or a delegate.

The CEO asks the Developers to add a "very important" item to a Sprint that is in progress. What should the Developers do?

Discuss the item with the other members of the Scrum Team so the team can decide what to do. The items selected for a Sprint have been selected as most valuable with the Product Owner during Sprint Planning. The items serve the Sprint's goal. No changes should be made that endanger the Sprint Goal. No one external to the Scrum Team can force changes on the Developers.

A Product Owner wants to change the Sprint Goal midway through a Sprint due to new market demands. How should the Scrum Team handle this situation?

Discuss the situation as a team and determine if canceling the Sprint is appropriate.

The Sprint Retrospective keeps resulting in the same improvement actions, but the team does not implement them effectively. How can the Scrum Master facilitate more meaningful change?

Encourage the team to prioritize and take ownership of the most important improvements.

How much work must the Developers complete for each Sprint?

Enough so that the Increment meets the Definition of Done.

The length of each sprint varies based on the estimated amount of work needed to accomplish the sprint goal

False

True or False: Scrum has a role called "project manager."

False

True or False: A first Sprint can start before the Product Owner has a complete and exhaustive Product Backlog in place. True

False A first Sprint requires no more than a Scrum Team and enough ideas to potentially complete a full Sprint.

True or False: When multiple Scrum Teams work together on the same product, each team should maintain a separate Product Backlog.

False Products have one Product Backlog, regardless of how many Scrum Teams are used. Any other setup makes it difficult for the Developers to determine what they should work on.

True or False: The Scrum Team must choose at least one high priority process improvement item, identified during the Sprint Retrospective, and place it in the Sprint Backlog.

False. An earlier version of the Scrum Guide prescribed the practice of placing one improvement in the Sprint Backlog. This was removed in the 2020 update to the Scrum Guide because it was felt to be too prescriptive. However, if this practice provides value to you then you should adopt it. It is simply not prescribed anymore, but can still be valuable.

True or False: It is mandatory that the product Increment be released to production at the end of each Sprint.

False. The product Increment should be usable at the end of every Sprint, but it does not have to be released.

Who creates the Definition of Done?

If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. If the Definition of Done for an Increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.

When does the next Sprint begin?

Immediately after the conclusion of the previous Sprint.

A company using Scrum decides to allow managers to attend the Daily Scrum and provide feedback to developers. What impact could this have?

It could disrupt team self-management and make the meeting ineffective.

Which statement best describes the Sprint Review?

It is when the Scrum Team and stakeholders inspect the outcome of a Sprint and figure out what to do next.

What is the Product Owner accountable for in Scrum?

Maximizing the value of the product resulting from the work of the Scrum Team.

Which statement best describes a Product Owner's responsibility?

Maximizing the value of the work the Scrum Team does.

When does a Developer become the sole owner of an item on the Sprint Backlog?

Never. All Sprint Backlog items are "owned" by the Developers on the Scrum Team. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint, and the set of Product Backlog items selected for the Sprint are collectively owned by the Developers. No individual Developer can claim ownership over an item as this would block communication and collaboration. The Sprint Backlog is updated by the Developers throughout the Sprint as more is learned.

When does a Developer become accountable for the value of a Product Backlog item selected for the Sprint?

Never. The entire Scrum Team is accountable for creating value every Sprint.

True statements about SCRUM

Scrum is a framework for developing and sustaining complex products. Each component of Scrum serves a specific purpose and is essential to your ability to use Scrum to develop complex products. Scrum is founded on empiricism and lean thinking.

Which statement best describes Scrum?

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

What are three incorrect, untrue, or misleading statements about Scrum?

Scrum is a methodology where you can pick and choose which parts of Scrum you think will work for your environment. Scrum is like traditional processes but with self-organization to replace Project Managers. Scrum is a framework that eliminates complexity.

The length of a Sprint should be:

Short enough to keep the business risk acceptable to the Product Owner. Short enough to be able to synchronize the development work with other business events. One month or less.

What is the function or purpose of Management in Scrum?

Support the Product Owner with insights and information into high value product and system capabilities. Support the Scrum Master to encourage organizational change that fosters empiricism, self-management, bottom-up intelligence, and intelligent product delivery. (Management has no official role or accountability on a Scrum Team. However, management external to the Scrum Team is relevant in setting the vision and strategy to guide the overall direction of the organization.)

Which of the following services is appropriate for a Scrum Master in regard to the Daily Scrum?

Teach the Developers to keep the Daily Scrum within the 15 minute timebox.

Right answers to know about: The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.

The Developers may work with the Product Owner to add or remove work if they find themselves with more or less capacity than expected. As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges. The Product Owner can help clarify or optimize the Sprint when asked by the Developers.

Who is required to attend the Daily Scrum?

The Developers.

Who is responsible for managing the progress of work during a Sprint?

The Developers.

The Product Owner manages the Product Backlog. Who is accountable for estimating the effort to complete the Product Backlog items?

The Developers. The Developers are responsible for all estimates. The people who will perform the work make the final estimate.

Who is responsible for managing the progress of work during a Sprint?

The Developers. The Developers use the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.

Who should know the most about the progress toward a business objective or a release, and be able to explain the alternatives most clearly?

The Product Owner The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owners' accountabilities include; developing and communicating the Product Goal, creating and communicating Product Backlog items, ordering the Product Backlog, and ensuring that the Product Backlog is transparent, visible and understood.

What best describes the relationship of the Product Owner and the stakeholders?

The Product Owner actively asks for stakeholder input and expectations to incorporate into the Product Backlog.

During a Sprint, a Developer determines that the Scrum Team will not be able to complete the items in their forecast. Who should be present to review and adjust the Product Backlog items selected?

The Product Owner and the Developers.

Adaptation requires regular inspection. In what ways does the Product Owner contribute to the results achieved by inspection ?

The Product Owner invites stakeholders to the Sprint Review to learn how the current state of the marketplace influences what is the most valuable thing to do next. The Product Owner shares the current state of Product Backlog at the Sprint Review, which, combined with the inspection of the Increment, leads to an updated Product Backlog.

Who has the final say on the order of the Product Backlog?

The Product Owner.

Which Scrum events are timeboxed?

The Scrum Guide states that the Sprint Planning, Sprint Retrospectives, and Sprint Reviews are timeboxed events. Sprints are fixed length events of one month or less to create consistency, and the Daily Scrum is a 15-minute event.

What is the main reason for the Scrum Master to be at the Daily Scrum?

The Scrum Master only ensures that all Scrum events take place and are positive, productive, and kept within the timebox.

The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity. Choose a false answer

The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.

The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.

The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint. The Sprint Backlog makes visible all of the work that the Developers identify as necessary to meet the Sprint Goal. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.

A Scrum Team consistently completes all their Sprint Backlog items but does not achieve the Sprint Goal. What could be causing this?

The Sprint Goal is too vague or misaligned with the backlog items.

Why is the Daily Scrum held at the same time and same place?

The consistency reduces complexity.

What does it mean to say that an event has a timebox?

The event can take no more than a maximum amount of time.

Is the Product Owner required to be present at the Sprint Retrospective?

Their attendance is mandatory. The Sprint Retrospective is an opportunity for the Scrum Team to assess and improve itself.

A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason:

There is no acceptable reason. A new Sprint starts immediately after the conclusion of the previous Sprint.

The three pillars of Scrum are:

Transparency, Inspection, Adaptation. Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is known.The three pillars uphold empirical and lean thinking: transparency, inspection, and adaptation.

The Developers should have all the skills needed to:

Turn the Product Backlog items they select into an Increment of a useful and valuable product. The Developers are a group of professionals who do the work of delivering an Increment of done product at the end of each Sprint. As a team, Developers have all of the skills necessary to create a product Increment.

A stakeholder complains that Scrum's lack of upfront planning makes it difficult to predict release timelines. How should the Product Owner handle this concern?

Use the Product Backlog and past velocity to provide a forecast.

The Product Backlog is ordered by:

Whatever is deemed most appropriate by the Product Owner. (The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team.)

When might a Sprint be cancelled?

When the Sprint Goal becomes obsolete. Only Product Owner has authority to cancel the Sprint

When does a Sprint conclude?

When the Sprint Retrospective is complete. (The Sprint Retrospective concludes the Sprint, and is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorterThough not typical, a Sprint can end if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to end the Sprint prematurely.)

An organization has decided to adopt Scrum, but management wants to change the terminology to fit with terminology already used. What will likely happen if this is done?

Without a new vocabulary as a reminder of the change, very little change may actually happen. The organization may not understand what has changed with Scrum and the benefits of Scrum may be lost. Management may feel less anxious.

What are typical activities for a Product Owner in a Sprint?

Work with the Developers on Product Backlog refinement. Collaborate with stakeholders, user communities, and subject matter experts.

How does an organization know that a product built using Scrum is successful?

By frequently releasing the Increment to the customer and measuring the value the customer receives.

The scrum team keeps failing to complete their work commitments each sprint. What could help?

Conducting more thorough product backlog refinement to give greater detail to the work that needs to be done

What should the Scrum Team do during the first Sprint?

Create a valuable and useful Increment. This principle applies to every sprint