Remove Agile Remove Cadence Remove Technical Review
article thumbnail

Everything You Need to Know About Release Managers

Rebel’s Guide to PM

The release manager at my last job worked closely with the development team to review what code changes would be coming. Once everything looks good from a technical standpoint, the release manager could start working on preparing communications about the upcoming software change. And then the cycle begins again!

article thumbnail

How a Consumer Services Company Embraced Professional Scrum to Fuel Growth

Scrum.org

Breaking the Tech Barrier: Implementing Scrum in Both Technical and Non-Technical Teams to Drive Measurable Business Outcomes Overview A fast-growing consumer services company delivering curated experiences to thousands of customers each week underwent a transformation in its approach to product development and team collaboration.

Insiders

Sign Up for our Newsletter

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

article thumbnail

How to make value flow without interruptions in SAFe

Scrum.org

In 2022, Andrew Sales ( Chief Methodologist and SAFe Fellow at Scaled Agile, Inc.) 4 Get fast feedback We have technical feedback (building the thing right) and customer feedback (building the right thing). Broken feedback loops will disrupt the system's flow and create rework and technical debt. You can find the talk here.

Cadence 195
article thumbnail

Product Operating Models and Shared Services / Business Operations Teams

Scrum.org

While developed in the context of Technology Operations, the principles apply to any sort of operational work: Understand how work Flows through development to operations. Again, all these principles were created in technical operations but can map nicely to business operations. in the form of PBIs/Features)?

article thumbnail

The Kanban Practice That Equips Teams For Self-Management

Scrum.org

The concept of self-managing teams is not just a characteristic of Scrum; it is one of the foundational principles of the Agile Manifesto, where the term “self-organizing teams” is used (note that discussing similarities and differences between self-organising and self-managing is an unnecessary detour in the context of this article).

article thumbnail

When To Use Scrum?

Scrum.org

Frequent delivery – Most enterprises are not configured to interact with end users in short cycles and are not technically capable of frequent delivery. But Scrum requires that the team is capable of taking new functionality into the hands of end users on a frequent cadence — in cycles not longer than one month, often much shorter.

SCRUM 116
article thumbnail

Agile Still Works

Scrum.org

Technology alone won’t solve the problem. Agile has been around for a while now, but many firms still see agility as a software development solution. It’s no secret that agile software teams see all sorts of performance gains. . Agile frameworks help us do that. Agile frameworks don’t fix your problems.

Agile 202