# Scrum Events

## About

All the 4 scrum events MUST be executed:

* Sprint Planning
* Daily Scrum
* Sprint Review
* Sprint Retrospective

They are key to create regularity and minimize the need for meetings not defined in Scrum.

To keep the Scrum Team focused, all the events are time-boxed, and the Scrum Guide prescribes a maximum duration for each one of them.

The team must define their lengths before starting it, which means that they MUST be defined before the Sprint Planning meeting, and it CANNOT be modified.

These events are a formal opportunity to inspect and adapt something, but it does not mean that meetings themselves are formal.

## Sprint ⭐

*"It is the Heart of Scrum."*

<mark style="background-color:yellow;">Time-boxed to, at most, 1 month</mark>, and MUST have fixed duration. They CAN change, but not frequently.

* Although, it can be short enough to handle business risks, or to synchronize with other business events. <mark style="background-color:yellow;">The Sprints help the Scrum Team to control Risks</mark>.

During the Sprint:

* <mark style="background-color:yellow;">No changes are made that would endanger the Sprint Goal.</mark>
* Quality Goals do not decrease.
* The Product Backlog is refined as needed.
* The Scope may be clarified and re-negotiated with the PO as more is learned.

<mark style="background-color:yellow;">A Sprint is over only when the time-box elapses, the exception is when the Sprint is canceled.</mark>

### Sprint Outcomes

* <mark style="background-color:yellow;">A Done Increment.</mark>
* Some done features.
* A part of the software that is available to end-users.

### Sprint Cancelling

<mark style="background-color:yellow;">Only the PO has the authority to cancel a Sprint.</mark>

* If part of the work is usable, it is considered Done.
* Done backlog items are reviewed.
* All incomplete backlog items are re-estimeted and put back in the Product Backlog.

### Sprint Monitoring

Burn-Up, Burn-Down or Cumulative Flow could be used for the Sprint monitoring.

## Sprint Planning ⭐

This event initiates the Sprint, by <mark style="background-color:yellow;">laying out the work to performed for the Sprint</mark>.

When the Scrum Team defines the goal of what to build and the flexible plan to guide achieving it.

<mark style="background-color:yellow;">The Plan is not fully formulated in the Sprint Planning, it can change.</mark>

The Sprint Backlog is the OUTPUT of a Sprint Planning.

**For the PO, planning efforts start even before Sprint Planning.**

* The must a set of Product Backlog Items,
* And their mapping to the Product Goal.

### The Input of Sprint Planning

* Projected capacity of the Developers during the Sprint.
* The Definition of Done.
* The Product Backlog.
* Past performance of the Developers.

### Who participates in the Sprint Planning?

<mark style="background-color:yellow;">The Scrum Team, but they may invite others to attend for advice like</mark>:

* An invited specialist.

### How do we execute this Sprint Planning?

The event has 3 topics to be addressed.

* <mark style="background-color:yellow;">Why is this Sprint valuable?</mark> (Craft the Sprint Goal)
  * It begins with the PO discussing the opportunities for increasing the product's value and utility and how the current Sprint can address it.
  * As a consequence <mark style="background-color:yellow;">the whole Scrum Team defines a Goal</mark>.
* <mark style="background-color:yellow;">What can be done in this Sprint?</mark> (Select the Backlog items)
  * For this purpose, <mark style="background-color:yellow;">the Developers select items from the Backlog</mark> through discussion with the PO.
  * Another factor that should be considered, <mark style="background-color:yellow;">is the Definition of Done</mark>, because the more stringent it is, the longer it might take to get Done with each Backlog item.
* <mark style="background-color:yellow;">How will the chosen work get done?</mark> (Craft the Sprint Plan)
  * The developers might use information, such as the <mark style="background-color:yellow;">upcoming capacity</mark> - which is about how many hours available the Developers have for this Sprint.
    * For instance, will anybody be out of the office during the Sprint?
    * Like vacations.
  * Further the Developers could also <mark style="background-color:yellow;">consider past performance</mark> as a reference.
    * Like seeing how many points were burned in past Sprints.

Since the developers are the ones to turn Backlog items into Increments of Value, they have the final word.

<mark style="background-color:yellow;">Most Scrum teams, decompose the Backlog items into technical tasks, which are smaller chunks of work often to units of one day or less.</mark>

## The Development work & Daily Scrums ⭐

