Skip to main content

Are you doing release retrospectives?

Last post 05:58 am February 25, 2013 by Sanjay Saini
3 replies
02:43 am February 14, 2013

And if so, how are they conducted?


08:23 am February 15, 2013

What's a Release Retrospective? :-)

06:01 am February 22, 2013

Oh, sorry for not replying sooner. My inbox is a mess.
I know some organisations have these kind of retros. The idea is to evaluate an entire release (not just a sprint) which can span multiple sprints. Although not formally a part of scrum I think it can be good to take a step back and try to look at the big picture. Sprint retros can be pretty narrow in context. Some invite stakeholders, management etc. and evaluate the collaboration in the entire organisation. If anyone has these kinds of retros I'd like to hear your experience. How are they conducted, are they valuable etc.


05:58 am February 25, 2013

We did it once and it was done by each individual group separately i.e. scrum teams, scrum master, POs and Program management team. The each individual group's findings were available at a shared location for everyone

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

Please note that the first and last name from your 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. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, 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 may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.