Getting to the Root of Software Delivery Issues
Effective Release Management
Summary
Organisations put a lot of time and money into releasing new versions of software but often don't apply the same level of focus to assessing whether the release was a success or not.
The attached document reviews what is currently the norm in this area and goes on to outline the process we generally use at Amadori Limited when asked to assess a release of software
We describe a process which
- Explicitly links the value of a release to the value that its contents will provide to the organization
- Values the prevention of regression and a smooth delivery process as highly as the delivery of change
- Places the needs of end users at the centre of the measurement process.
It will also allow releases across an organisation to be compared and measured in an objective and consistent fashion
The document includes a worked example showing in detail how the reporting process works in practice and a survey template which can be used to elicit information about a release from end users in a structured fashion. Both can easily be adapted to fit the details of your specific projects and releases
Hopefully we’ve designed this document to be as clear as possible, but if you have any questions about it, please don’t hesitate to get in touch.
Use the buttons on the right to download
- a copy of the document which explains our process in detail
- a template which can be used as a basis for extracting information about a release from end users
- a copy of the spreadsheet which was used to generate the worked example in the process document which you can use the same style of report against your own releases
Feel free to tailor the templates to your own specific needs. If you need any assistance in doing so, please get in touch
