YDS: Who is Responsible for Release Planning on a Scrum Team?

(United States)

March 10, 2021

On today’s episode of YOUR DAILY SCRUM: Who is responsible for release planning on a Scrum Team? Today's question is about release planning on a Scrum Team. When it comes to deciding when to release, the Product Owner has a lot of input. But when it comes to how we release or what is released, the Developer has a say. From an efficiency perspective, even the Scrum Master could have an opinion. Listen in to see how Todd and Ryan sort out release planning on a Scrum Team.

Ryan Ripley and Todd Miller are the author of Fixing Your Scrum: Practical Solutions to Common Scrum Problems. They are the co-founders of Agile for Humans, the premiere Scrum and Kanban training organization.

What did you think about this post?

Share with your network

Comments (2)

Constantin von Zitzewitz

10:19 am March 11, 2021

The notion of the Product Backlog reflecting the Release Plan seems helpful to me. This is where everything culminates and is made transparent. The sorting by the PO, estimations of the developers and other data. So maybe also ask "What is responsible for Release Planning in a Scrum Team"? meaning the PB as Scrum Artifact plays a major role in release planning.

Horsey McHorseface

12:19 pm March 11, 2021

my org... Product owner (me) works with stakeholders to establish business perception of when features are needed. PO communicates desired release dates to scrum team and UAT team. We negotiate. PO strives to be receptive to delivery teams and be flexible/adaptive on dates. PO often bulldozed by leadership then PO has to be firm with delivery teams and try to keep desired dates. Invariably, in a rush to hit release dates we create technical debt with design, rush testing, rubber-stamp sign offs, and have bugs to resolve later... Later seldom comes.