To most IT departments, the answer to the question “Do we need a formal release management process?” probably seems obvious: a resounding “Yes!” However, the answer may not be as simple as it seems. For small enterprises in particular, deciding when to start implementing a more rigorous release management process is a tough call.

Understanding Release Management

Face it: all applications eventually require changes. Business requirements change, technology advances, and end user enhancements become a must. Release management is the process of putting code into production. Note that there are relative approaches to release management: quarterly releases, functional releases, or on demand.

The process varies between departments and can consist of any of the following:

· Release Planning.

· Code the change using some form of version control.

· Formal unit testing.