Project Implementation – Release Control
Project Implementation – Release Control (#50 in the Hut A Project Management Primer)
By Nick Jenkins
When you release a product ‘into the wild’ you will need to know what you released, to whom and when. This may seem trivial but you’ll want to keep track of things so you can make fixes and changes as the customer discovers problems (and they will!).
These are the things you typically need to track for each release :
- The version number or identifier of the release
- The date and time of the release
- The purpose of the release (maintenance, bug fix, testing etc)
- For each component within the release
- the name and version number of the component
- the date it was last modified
Here is an example :
Next in the Hut A Project Management Primer:
Project Implementation – Positive Perception
Previously in the Hut A Project Management Primer:
Project Implementation – Acceptance Testing
Nick Jenkins is an IT manager with 10 years experience in software development, project management and software testing. He’s worked in various fields of IT development in Australia, Britain and the USA and occasionally he learned something along the way. Now he lives on the banks of the Swan River in Perth, Western Australia, and he publishes the odd guide to help aspiring IT professionals. Nick’s website can be found at www.nickjenkins.net.
