The Scrum Guide

14.03 How long is the Sprint Retrospective?

At most a three-hour meeting for one-month Sprints.

6.04 What is meant by Cross-Functional?

Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.

12.01 How long is the Daily Scrum?

Daily Scrum is 15 minutes.

11.01 Who decides how the chosen work will get done in The Sprint?

Development Team decides how it will build this functionality into a "Done" product Increment during the Sprint. The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint.

6.05 What is the team model in Scrum designed to do?

Optimize: 1. Flexibility 2. Creativity 3. Productivity

5.10 What is meant by Commitment?

People personally commit to achieving the goals of the Scrum Team.

3.01 What is the definition of Scrum?

Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

9.01 What are Scrum Events used for?

Scrum Events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.

14.07 What are Scrum Artifacts?

Scrum Guide: Artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts are defined by Scrum to maximize transparency of key information so that everybody has the same understanding of the artifact. From Innolution: A tangible by-product produced during product development such as the Product Backlog, Sprint Backlog, and potentially shippable product Increment.

3.03 What is Scrum not?

Scrum is not a process, technique, or definitive method.

10.06 How long is Sprint Planning?

Sprint Planning is eight hours for a one-month Sprint.

13.02 How long is the Sprint Review?

Sprint Review is four-hour meeting for one-month Sprints.

10.04 Why are Sprint cancelations bad?

Sprint cancellations consume resources and are often traumatic to the Scrum Team.

9.08 What is the duration of each Sprint?

Sprints are limited to one calendar month.

7.01 What is the Development Team?

The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint.

12.09 Who conducts the Daily Scrum?

The Development Team is responsible for conducting the Daily Scrum.

12.07 What often times occurs right after the Daily Scrum?

The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint's work.

11.06 What should be accomplished by the end of 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.

10.11 Who determines how many items should be completed from the Product Backlog?

The Development Team.

11.04 What does the Product Owner do during Sprint Planning?

The Product Owner can help to clarify the selected Product Backlog items and make trade-offs.

6.09 Can the Product Owner delegate responsibilities?

The Product Owner may have the Development Team do its tasks, however, the Product Owner remains accountable.

12.08 What does the Scrum Master do during the Daily Scrum?

The Scrum Master ensures that the Development Team has the meeting and that the Development Team keeps the Daily Scrum within the 15-minute time-box. If others are present, the Scrum Master ensures that they do not disrupt the meeting.

10.07 What is the Scrum Master's role in Sprint Planning?

The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master ensures that the Scrum Team keeps it within the time-box.

7.05 What is a Scrum Master?

The Scrum Master is a servant-leader for the Scrum Team.

5.11 What is meant by Courage?

The Scrum Team members have courage to do the right thing and work on tough problems.

13.05 What should the result be 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.

3.06 What is the purpose for the rules of Scrum?

The rules of Scrum bind together the roles, events, and artifacts, by governing the relationships and interaction between them.

9.10 What happens if a Sprint is too long?

When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints also limit risk to one calendar month of cost.

9.07 What are Sprints used for?

1. Accomplish a goal of what is to be built 2. A design and flexible plan that will guide building it 3. The work 4. The resultant product increment.

15.01 What is the Product Backlog?

1. An ordered list of everything that is known to be needed in the product. 2. The single source of requirements for any changes to be made to the product.

13.04 What are the elements of the Sprint Review?

1. Attendees include the Scrum Team and key stakeholders invited by the Product Owner; 2. The Product Owner explains what Product Backlog items have been "Done" and what has not been "Done"; 3. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; 4. The Development Team demonstrates the work that it has "Done" and answers questions about the Increment; 5. The Product Owner discusses the Product Backlog as it stands and projects likely target and delivery dates based on progress; 6. The entire group collaborates on what to do next; 7. Review of how the marketplace, or potential use of the product, might have changed the most valuable thing to do next; 8. Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.

6.08 What does Backlog Management include?

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

8.02 What is the Scrum Master's service to the Development Team?

1. Coaching the Development Team in self-organization and cross-functionality; 2. Helping the Development Team to create high-value products; 3. Removing impediments to the Development Team's progress; 4. Facilitating Scrum events as requested or needed; 5. Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.

5.09 What are the Scrum Values?

1. Commitment 2. Courage 3. Focus 4. Openness 5. Respect

14.04 What are the Scrum Master's responsibilities during a Sprint Retrospective?

1. Ensures that the event takes place and that attendants understand its purpose. 2. Ensures that the meeting is positive and productive. 3. Teaches all to keep it within the time limit. 4. Participates as a peer team member in the meeting for accountability over the Scrum process. 5. Encourages the Scrum Team to improve its development process and practices, and make it more effective and enjoyable for the next Sprint.

