User:Jlaska/QA:SOP release retrospective

This SOP describes the best practices for running a productive release QA retrospective.

Background

A software retrospective is a process by which a team reviews successes and failures, makes recommendations and executes corrective action. A retrospective is an iterative process that works best when consistently applied to a project. The exact frequency and format will differ between projects and teams. This page documents the process used by Fedora QA.

[...] a retrospective is a meeting held by a project team at the end of a project or process (often after an iteration) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects. http://en.wikipedia.org/wiki/Retrospective#Software_development