A typical deployment process includes:
· Finalize the release notes
· Submit a change request to the CCB to change the production baseline with the release package.
· Collect supporting documents that indicate the readiness of the release (test reports, release notes, installation plan, backout and recovery plan, etc.)
· Review and authorize the release package
· Review the change request and all supporting documents
· Determine disposition of release package (approve, reject, pending, etc.)
· Address concerns
· If approved, communicate pending release package has been tested with release dates to stakeholders and support staff.
· Install release into production. Production may be media or production server(s) or client(s).
· Validate release package in production.
· If media, this should include testing the installation process from media to production server and/or client as well as testing functionality once installed.If production server or client, test functionality.
· Communicate that release is in production to all customers, stakeholders, and support staff
When implementing CM processes, build, package, and deploy can be a good place to start. It is usually one of the more visible areas where a CM’er can show value. It is not important to debate the name of the processes involved in this part of the lifecycle. If there are names that the project teams understands which represent the building, packaging, and deploying of deliverables (a.k.a., release package) into production, consider using them. The easier recognition may improve adoption. If there is no set process, consider documenting the current process and sharing it with the team. Once a process is defined, it also becomes a good basis for suggesting improvements. Ultimately, a CM’er must show (added) value and these processes are a good place to start.
1. “Software Configuration Management Implementation Roadmap” by Mario E. Moreira, 2004, John Wiley & Sons, Ltd Publishing. Specifically the following sections:
2. Chapter 4, “6.6. Develop an SCM Build Process”
3. Chapter 4, “6.7. Develop an SCM Release Process”