Remove Blog Remove Cadence Remove Closing Remove Development Team Review
article thumbnail

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

Scrum.org

In this blog I want to share some common collaboration problems and solutions I experimented with. 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.

article thumbnail

Improving SAFe Through Professional Scrum

Scrum.org

SAFe's approach to product ownership is that scale is achieved by splitting the product ownership role between Product Management, which is more like the classic Scrum Product Owner, and the Product Owner, which is indeed more like a proxy or technical product owner working more closely with teams. Well, let's unpack this.

SCRUM 137
Insiders

Sign Up for our Newsletter

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

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. And classic teams only get to that level of “working” pretty infrequently. Their REAL feedback loop takes weeks if not months to close. Can it also be a release cadence?

Cadence 134
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. And classic teams only get to that level of “working” pretty infrequently. Their REAL feedback loop takes weeks if not months to close. Can it also be a release cadence?

Cadence 127
article thumbnail

Improving SAFe thru Professional Scrum

Scrum.org

SAFe's approach to product ownership is that scale is achieved by splitting the product ownership role between Product Management, which is more like the classic Scrum Product Owner, and the Product Owner, which is indeed more like a proxy or technical product owner working more closely with teams. Well, let's unpack this.

SCRUM 112
article thumbnail

Agile Communications Plans

Leading Answers

Instead, the team regularly surfaces from work to show where they are with progress and discuss what should come next. It is this predictable cadence of show-and-tell sessions that creates the dolphins-versus-submarines comparison.  Frequent demos mean the project never disappears for long.

Agile 135
article thumbnail

How To Implement Lean Portfolio Management?

Agilemania

Your team is granted funds that are decided by strategic needs, and they make sure your goals align with those needs. In order to connect strategy to execution The leadership team evaluates these targets on a regular basis. “Go see” the incremental value demonstrated in team demos and validate the value hypotheses.

Lean 98