Deployment phase

Purpose of Deployment Phase

The deployment phase is the final phase of the software development life cycle (SDLC) and puts the product into production. After the project team tests the product and the product passes each testing phase, the product is ready to go live. This means that the product is ready to be used in a real environment by all end users of the product.

There are various phases of the deployment process the project team must follow to ensure the code and technology deploy appropriately. The phases include deployment preparation and procedures, product deployment, transferring ownership of the product, and closing the deployment phase. Let’s learn about each phase in more detail.

 TEST

What is the purpose of the deployment phase in SDLC?

To put the product into production.

What is the purpose of the closing phase of deployment?

Feedback from the customer.

What happens during product deployment?

The project team suspends all tests until further feedback from the business.

What happens during the transfer ownership phase of deployment?

The project team transfers operations for the product to the business who now is responsible for maintenance.

What are the steps within the deployment phase in SDLC?

Preparation, product deployment, ownership transfer and close deployment

Preparation and Procedures

In the preparation and procedures phase, the project team installs the software and conducts another test to ensure successful installation. Once the installation is complete, the project team creates operating procedures, which include instructions for how the software should work in the information technology environment. If there are issues with system functionality, the operating instructions also provide a mitigation plan to help the end user repair the issue.

Product Deployment

Under the product deployment phase, the project team implements the programming and coding to each system location. For example, say a company has two regional worksites in Florida and Georgia and over 5,000 computer systems. The deployment phase includes pushing the program and coding to each regional site and each computer system.

Ownership Transfer

Once the program and code deploy to each system, the project team’s work is complete. They can transfer ownership to the business who is now responsible for maintaining the system functionality. The project team transfers ownership of the program and code, along with all operating procedures, to the business.

Close Deployment

After the project team deploys the product and transfers ownership of the product to the business, it is time to document the results and close the project. The project team completes the project plan and updates the completion date. During the closing phase, the project team also gathers feedback from the customer, and the team reviews the feedback to improve processes for the next project.

Summary

The deployment phase is the final step in the software development life cycle and delivers the final product to the customer in a live production environment. After the product deploys, the product is ready for customers to use.

How to categorize SDLC phases with Development - Loginworks

The phases of deployment include:

  1. Preparation and procedures: the project team installs the software and conducts another test to ensure successful installation.
  2. Product deployment: the project team implements the programming and coding to each system location.
  3. Ownership transfer: the project team gives ownership over to the business, who is now responsible for maintaining the system functionality.
  4. Closing deployment: the project team documents the results, completes the project plan, updates the completion date, and gathers feedback from the customer.

After the product is released into the production environment, the customer uses the operating procedures as a guide to operating the new software and to troubleshoot any issues that may arise. Meanwhile, the project team completes final requirements and gathers customer feedback on the project team’s performance throughout the SDLC.

The feedback is captured in an after-action review. The review helps the project team determine whether the team completed each requirement, on schedule, with an accurate and fully functioning product. The project team can also use feedback to help determine if any process steps should have been completed differently according to the customer.