- Introduction
- Definition of Production Acceptance
- The Benefits of a Production Acceptance Process
- Implementing a Production Acceptance Process
- Full Deployment of a New Application
- Distinguishing New Applications from New Versions of Existing Applications
- Distinguishing Production Acceptance from Change Management
- Case Study: Assessing the Production Acceptance Process at Seven Diverse Companies
- Summary
- Test Your Understanding
- Suggested Further Readings
This chapter is from the book
This chapter is from the book
This chapter is from the book
Full Deployment of a New Application
By this point, the production acceptance process should be designed, approved, documented, tested, and implemented. So when does the new application become deployed? The answer is that the process of developing the process does not specifically include the deployment of a new application. When the production acceptance process is applied, it will include the use of a form such as the one previously described in Figure 9-1, which includes all of the activities leading up to the actual deployment. In other words, if all of the tasks outlined by the form in Figure 9-1 are completed on time for any new application, its successful deployment is all but guaranteed.
){kind=link}
One of the key aspects of this entire process is the involvement of the infrastructure group early on. The development manager who owns the new application should notify and involve the production acceptance process owner as soon as a new application is approved. This ensures infrastructure personnel and support staff are given adequate lead time to plan, coordinate, and implement the required resources and training prior to deployment. Just as important are the follow-up and lessons-learned portions of the process, which usually occurs two to three weeks after initial deployment.