article thumbnail

Everything You Need to Know About Release Managers

Rebel’s Guide to PM

They work with development teams to track progress and identify potential risks, as well as liaise with other departments such as QA, ops teams, service management, and support. The release manager at my last job worked closely with the development team to review what code changes would be coming.

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.

Insiders

Sign Up for our Newsletter

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

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+ is comprised of several Nexus.

Cadence 137
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
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 113
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