The Continuous Delivery Workshop

Report

The Continuous Delivery Workshop offers you and your team a way to look for opportunities in their development process. In 90 minutes you'll map out the current development process starting when you start working on an item until you've released it in production. Looking for opportunities to release your Product Increments faster.

When to use The Continuous Delivery Workshop?

As a Scrum team member, you'll notice that there is not a real strategy when it comes to releasing fast.

Some of the signs you can look for are:

  • You release quarterly or yearly.

  • You batch all the work in one release, your release notes are pages upon pages.

  • Everyone clears their schedule when a release is coming.

  • It takes a long time for bugs to be resolved.

  • When you don't create a Product Increment every sprint.

How does The Continuous Delivery Workshop work?

Before running the workshop it's best to gather the following data:

  • Cycle time

  • Lead time

  • Definition of Done

  • The amount of incidents after releases

Development Timeline

The workshops starts with building the current timeline of the development process. Starting when we first start working on an item and finishing when it is released in production.

When the timeline is build we let the participants vote on what is the biggest bottleneck when it comes down to the speed of delivery.

Lighning demo's

We let the participants scour the internet to find ideas of what other are doing.

They present their ideas to the group.

Afterwards people get to vote on the best ideas so we get a top 5.

Effort/Impact

We take the ideas from the lightning demo's and plot them on the effort impact scale. Looking for ideas that are high impact we can act upon.

Actionable items

We take the items that were prioritized in the Effort/Impact exercise and create an action plan.

Ideas that are low effort, high impact are things we should add to our next sprint.

Ideas that are high effort, high impact are things we should add to the product backlog.

The rest of the items we can keep in mind or throw away.

Categories

Jelmar Van Aert image
Jelmar Van Aert
Scrum Master@Spilberg
Jelmar is a passionate Scrum Master focussing on team collaboration. He helps teams get things done!
Share your comment with the Miroverse community.

Similar templates