Events Flashcards by Alicia Hildebrand

What is the Primary goal of Scrum?

=> to deliver value

Scrum is about transforming ideas, that are stored in the Product Backlog, into value through Sprints

How well did you know this?

Not at all

Perfectly

Who’s accountable for ensuring that the Product Backlog is good?

=> Product Owner

Is the single person accountable for defining what will be done and in what sequence

! If you have a bad PO that doesn’t understand the business domain, is not committed to the product, or does not collaborate with stakeholders or the Scrum Team, you will most probably have a low-quality Product Backlog that will most likely lead to failure in delivering value.

How well did you know this?

Not at all

Perfectly

How long is a Sprint?

(maximum lenght)

=> max 1 Month

How well did you know this?

Not at all

Perfectly

How long is the Sprint Planning?

Max. 8 h

How well did you know this?

Not at all

Perfectly

How long is a Daily Scrum?

max. 15 Min

How well did you know this?

Not at all

Perfectly

How long ist the Sprint Review?

for a 1 month Sprint: max. 4 h

for a shorter Sprint: usually shorter

How well did you know this?

Not at all

Perfectly

How long ist the Sprint Retrospective?

for a 1 month Sprint:
max. 3 h

for a shorter Sprint:
usually shorter

How well did you know this?

Not at all

Perfectly

What is Flaccid Scrum?

=> Scrum Anti-Pattern

Reflects the behavior of the teams that focus too much on delivering features as fast as possible while compromising quality.

Consequently: While they achieve great velocity on the first Sprints, they suffer a lot later when dealing with the low-quality product they have produced!

How well did you know this?

Not at all

Perfectly

What is Velocity?

Übersetzung: Geschwindigkeit

