Scrum Events

 Is the second to last event of the Sprint

This event concludes the Sprint

 Occurs in the same place at the same time every day

Each of these can be considered a short project

Addresses the topic: What can be Done this Sprint?

Timeboxed to 4 hours for a one-month Sprint

Is a working session and the Scrum Team should avoid limiting it to a presentation

A new one starts immediately after the conclusion of the previous one

The purpose is to inspect the outcome of the Sprint and determine future adaptations

 Timeboxed to 8 hours for a one-month Sprint

Should never be considered a gate to releasing value

 Fixed length events of one month or less to create consistency

Focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work

What went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved

The Scrum Team and stakeholders review what was accomplished, what has changed, and collaborate on what to do next

This event is for the Developers of the Scrum Team

 Addresses the topic: Why is this Sprint valuable?

The purpose of this event is to turn ideas into value

 Discuss with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint

Inspect how the last Sprint went with regards to individuals, interactions, processes,tools, and their DoD

The purpose is to plan ways to increase quality and effectiveness

For each selected PBI, the Developers plan the work necessary to create an Increment that meets the Definition of Done