Scrum Guide Flashcards

1
Q

What is Scrum?

A

Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

Scrum is:

  • Lightweight
  • Simple to understand
  • Difficult to master
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What does Scrum framework consist of?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What does empiricism assert?

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are Scrum pillars?

A

Scrum pillars are:

  1. Transparency
  2. Inspection
  3. Adaptation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are Scrum events?

A

Scrum defines 5 events:

  1. Sprint
  2. Sprint Planning
  3. Daily Scrum
  4. Sprint Review
  5. Sprint Retrospective
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are Scrum values?

A

Scrum defines 5 values:

  1. Commitment
  2. Courage
  3. Focus
  4. Openness
  5. Respect
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What does the Scrum Team consist of?

A

The Scrum Team consists of the following:

  1. Product Owner
  2. Development Team
  3. Scrum Master
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is the Scrum Team model designed to optimise?

A

The Scrum Team model is designed to optimise:

  1. Flexibility
  2. Creativity
  3. Productivity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the Product Owner responsible for?

A

The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Is the Product Owner a one person role or can it be a committee?

A

The Product Owner is one person, not a committee.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What does the management of the Product Backlog imply?

A

The management of the Product Backlog implies:

  • Clearly expressing Product Backlog items;
  • Ordering the items in the Product Backlog to best achieve goals and missions;
  • Optimising 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What does the Development Team consist of?

A

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.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the characteristics of the Development Team?

A
  • 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 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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What is the recommended size of a Development Team? What happens if the team is smaller than the minimum? And larger?

A

Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. It is recommended a team of 3 to 9 people.

Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment.

Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is a Scrum Master? What is the Scrum Master responsible for?

A

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

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 well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

In what ways does the SM serve the PO?

A
  • 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.
17
Q

In what ways does the SM serve the DT?

A
  • 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.
18
Q

In what ways does the SM serve the organisation?

A
  • 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.
19
Q

What are Scrum Events designed for?

A

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.

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

20
Q

What is a Sprint?

A

A Sprint is a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint.

21
Q

What do Sprints consist of?

A

Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.

22
Q

What is the Sprint Planning?

A

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. It is where the work to be performed in the Sprint is planned. This plan is created by the collaborative work of the entire Scrum Team.

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

Sprint Planning answers the following:

  1. What can be delivered in the Increment resulting from the upcoming Sprint?
  2. How will the work needed to deliver the Increment be achieved?
23
Q

Can changes be done during a Sprint that endanger the Sprint Goal?

A

No. No changes are made that would endanger the Sprint Goal;

24
Q

Can the quality goals decrease in scope of a Sprint?

A

No. Quality goals do not decrease;

25
Q

Can scope be re-negotiated during a Sprint?

A

Yes. Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.

26
Q

Who can cancel a Sprint?

A

The Product Owner

27
Q

When can a Sprint be cancelled and under what circumstances is it cancelled?

A

A Sprint can be cancelled at any moment during the time-box. It is cancelled when the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances.

28
Q

What is done with the items in the Product Backlog that were selected for a Sprint when it gets cancelled?

A

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 work done on them depreciates quickly and must be frequently re-estimated.

29
Q

What is the outcome of the Sprint Planning?

A

The outcome is of the Sprint planning is:

  1. A Sprint Goal, crafted between the Scrum Team,
  2. The items selected from the Product Backlog that will meet the goal. PO knows what items meet the goal, and DT knows how many items can be selected for the Sprint, and
  3. A plan of how to turn the selected items into a Done increment. The DT is in charge of this part.

The selected PB items plus the plan is the Sprint Backlog.