Scrum's Events

Basic

difficulty

Stage 2

Agile IQ® Level

Events

Practices

Scrum

Framework

Introduction

The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required.

Impacts of not using these events

Failure to run any of these events results in lost opportunities to inspect and adapt. Events are used in Scrum to create regularity and to minimise the need for meetings not defined in Scrum.

Transparency is reduced: The actual state of artefacts – the Product Backlog and the Sprint Backlog – becomes less clear.
Risk increases: How close are we to delivery? Are issues stalling us from achieving the Sprint Goal? Each day that passes without a Daily Scrum reduces our ability to adequately answer these questions.

Transparency of progress is reduced

The state of the Sprint's goal and progress toward it less clear. Does it truly reflect where delivery is at?

Delivery is at risk

If daily plans are not assessed, opportunities to adapt to change in the environment are lost.

Failure to adapt

Opportunities are lost to deliver smarter, faster, if not assessed on a daily basis.

Reducing complexity and variability

Optimally, all events are held at the same time and place to reduce complexity.

Scrum Facilitation Guides

The Facilitation Guides for Scrum’s 5 events, and Backlog Refinement, cover the essential working sessions to strengthen empiricism through regular and consistent inspection and adaptation.