Skip to main content

Due to the Russian invasion of Ukraine, we have paused all purchases and training in and from Russia.

To Retro or not to Retro

Last post 09:39 pm August 1, 2016 by Michael Kogan
4 replies
Anonymous
07:25 pm July 18, 2016

Hi all,

I was wondering about the following:

Lets say there is an issue. When does a Scrum Team decide to wait for and discus it in the Sprint Retrospective and when does it need to be addressed immediately?


09:31 pm July 18, 2016

Does the Development Team feel that the issue may affect their ability to achieve the sprint goal? If so, then it should be discussed immediately, and not have to wait for the Retrospective. (critical)

If the issue is non-critical, it is up to the team whether to address it before or at the Retrospective. An assessment of team capacity and progress towards the sprint goal are a couple weighing factors for making a decision to discuss now or wait until later.


Anonymous
04:14 am July 19, 2016

Thanx, sounds logical


08:36 pm August 1, 2016

Inspection and adaptation should occur as close as possible to the time and place of issue. This is as true in Scrum as it is in any other lean or agile way of working. Failure to do this incurs waste. There's nothing in Scrum which says remedial action for an issue must delayed until a formal event such as a Sprint Retrospective.


09:39 pm August 1, 2016

Hi Pablo,

let me ask you a rhetorical question: if there is an issue in your family, or in your car or in your gang, when should it be addressed? The answer, of course, is: when appropriate, taking into account the severity, the context, the settings, the people's traits and other factors.
Scrum retros are mandatory events because an improvement process is considered critical and they are an attempt to enforce it in the typically stressful environment where they may very easily be omitted. As Ian mentioned, there is no reason why issues cannot be handled early on.

Hope this helps,
Michael


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.