This article has multiple issues. Please help talk page. (Learn how and when to remove these template messages)( or discuss these issues on the Learn how and when to remove this template message)
IT infrastructure deployment typically involves defining the sequence of operations or steps, often referred to as a deployment plan, that must be carried to deliver changes into a target system environment. The individual operations within a deployment plan can be executed manually or automatically. Deployment plans are usually well defined and approved prior to the deployment date. In situations where there is a high potential risk of failure in the target system environment, deployment plans may rehearsed to ensure there are no issues during actual deployment. Structured repeatable deployments are also prime candidates for automation which drives quality and efficiency.
The objective of Deployment Planning is to ensure that changes deployed into a target system environment are executed in a structure and repeatable manner in order to reduce the risk of failure. The purpose of release and deployment planning is to:
A deployment template is an unbound deployment plan which defines the steps of execution but not the profiles and systems. Deployment templates are patterns from which deployment plans can be created.
Typical information captured for each step in the deployment plan is:
Manage research, learning and skills at defaultlogic.com. Create an account using LinkedIn to manage and organize your omni-channel knowledge. defaultlogic.com is like a shopping cart for information -- helping you to save, discuss and share.