Bob Aiello - November 2002

The Release management process is often an overlooked step in the Software Development LifeCycle. Usually, this “drudgery” is delegated to the most junior member of the team. With little or no background the release manager can make mistakes that can cost the team a great deal of time and effort. Putting out bad releases can ultimately cost the company a great deal of money and seriously impact the bottom line. How can we most effectively define the release management function to demonstrate it’s value and develop a process that works for the company, the development team and the individual assigned this important responsibility?