8.01 What is the Scrum Master's service to the Product Owner?

1. Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team; 2. Finding techniques for effective Product Backlog management; 3. Helping the Scrum Team understand the need for clear and concise Product Backlog items; 4. Understanding product planning in an empirical environment; 5. Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; 6. Understanding and practicing agility; 7. Facilitating Scrum events as requested or needed.

12.10 What do Daily Scrums accomplish?

1. Improve communications 2. Eliminate other meetings 3. Identify impediments to development for removal 4. Highlight and promote quick decision-making 5. Improve the Development Team's level of knowledge

14.05 What is the purpose of the Sprint Retrospective?

1. Inspect how the last Sprint went with regards to people, relationships, process, and tools; 2. Identify and order the major items that went well and potential improvements; 3. Create a plan for implementing improvements for the way that the Scrum Team does its work.

8.03 What is the Scrum Master's service to the Organization?

1. Leading and coaching the organization in its Scrum adoption; 2. Planning Scrum implementations within the organization; 3. Helping employees and stakeholders understand and enact Scrum and empirical product development; 4. Causing change that increases the productivity of the Scrum Team; 5. Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization

3.02 What are the characteristics of Scrum?

1. Lightweight 2. Simple to understand 3. Difficult to master

6.07 What is the Product Owner responsible for?

1. Maximizing the value of the product resulting from work of the Development Team, 2. The sole person responsible for managing the Product Backlog.

9.06 What are rules of The Sprint?

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

4.01 Name examples of how Scrum has been used.

1. Research and identify viable markets, technologies, and product capabilities; 2. Develop products and enhancements; 3. Release products and enhancements, as frequently as many times per day; 4. Develop and sustain Cloud (online, secure, on-demand) and other operational environments for product use; and, 5. Sustain and renew products.

3.05 What does the Scrum Framework consist of?

1. Scrum Teams and their associated roles 2. Events 3. Artifacts 4. Rules

5.08 What are the four formal events for Inspection and Adaptation?

1. Sprint Planning 2. Daily Scrum 3. Sprint Review 4. Sprint Retrospective

10.09 What work can be done during this Sprint?

1. The Development Team works to forecast the functionality that will be developed during the Sprint. 2. The Product Owner discusses the objective that the Sprint should achieve. 3. The Product Owner discusses which Product Backlog items should be completed to achieve the Sprint Goal. 4. The entire Scrum Team collaborates on understanding the work of the Sprint.

10.10 What is used as input for Sprint Planning?

1. The Product Backlog 2. The latest product Increment 3. Projected capacity of the Development Team during the Sprint 4. Past performance of the Development Team

11.02 What is the Sprint Backlog?

1. The Product Backlog items selected for this Sprint, 2. Plus the plan for delivering them.

7.02 What are the characteristics of the Development Team?

1. They are self-organizing; 2. Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment; 3. Scrum recognizes no titles for Development Team members; 4. Scrum recognizes no sub-teams in the Development Team; 5. Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.

4.10 What are the three pillars which uphold every implementation of empirical process control?

1. Transparency 2. Inspection 3. Adaptation.

10.08 What questions are answered in Sprint Planning?

1. What can be delivered in the Increment resulting from the upcoming Sprint? 2. How will the work be achieved?

12.06 What is an example of questions asked during the Daily Scrum?

1. What did I do yesterday that helped the Development Team meet the Sprint Goal? 2. What will I do today to help the Development Team meet the Sprint Goal? 3. Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

6.06 How do Scrum Teams deliver products?

1.Iteratively 2.Incrementally 3.Maximizing opportunities for feedback

6.01 Who does the Scrum Team consist of?

1.Product Owner 2.Development Team 3.Scrum Master

9.05 What is contained within The Sprint?

1.Sprint Planning 2.Daily Scrums 3.The development work 4.The Sprint Review 5.The Sprint Retrospective

10.02 When should a Sprint be cancelled?

A Sprint would be cancelled if the Sprint Goal becomes obsolete and if it no longer makes sense given the circumstances.

5.07 How quickly should Adaptation occur?

An adjustment must be made as soon as possible to minimize further deviation.

13.01 What is the Sprint Review?

An informal meeting (not a status meeting) to inspect the Increment and adapt the Product Backlog if needed, and to elicit feedback and foster collaboration.

9.02 What opportunities do Scrum Events create?

Each Scrum Event is a formal opportunity to inspect and adapt something.

4.08 What is Empiricism?

