Launch and Post‐Launch: UAT, Security Testing, Performance Testing, Go Live, Rollback Criteria, and Support Mode
Anna Murray · 2015
Launch doesn't mean instant relief from stress. This chapter focuses on the launch and post-launch periods. The process of user acceptance testing (UAT) is explored in this chapter, along with how to manage UAT so it doesn't get out of control. Strategies are given such as planning for UAT ahead of time, instructions to the UAT team, and classifying UAT feedback. Conflict resolution, often necessary at the end of projects, is explored.End-of-project activates are set forth such as final launch criteria, load testing, performance testing, and security testing. A guest article by a certified cyber security expert is including with definitions of cyber security and its role in the software development lifecycle—from design, through implementation, testing, and maintenance. The chapter gives advice on defining acceptable risk. The project sign-off process is set forth as well as questions to answer to determine launch readiness. The possible need to rollback is discussed and criteria for rollback are given. Post-launch stress and problems are discussed such as change management, the challenges of operating in a live state, training, and when to assess success.