---

Deployment management is the practice of moving new or changed service components into live environments.

Its purpose is to ensure that deployments are carried out in a controlled and effective manner.

Deployment management may involve deploying software, hardware, documentation, or other service components.

Deployments should be planned and coordinated to minimise disruption to services.

Deployment management works closely with release management and change enablement.

---

2. How This Applies to TakeCars (Car Rental Marketplace)

This practice explains how changes are physically or logically put into production, as distinct from approval and release communication.

a) What a “deployment” is at TakeCars

Deployments include:

• Pushing new code to production
• Enabling new pricing logic
• Activating new host rules
• Updating production configuration
• Publishing new operational documentation

A deployment is the act of putting components live.

---

b) Deployment vs release vs change (exam-critical clarity)

• Change enablement
  • Decides if/when a change is allowed
• Release management
  • Packages and prepares changes for use
• Deployment management
  • Moves components into the live environment

These are related but not the same.

---

c) Controlled deployments in TakeCars

Why control matters:

• Live bookings are always in progress
• Errors affect real trips immediately

Good deployment practices include:

• Deploying outside peak pickup times
• Feature toggles for gradual rollout
• Rollback capability
• Coordination with support

Poor deployments become incidents.

---

d) Minimising disruption

ITIL stresses minimising disruption, not eliminating change.

For TakeCars:

• Small, frequent deployments are safer than big ones
• Visibility to operations reduces surprises
• Coordination reduces support spikes

---

e) Exam-critical insight

If the exam asks:

“What is the purpose of deployment management?”

Correct logic:

• Move new or changed components into live use
• Do so in a controlled way
• Minimise service disruption

Answers suggesting deployment management approves changes or designs releases are incorrect.

---

3. Key Things to Read / Remember Right Before the Exam

Deployment management (high probability)

• A service management practice
• Deploys components into live environments
• Minimises disruption
• Works with change enablement and release management

---

Common exam traps

• Deployment management decides what to change → False
• Deployment management is the same as release management → False
• Deployments should be unplanned → False

---

One-line memory hook

Deployment management carefully moves changes into live use without disrupting services.

---