Release Management Checklist and Steps - List
5.00/5.00 - (1 votes for this article, provide comments and help us improve if required.)
Release management checklists are required for ensuring the policies and processes used to release developed software are appropriate.
Release management.
What is a software release management checklist?
A release management checklist is required for ensuring the policies and processes used to release developed software via a release plan. Working with the development team/s a release manager ensures that the software being released is correct and will work first time. It is important that the release manager is involved from the offset to provide the necessary oversight required for a successful release.
| Folder/Task | Task | Done |
|---|---|---|
| Release strategy polices and standards. | ||
| Definition of release levels, major, minor, patch, service pack, general release etc. | ||
| Definition of release numbering and naming conventions etc. | ||
| Definition of release type, full replace, manual/automated push/pull etc. | ||
| Definition of expected release frequency. | ||
| Ensure it is defined where releases will be located/defined labelled etc. | ||
| Ensure Roles and responsibilities for the releases are clearly defined. | ||
| Prerequisites for a release. | ||
| Ensure version number defined. | ||
| Ensure a product plan has been created | ||
| Ensure a team is engaged to deliver the release. | ||
| Development considerations. | ||
| Debugging and testing code has been removed for final version. | ||
| Ensure all development/coding is completed and reviewed. | ||
| All unit test code has been updated/completed. | ||
| Ensure any development documentation has been updated. | ||
| Confirm the development team has signed-off the release. | ||
| Update any required version numbers. | ||
| Create any required installation and configuration scripts. | ||
| Create the release, msi zip files etc. | ||
| Development quality assurance. | ||
| Verify all source code meets coding standards. | ||
| Check that all defects on current defect list have been resolved. | ||
| If possible verify all unit tests run automatically on the current build. | ||
| Release management document quality assurance. | ||
| Verify that user documentation still matches current release. | ||
| Ensure any help files required are included/updated with the release. | ||
| Create a "ReadMe" text file with installation instructions. | ||
| Ensure Release Guide Notes define, if applicable, any "Known Issues". | ||
| Ensure any copyright, license type documents are included with the release if necessary. | ||
| Ensure the release guide contains the release number. | ||
| Ensure installation guide details any additional/amended pre-requisites required hardware and software. | ||
| Ensure release guide contains details of any changes to the database/forms. | ||
| Ensure installation guide details operations required pre and post release required for rollback. | ||
| Ensure Release Guide documents detail potential impact on disaster recovery procedures. | ||
| Ensure Release guide contains any details of any training which might be required post release. | ||
| Release management testing. | ||
| Confirm functional testing complete. | ||
| Verify that every test in the test script has completed. | ||
| If possible verify all system test scripts run automatically on the actual released software. | ||
| Perform all non-functional system tests manually and document results. | ||
| Verify installation by installing system on target machines as target install user. | ||
| Have someone not on the project team install and run your the install without assistance by following your installation directions. | ||
| If applicable, run as a fresh installation. | ||
| If applicable, run as an upgrade. | ||
| Confirm User acceptance/usability testing Complete. | ||
| Confirm performance/stress Testing complete. | ||
| Confirm software has been tested in all target type of environments. | ||
| Confirm integration testing has completed. | ||
| Confirm all testing has been signed off. | ||
| Does the release affect any disaster recovery plans? | ||
| Has the release been understood by all parties? | ||
| Confirm all parties have agreed the release can be implemented. | ||
| Release management media quality assurance. | ||
| Virus scan all release media. | ||
| Ensure the source code repository contains a final version of the release. | ||
| Confirm final freeze on list of files to be distributed. | ||
| If possible, synchronize date/time stamp on all release files. | ||
| Prepare final release. | ||
| Verify that all files are present for the release. | ||
| If on hardware (CD) etc confirm hardware is checked as not corrupt. | ||
| Create a backup of the build environment and place the development environment under strict change control. | ||
| Release management final quality assurance. | ||
| Smoke test/regression test final build. | ||
| Check User Manual has been updated. | ||
| Check System Test documents exist and are solid/completed. | ||
| Release notes must match what is being release. | ||
| Communicate release readiness. | ||
| Release management post release steps. | ||
| Perform a lessons learnt/post mortem for the release and feed any suggested improvements into next release. | ||
| Confirm there is adequate support from the development and test team as early releases are deployed. | ||
| Are there processes in place to monitor performance post the release? | ||
| Is a support handover document in place which accurately describes the functionality of the release? | ||
| Does the support handover document what changes will be made to the current environment with the release and the intended user base? | ||
| Does the support team agree the release will deliver the required functionality? | ||
| Does the support team agree post the release there can be equivalent availability, capacity, security, and continuity? | ||
| Does support agree the release will be usable by all potential users? | ||
| Does support agree the change will not impact their ability to meet the SLA? | ||
| Does the support team have the necessary skills to support the required release? | ||
| Will the user community need training and are materials available? |
Synonyms/tags: release management checklist, release checklist, software release process checklist
Want to know more? Then more information can be found about Release Management Checklist and Steps with the external resources from another site here.
Or, per your interest, look at other related links;
User acceptance checklist.
Technical specification checklist.
Software development checklist.
This list was published by Here There, Everywhere; and is a printable check-list; To print, hold down the key marked "ctrl", and whilst holding that down, press the "p" key.
This is a downloadable list, select here, if you would like to download the Release Management Checklist and Steps - List as an excel or .csv file. Or find the print function on your browser (top right, three dots, print) and print to a pdf printer if you would like to download as a pdf file, or print to a pdf file.
Suggest improvements, request additional items, report typos, errors or misspellings, ask us questions or just say hello via the comments here below, we are always pleased to hear from you..
Be a pioneer and write the first comment.
Note: Current average rating of 5.00 based on 1 reviews and ratings. (1-Low, 5-High)
Note: Comments and ratings help this site get better; if you see something missing, see something wrong, have a question, or want to suggest something to improve then comment below and join the dialogue;
« Back to main checklist
"I would like to create my own checklist"and look for the Depute application. You can set up you own personal lists or share your favourite lists, with our free application.