Empiricism asserts that knowledge comes from experience and making decisions based on what is known.

5.12 What is meant by Focus?

Everyone focuses on the work of the Sprint and the goals of the Scrum Team.

7.03 What should the size be of the Development Team?

From 3 to 9 members. Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint.

5.06 What is meant by Adaptation?

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.

4.06 What do the words "develop" and "development" refer to?

In the Scrum Guide "develop" and "development" refer to complex work.

5.04 How frequently should Inspections occur?

Inspection should occur frequently, but not so frequently that they get in the way of work.

5.05 When are Inspections most beneficial?

Inspections are most beneficial when: 1. Diligently performed by skilled inspectors, 2. At the point of work.

11.09 When is the Sprint Goal created?

It is created during the Sprint Planning meeting.

9.04 What is The Sprint?

It is the heart of Scrum, a time-boxed event of one month or less, during which a "Done", useable, and potentially releasable product Increment is created.

11.05 What happens if the Development Team determines it has too much or too little work?

It may renegotiate the selected Product Backlog items with the Product Owner. The Development Team may also invite other people to attend to provide technical or domain advice.

11.08 What does the Sprint Goal provide?

It provides guidance to the Development Team on why it is building the Increment. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint.

10.03 What happens when a Sprint is cancelled?

Items are reviewed and any potentially releasable items are typically accepted by the Product Owner. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog.

10.01 How can a Sprint be cancelled?

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.

5.14 What is meant by Respect?

Scrum Team members respect each other to be capable, independent people.

4.09 What approach does Scrum employ regarding risk?

Scrum employs an iterative, incremental approach to optimize predictability and control risk.

4.02 Where might we find Scrum where it affects our daily lives?

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's utility in dealing with complexity is proven daily.

4.07 What theory is Scrum founded on?

Scrum is founded on empirical process control theory, or empiricism.

3.04 What does Scrum make clear?

Scrum makes clear the relative efficacy of your product management, and work techniques, so that you can continuously improve the product, the team, and the working environment.

4.03 Where has Scrum proved especially effective?

Scrum proved especially effective in iterative and incremental knowledge transfer and is now widely used for products, services, and the management of the parent organization.

5.03 What is meant by Inspection?

Scrum users must frequently inspect Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances.

4.05 The strengths of Scrum are demonstrated when operating with what kind of teams?

Scrum's strengths are present when operating in single, several, many, and networks of teams that develop, release, operate and sustain the work and work products of thousands of people.

6.02 What are the traits of the Scrum Team?

Self-organizing and Cross-functional.

6.03 What is meant by Self-organizing?

Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.

5.01 What is meant by Transparency?

Significant aspects of the process must be visible to those responsible for the outcome.

9.11 How do Sprints enable predictability?

Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month.

12.05 What is the structure of the Daily Scrum?

The Daily Scrum can be conducted in different ways as long as it focuses on progress toward the Sprint Goal.

12.02 What is the Daily Scrum?

The Daily Scrum is an internal meeting for the Development Team where they plan work for the next 24 hours.

12.04 Where is the Daily Scrum held?

The Daily Scrum is held at the same time and place each day to reduce complexity.

11.03 What does the Development Team usually do during Spring Planning?

The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often into units of one day or less.

13.03 What does the Scrum Master's role during the Sprint Review?

The Scrum Master ensures that the event takes place, that attendees understand its purpose, and that everyone involved keeps it within the time-box.

7.04 What is the Scrum Master responsible for?

The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Master does this by helping everyone understand Scrum theory, practices, rules, and values.

5.13 What is meant by Openness?

The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work.

14.06 What should the result be of the Sprint Retrospective?

The Scrum Team should have identified improvements that it will implement in the next Sprint.

11.07 What is the Sprint Goal?

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

14.01 What is the Sprint Retrospective?

The Sprint Retrospective is a formal opportunity to focus on inspection and adaptation where the Scrum Team inspects itself and creates a plan for improvements to be enacted during the next Sprint.

14.02 When does the Sprint Retrospective occur?

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.

4.04 What is the essence of Scrum?

The essence of Scrum is a small team of people which is highly flexible and adaptive.

10.05 What is Sprint Planning?

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.

9.03 What are Scrum Events designed for?

These events are specifically designed to enable critical transparency and inspection.

12.03 What is the purpose of the Daily Scrum?

To optimize team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Development Team uses 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.

5.02 What is the requirement of Transparency?

Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen. For example: 1. A common language referring to the process must be shared by all participants; 2. Those performing the work and those inspecting the resulting increment must share a common definition of "Done".