Skip to main content

Scrum Kanban Guide / Retrospective event

Last post 03:00 pm August 13, 2018 by Ian Mitchell
5 replies
09:05 am August 13, 2018

Hi everyone, 

This is from Scrum Kanban Guide (about retrospective)

Flow-Based Sprint Retrospectives A flow-based Sprint Retrospective adds the inspection of flow metrics and analytics to help determine what improvements the Scrum Team can make to its processes, including the Sprint Retrospective itself. The Scrum Team using Kanban also inspects and adapts the definition of “Workflow” to optimize the flow in the next Sprint. Using a cumulative flow diagram to visualize a Scrum Team’s Work in Progress, average approximate Cycle Time and average Throughput may be valuable. The Scrum Guide dictates that the Sprint Retrospective take place after the Sprint Review and before the next Sprint Planning. This does not change when using Kanban. However, flow-based retrospective opportunities need not coincide within the boundaries of a Sprint. They can occur "just in time”. Correspondingly, changes to a team’s definition of “Workflow” may happen at any time, however, as these changes will have a material impact on how the Scrum Team performs, changes made during the regular cadence provided by the Sprint Retrospective event will reduce complexity and improve transparency.

Maybe stupid question from my side and really apologies, but anyway, does it mean that retrospective event is not mandatory in Scrum Kanban?  


10:35 am August 13, 2018

The retrospective event is mandatory. However, it does not have to occur on a regular cadence. In traditional Scrum, the retrospective is held between Sprint Review and Sprint Planning. However, in Kanban, you can hold a retrospective event whenever it is necessary.

Not holding retrospectives at all would violate the principles of both Scrum (both inspection and adaptation) as well as Lean (eliminate waste, amplify learning, empower the team).


12:27 pm August 13, 2018

The Kanban Guide for Scrum Teams 

This guide is not meant to replace or discount any part of The Scrum Guide. It is designed to enhance and expand the practices of the Scrum framework. This guide assumes the reader is operating a process using the Scrum framework. Therefore, The Scrum Guide applies in its entirety.

 

The Sprint Retrospective take place after the Sprint Review and before the next Sprint Planning.

This DOES NOT change when using Kanban.

However, flow-based retrospective opportunities need not coincide within the boundaries of a Sprint.

Sprint Retrospective: is one of the mandatory events of Scrum.

retrospective opportunities: means the any activities to inspect the flow defined by the Scrum Team.

 

 

 

 


12:34 pm August 13, 2018

Keep in mind, 

Scrum with Kanban DOES NOT change Scrum, it adds to it with a set of great PRACTICES that make work more visible.

 


02:50 pm August 13, 2018

Ching-Pei, Thomas, thanks lor for your answers. I guess I've understood. At least I see this on real exam :) 


03:00 pm August 13, 2018

Regardless of whether a Kanban is being implemented or not, a Scrum Team ought to look for opportunities to inspect-and-adapt throughout a Sprint. Inspection and adaptation is not constrained to formal events and ought to be as timely as possible in order to reduce waste.

Kanban does not change this thinking, but it does introduce a new perspective on why “just-in-time” process control is advantageous, most notably with regard to improving value and flow.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.