Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Scrum > Part 3 > Flashcards

Part 3 Flashcards

1
Q

What are Scrum Events?

A
  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
2
Q

Why does Scrum use events?

What is meant by “Time Boxed”?

A
  1. To Create regularity and minimize on meetings not defined in scrum.
  2. It has a maximum duration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Once a sprint begins can it be shortened or lengthened?

Does this effect any following events?

A
  1. No. Its fixed.
  2. No. remaining events may end whenever the purpose of events have been achieved this will ensure appropriate amount of time is spent preventing waste.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is a Sprint?

Typically how long is a sprint?

When do new sprints start?

A
  1. Considered the Heart of the Scrum. Can be considered a project.
  2. Has a time-box of a month or less with a “done” useable and potentially releasable product increment is created.
    1. Sprints have consistent durations throughout a dev effort.
  4. A new sprint starts immediately after the other finishes.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What does a sprint contain and consist of?

A
  1. Sprint Planning,
  2. Daily Scrums,
  3. the dev work,
  4. the sprint review
  5. the sprint retrospective.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What should not happen during the sprint?

What’s the exception?

A
  1. No changes made that could endanger the sprint goal
    1. Quality goals do not decrease
  3. Scope may be clarified and renegotiated between product owner and dev team as more is learned.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is the max duration of a sprint and Why?

A
  1. 1 month
  2. When duration is too long definition of what is being built may change, complexity may rise, and risk may increase. So to minimize this the one month time period helps by:
    1. Adding predictability as inspection and adaptation of sprint goals will happen atleast once a month.
    1. Also limit risk of cost per month.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Who has the authority to cancel a sprint?

A

Product Owner

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

Why would a sprint be cancelled?

A
  1. Sprint goal becomes obsolete. In general it should be cancelled if it nolonger makes sense given the circumstances. It could be due to:
    1. Company changes direction
  3. 2.Market conditions change
    1. Tech conditions change
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What happens after the sprint cancellation?

If work is partially completed will the product owner accept it?

How does the product owner deal with incomplete product backlog items?

A
  1. Completed and “done” product backlog items are reviewed.
  2. If its potentially releasable the product owner typically accepts it.
  3. They are re-estimated and put back into the product backlog.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the effects of a Sprint cancellation?

How often do cancellations occur?

A
  1. They consume resources b/c everyone regroups for another sprint planning.
    1. Traumatic to the scrum team
  3. VERY uncommon
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a Scrum Plan and its topics?

Who creates it?

What is the typical duration of a Sprint planning?

A
  1. The work to be performed in the sprint.
    1. What can be done this sprint?
    1. How will the chosen work get done?
  4. Entire Scrum team.
  5. Max eight hrs for a one month sprint. For shorter sprints the event is shorter.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

WHAT IS THE SCRUM MASTERS ROLE IN SCRUM PLANNING?

A
  1. Ensures the event happens and that its purpose is understood.
  2. Teaches the team to keep it in the time-box.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Who determines what can be done this Sprint?

A
  1. The entire team collabs on understanding the work of the sprint.
  2. The dev team – works to forecast functionality that’ll be developed during the sprint.
  3. Product Owner – discusses the objective to be achieved and the product back log items.
    1. If the work is completed in the sprint, the sprint goal would be achieved.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is discussed?

Who decides the number of items selected from the product backlog?

A
  1. Product Backlog
    1. Latest product increment
    1. Projected capacity of the dev team during the sprint
  4. By the dev team…solely, as only the dev team can assess what it can accomplish.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is a sprint back log?

How much work is planned during the sprint planning?

What units is the work broken down to?

What happens if the dev team determines it has too much or too little work?

A
  1. The product backlog items selected for the sprint plus the plan for delivering them is called the sprint backlog.
  2. Enough for dev team to forecast what it believes it can achieve in the upcoming sprint.
  3. 1 day or less
  4. Renegotiation with the product owner.
17
Q

What should the dev team be able to describe following the sprint planning?

A

How it will self-organize and accomplish the sprint goal and create the anticipated increment.

18
Q

What is a sprint goal and when is the it created?

A
  1. An objective that will be met w/I the sprint through implementation of the product backlog.
    1. Provides guidance for the dev team on why its building the increment.
    1. Give dev team some flexibility regarding the functionality implemented within the sprint.
  4. Created during sprint planning
19
Q

What do dev teams do to implement sprint goals?

What happens if the work turns out different than expected?

A
  1. Functionality and technology

2. Collab with Product owner to negotiate the scope of sprint backlog within the sprint.

20
Q

What is a Daily Scrum?

Why is it done?

Where is it done?

A
  • A KEY INSPECT AND ADAPT MEETING*
    1. 15 min time boxed event for dev team, where work for the next 24 hrs is planned.
  1. To optimize team collab and performance by inspecting the work done since the last daily scrum, and forecasting upcoming sprint work.
    1. Increases probability that the sprint goal will be met.
  3. Done in the same place and time to reduce complexity.
21
Q

Daily scrum impact on the dev team?

A
  1. Improves comms
  2. Eliminates other meetings
  3. Identifies impediments to dev for removal.
  4. Highlight and promote quick decision making
  5. Improve the dev teams level of knowledge
22
Q

WHAT IS SCRUM MASTERS ROLE IN THE DAILY SCRUM?

A
  1. To set the meeting.
  2. Teach the team to stay within the time-box.
  3. If others are present ensures they don’t disrupt the meeting.
23
Q

What is a Sprint Review?

What happens during one?

A
  1. Held at the end of the sprint to inspect the increment and adapt the product backlog if needed.
  2. During the review the scrum team and stakeholders collab about what was done in the sprint.
    1. Based on that and any changes to the product backlog during the sprint, attendees collab on the next things that could optimize value.
24
Q

Are Sprint Reviews Formal or Informal?

Duration?

A
  1. Informal; intended to elicit feedback and foster collab.

2. Max 4hr for 1 month sprint.

25
Q

WHAT IS THE SCRUM MASTERS ROLE IN A SPRINT REVIEW?

A
  1. Ensures that the event takes place and that attendees understand its purpose.
  2. Teaches them to keep it to 4hrs.
26
Q

A Scrum Review includes the following: Pt 1

A
  1. Product owner invites everyone

2. Product owner explains what product backlog items have been “done” and which have not.

27
Q

A Scrum Review includes the following: Pt 2

A
  1. The dev team discusses what went well during the sprints, any problems, and how the probs were solved.
  2. Dev team demonstrates the work it has “done” and answers questions about the increment.
28
Q

A Scrum Review includes the following: Pt 3

A
  1. Product Owner discusses the product backlog as it stands, then projects likely target and delivery dates.
  2. The grp collabs on what to do next to provide valuable input to next sprint planning.
29
Q

A Scrum Review includes the following: Pt 4

A
  1. Review how the marketplace or potential use of product may have changed and whats the most valuable thing to do next.
  2. Review of timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product.
30
Q

What is the result of a Scrum review?

A
  1. A revised product backlog that defines the probably product backlog items for the next sprint.
    1. May also be adjusted overall to meet new opportunities.

Scrum (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions