Working in an Agile environment means that we have many releases throughout the year. Despite our sprints being of the same length, there generally seems to be releases where there is a lot to of functionality, and some where not so many changes are going in. Releases tend to be a team effort here, but the overall management of the process falls to me. But no matter how regularly we deploy, or how big an impact the release will be, it always makes common sense to be diligent when preparing for a release. The last thing I want to be doing on a Saturday is trying to fix an issue that could and should have been caught in regression. So how do we help ourselves?