=> wide spread measure of Team performance
(amount of Product Backlog turned into an Increment during a Sprint

Beispiel:
in the last Sprint the Team delivered 20, 25 and 28 points.
On average, the Team gets Done with 21 points per Sprint

=> it has a velocity of 21 Point per Sprint

How well did you know this?

Not at all

Perfectly

What is the Sprint?

=> is a container for all other events

(Sprint Planning, Daily Scrum, Sprint Review & Sprint Retrospective)

=> „The Heartbeat of Scrum“

How well did you know this?

Not at all

Perfectly

What are Scrum events for?

=> are used to create regularity and to minimize the need for meetings not defined in Scrum

=> all the events of Scrum (except Sprint) are designed to promote transparency and inspection, being a formal opportunity to inspect and adapt something

How well did you know this?

Not at all

Perfectly

When and where are the Scrum events held?

=> optimally, all of the events are held at the same time and place to reduce complexity

How well did you know this?

Not at all

Perfectly

When are the Scrum events over?

=> A Sprint is only over, when the time-box elapses (or if it gets canceled)

=> the other events can finish before the time-box elapses if their purpose has been achieved

How well did you know this?

Not at all

Perfectly

What is the Sprint Planning?

=> initiates the Sprint,

by laying out the work to be performed for the Sprint

The Sprint is like a mini project and the Sprint Planning is where the Scrum Team defines a goal what to build and the flexible plan to guide achieving it.
The Plan is called the Sprint Backlog.

How well did you know this?

Not at all

Perfectly

Who participates in Sprint Planning?

=> the entire Scrum Team

Further they may invite other Stakeholders to attend and provide advice (specialists to assist).

How well did you know this?

Not at all

Perfectly

Which 3 topics are addressed in the Sprint Planning?

=> the event has 3 topics to be addressed:

1| Why is this Sprint valuable?
=> Scrum team defines a Sprint Goal

2| What can be done in this Sprint?
=> Product Backlog items selected for the Sprint

3| How will the chosen work get done?
=> a plan for delivering the Product Backlog Items => Sprint Backlog

How well did you know this?

Not at all

Perfectly

Who is allowed to change the Sprint Backlog after the Sprint Planning is over?

=> only the Developers

because it is their only source of work

When does a new Sprint start?

=> immediately after the conclusion of the previous Sprint

(Heartbeat)

Name 3 Factors of deciding how long the Sprints are.

Factor 1: Risk
They should be short enough to keep the risks acceptable.
The more uncertain the business environment, (usually) the shorter the Sprint should be.

Factor 2: Number of Developers
The number of Developers; it could take more or less time to deliver the Increment following high quality standards.

Factor 3: Business environment
Any events in the business environment (e.g. event for your company to showcase the product in three weeks)

What is the logic behind having Sprints?

=> Sprints enable predictability by ensuring inspection and adaptation of progress towards a Product Goal,

at least every calendar month

Are the durations of Sprints fixed?

=> Sprints must have fixed durations

can change (because of business events, etc.) but shouldn’t be changed frequently

When can a Sprint be canceled?

=> should only be canceled if the Sprint Goal becomes obsolete (veraltet, überholt)

Who has the authority to cancel a Sprint?

=> only the Product Owner

Since the PO is the one responsible for defining the strategy to deliver value.

Of course other stakeholders (incl. Developers or the Scrum Master) might influence the PO.

Name 4 Invalid Sprints.

Hardening (or Integration or Stabilization) Sprint
Sprint 0
Release Sprint
Design Sprint

What are practices to monitor **Sprint Progress**?

* Burn-Down-Chart * Burn-Up-Chart * Cumulative Flow Chart *=> BUT the Scrum Guide doesn’t mandate using any projective practices*

What is the **Development Work**?

=> is the work performed by the Developers to develop the Increment during the Sprints

What exactly do the **Developers** do during the **Sprint**?

=> Since the Team is cross-functional, they must be able to do all the work necessary to deliver Increments => Depending on the domain (Bereich), they will have different types of tasks

What do they talk about in **Daily Scrums**?

=> the Developers get together, to talk about their progress toward the Sprint Goal and to adapt the Sprint Backlog as needed. (Time the Developers invest to synchronize work)

When and where is the **Daily Scrum** held?

=> every working day at the same time and place, => to reduce complexity

What is the Scrum Masters part in the **Daily Scrum**?

=> does not participate * needs to ensure that the meeting takes place * helps the developers to keep it within the 15 minute time-box * makes sure it's positive and productive **Exception** in cases in which the Scrum Master or the Product Owner are actively working on items in the Sprint Backlog. In these cases, they participate as Developers.

What is the Product Owner's part in the **Daily Scrum**?

=> does not participate **Exception** in cases in which the Scrum Master or the Product Owner are actively working on items in the Sprint Backlog. In these cases, they participate as Developers.

What structure or techniques do they use in the **Daily Scrums**?

*=> They can select whatever structure and techniques they want* Most teams have each member to answer ***3 questions***, e.g. 1| What did I do yesterday that helped the team to meet the Sprint Goal? 2| What will I do today to help the team meet the Sprint Goal? 3| Do I See any impediments (Hindernisse) that prevents me or the team from meeting the Sprint Goal?

What is the Goal of the **Sprint Review**?

=> to ***inspect*** the Increment or any other outcome of the Sprint => and if needed ***adapt*** the Product Backlog or determine any other future adaptations

Who is attending The **Sprint Review**?

**=> *Ideally* users, customers and internal stakeholders** If customers and users can’t show up, the PO represents their interests. But it is essential for them to be there because if they inspect the Increment, they can give the Scrum Team valuable feedback

What happens before the **Sprint Review** starts?

=> It begins with the Developers getting ready for the event. => They need to check which Product Backlog Items are done, given the Definition of Done and prepare them to be presented during the Sprint Review.

Should the undone work be presented during the **Sprint Review**?

=> No Only the increment is presented during the Sprint Review and undone work must not be part of the Increment

What is the **Sprint Review** NOT?

**=> Not a demo meeting** *Team should NOT present something with slides, screenshots of the tools, etc.* => because to get transparency, you should allow the stakeholders to use the Increment whenever possible

What is the **Sprint Retrospective**?

=> is an opportunity for the Scrum team to reflect on their methods and teamwork to improve its effectiveness.

What are topics that can be discussed during a **Sprint Retrospective**? | Name 5.

* Interpersonal issues? * Product Quality issues? * DoD appropriate? * Productivity issues? * Process issues (unproductive Scrum events, Sprint length not being appropriate)

Who is attending the **Sprint Retrospective**?

=> the Scrum team

Who ensures that the **Sprint Retrospective** event is positive and productive?

=> the Scrum Master

During the Sprint Retrospective, the goal is to answer 3 questions. | Name the 3 questions.

* What went well during the sprint? * What didn’t go well? * How can we improve? The most impactful improvements may even be added to the Sprint Backlog for the next Sprint.