Remove Cadence Remove Development Team Review Remove Workshop
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
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
Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

How I transformed “multiple Scrum teams” into “multiple team Scrum”

Scrum.org

I advise to start finding one person to be the single Product Owner for all teams. The other “fake PO’s” should be moved inside the development teams as subject matter experts so they can provide detailed requirements. The Product Owner should develop an inspiring vision and a plan to make it happen.

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. In order to scale, the Product Owner needs to have the courage to let the Development Team run some of those experiments on their own. Can it also be 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. In order to scale, the Product Owner needs to have the courage to let the Development Team run some of those experiments on their own. Can it also be 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

Creating a Risk-Adjusted Backlog

Leading Answers

Assessing the chances of loss or gain occur throughout all forms of business and relies on taking an economic view of decision making. Instead, I believe many projects leave a lot of development team sourced opportunities unactioned.   Team Activities and Tools. Risks Actions in the Backlog.

Risk 145