Release retrospective Presentation subtitle is Open Sans Regular 14pt, one line maximum 00 Month 0000 | Firstname Lastname
Release retrospective vs Sprint retrospective The Release and Sprint retrospectives have many similarities including techniques and the ultimate goal of continuous improvement which is so important to Agile. However there are some differences …
Release retrospective vs Sprint retrospective Focus on the entire release (multiple sprints) with goal to improve next release Focus on current sprint with goal to improve future sprints
Release retrospective vs Sprint retrospective Emphasis on risk ID specifically with respect to strategic objectives and product quality (refer to slide on inspection points) Emphasis on process improvements
Release retrospective vs Sprint retrospective More formal, greater prep required Somewhat informal and casual, less prep required
Release retrospective vs Sprint retrospective Fact and data driven Emotional/feeling points may be addressed
Release retrospective vs Sprint retrospective Broader participation - team, management, & stakeholders Limited participation - team only
Release retrospective vs Sprint retrospective Duration – typically, two hours depending on release length, format, and agenda Duration – typically, one hour
Some common inspection points for release retro Product quality Current status of the projects Number of escaped defects Planned features versus delivered features Whether the features delivered were in order of priority The number of features developed that were actually accepted The number of features delivered that are actually used by the customer The number of issues reported by the customer and the length of time we took to fix those issues Whether the release date was extended and, if so, why Whether we delivered all the scope planned for the release The number of defects getting generated on previous enhancements Whether we are taking interim customer feedback New technology initiatives Infrastructure issues causing release delays Performance improvement initiatives Any new tools to be introduced The optimization that can be done at various levels How we measured the data and scope of improvement What strategies were highly effective Etc. Source: https://www.scrumalliance.org/community/articles/2014/september/the-significance-of-release-retrospectives
Overview and techniques for retrospectives For a general overview and some common techniques that are useful in running scrum retrospectives, please refer to: http://pdn.pega.com/documents/scrum-basics-retrospectives