### The Development Work

*Depending on the area of work, the pipeline will be different, since there will be different tasks.*

<figure><img src="https://3254186584-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA9AaxvoNFpTEwZ12nTvp%2Fuploads%2FKjL0QLeDvGrSuURd8LVS%2Fdevelopment-work.png?alt=media&#x26;token=57c35758-bc5c-4f85-b12f-e59a931619a6" alt=""><figcaption></figcaption></figure>

Usually done by using Scrum Boards, to enable:

* Collaboration,
* Communication,
* Transparency.

Important factors for self-management.

### Daily Scrums

{% embed url="<https://medium.com/@mperkusich/a-complete-guide-for-conducting-effective-daily-scrums-a481c853eed0>" %}

<mark style="background-color:yellow;">Is a meeting that occurs DAILY, at the same time and place.</mark>

<mark style="background-color:yellow;">Time-boxed to 15min.</mark>

<mark style="background-color:yellow;">The Scrum Master only needs to ensure that the meeting takes place, and is within 15min long</mark>. The PO usually does not participate.

<mark style="background-color:yellow;">Just the Developers MUST attend</mark>. Scrum does not forbid others from attending the Daily Scrum, but only the Developers can participate.

Each member answer to usually three questions:

* What did I do yesterday that helped the team to meet the Sprint Goal?
* What will I do today to help the team meet the Sprint Goal?
* Do I see any Impediments that prevents me or the team from meeting the Sprint Goal?

But these are not fixed, the developers can do different. The important thing is that the meeting:

* <mark style="background-color:yellow;">Focuses on assessing the team's progress toward the Sprint Goal</mark>, and
* <mark style="background-color:yellow;">Produces an actionable plan for the next day of work.</mark>

<mark style="background-color:yellow;">NOT a technical meeting.</mark>

## Sprint Review ⭐

Held at the END of each Sprint.\ <mark style="background-color:yellow;">Time-boxed up to 4h.</mark>

Its Goal is to:

* <mark style="background-color:yellow;">Inspect the Increment or any other outcome of the Sprint and</mark>
* <mark style="background-color:yellow;">If needed, adapt the Product Backlog or determine any other future adaptations.</mark>
* <mark style="background-color:yellow;">Have transparency and collaboration between Scrum Team and Stakeholders.</mark>
  * <mark style="background-color:yellow;">Have the Stakeholder be able to USE the Increment.</mark>

Who SHOULD participate:

* <mark style="background-color:yellow;">Users or Customers,</mark>
* <mark style="background-color:yellow;">Internal Stakeholders,</mark>
* <mark style="background-color:yellow;">Developers,</mark>
* <mark style="background-color:yellow;">The Scrum Master,</mark>
* <mark style="background-color:yellow;">PO</mark>

<mark style="background-color:yellow;">UNDONE work should NOT be presented in the Sprint Review. Sprint Review is NOT a Demo meeting.</mark>

* You must NOT present slides,
* screenshots,
* or similar

<figure><img src="https://3254186584-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA9AaxvoNFpTEwZ12nTvp%2Fuploads%2FXZGU9fM0kQ2mtFX2fwz8%2Fsprint-review.png?alt=media&#x26;token=bb84e073-f52f-4f7d-87f9-70d1b9dd3057" alt=""><figcaption></figcaption></figure>

## Sprint Retrospective ⭐

It occurs after the Sprint Review.\ <mark style="background-color:yellow;">Time-boxed to up to 3h.</mark>

Is an opportunity for the Scrum Team to reflect on their methods and teamwork.\
It is about to make teams better and continuously improving.

The Scrum Master ensures that the event is positive and productive.

<mark style="background-color:yellow;">The hole Scrum Team SHOULD participate.</mark>

* Only the Scrum Team participates.

#### Examples of topics

* Interpersonal issues?
* Product quality issues?
* Definition of Done appropriate?
* Productivity issues?
* Process issues?

Usually have theses questions:

* What went well during the Sprint?
* What didn't go well?
* How can we improve?

<figure><img src="https://3254186584-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA9AaxvoNFpTEwZ12nTvp%2Fuploads%2F6GJBsY2vfTOkGt2jWSJg%2Fsprint-review-topics.png?alt=media&#x26;token=33a2382d-69c6-49d2-9cc3-5ed825a2a9b5" alt=""><figcaption></figcaption></figure>