Remove Cadence Remove Development Team Review Remove Events
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 194
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 218
Insiders

Sign Up for our Newsletter

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

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 172
article thumbnail

The Sprint Increment Is Dead

Scrum.org

These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. The Sprint-level events are still as valuable as ever for inspecting and adapting the Product and the Process. A lot of people see the Scrum Sprint as mainly a release cadence.

Cadence 156
article thumbnail

The Increment Is Dead

Scrum.org

These are nice levels of transparency that are much better than just reviewing documentation of course, but they leave a lot to be desired. The Sprint-level events are still as valuable as ever for inspecting and adapting the Product and the Process. A lot of people see the Scrum Sprint as mainly a release cadence.

Cadence 150
article thumbnail

Improving SAFe thru 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 123
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.