article thumbnail

The Forgotten Scrum Event

Scrum.org

What are the 5 events in Scrum? Chances are that you said something like “Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and…. The Sprint is the most commonly overlooked event in Scrum. In fact, many people don’t even realize that it is an event in Scrum. Can you name them?

SCRUM 167
article thumbnail

To Fix Your OKRs – Go Back to First (Familiar) Principles

Scrum.org

Figuring out the right Cadence . It’s all about finding the “goldilocks” cadence that provides frequent enough transparency and the opportunity to inspect and adapt at the right level. There can be a different cadence for everyone involved in achieving an OKR as compared to the cadence involving all stakeholders interested in that OKR.

Cadence 197
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

Scrum Events. There are plenty of opportunities for stakeholders to interact responsibly with a Scrum Team. The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. Show, don’t tell. Daily Scrums.

article thumbnail

Comparing Nexus and SAFe - Similarities, Differences, potential synergies

Scrum.org

Empiricism via working integrated increments every Sprint - System Demo & Nexus Sprint Review meeting a common Definition of “Done”. The Nexus Sprint Review and the System Demo are similar events happening on a similar cadence - every several weeks (Sprint/Iteration). Nexus has Product Owner for the entire product.

Cadence 137
article thumbnail

A Review Of Scrum For Kanban Teams

Digite

In case you haven’t read Yuval’s post, basically, it presents a map of values and practices in Scrum to Kanban language, and encourages Kanban teams to approach Scrum from a practices point of view. This is probably the set of things that, regardless of the name, Scrum and Kanban teams will have the most in common.

article thumbnail

A Deeper Look: Top Changes in the New 2020 Scrum Guide for Agile Practitioners

MPUG

The new guide clearly informs that Sprint Reviews should not be considered “gates” for releasing value. As there can be multiple Increments, the sum of all these Increments are presented to the (key) stakeholder at the Sprint Review. Introduction of Cadence. The diamond shapes in the cadence stream denote the Sprint Reviews.

Cadence 116
article thumbnail

Improving SAFe Through Professional Scrum

Scrum.org

In real life, these Product Owners are typically accountable to the value delivered by these multiple teams and rely upon a lot of assistance from the Development Teams in order to deal with the challenge of scale. . SAFe has a cadence at the Team and Program levels. But we can't ignore the differences in lingo.

SCRUM 139