{"id":204,"date":"2026-01-08T11:46:03","date_gmt":"2026-01-08T08:46:03","guid":{"rendered":"https:\/\/ruck.nz\/?p=204"},"modified":"2026-01-08T11:46:10","modified_gmt":"2026-01-08T08:46:10","slug":"10-3-deployment-management","status":"publish","type":"post","link":"https:\/\/ruck.nz\/?p=204","title":{"rendered":"10.3. Deployment management"},"content":{"rendered":"\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<p class=\"wp-block-paragraph\">Deployment management is the practice of moving new or changed service components into live environments.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its purpose is to ensure that deployments are carried out in a controlled and effective manner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deployment management may involve deploying software, hardware, documentation, or other service components.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deployments should be planned and coordinated to minimise disruption to services.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Deployment management works closely with release management and change enablement.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">2. How This Applies to <strong>TakeCars<\/strong> (Car Rental Marketplace)<\/h1>\n\n\n\n<p class=\"wp-block-paragraph\">This practice explains <strong>how changes are physically or logically put into production<\/strong>, as distinct from approval and release communication.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">a) What a \u201cdeployment\u201d is at TakeCars<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Deployments include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Pushing new code to production<\/li>\n\n\n\n<li>Enabling new pricing logic<\/li>\n\n\n\n<li>Activating new host rules<\/li>\n\n\n\n<li>Updating production configuration<\/li>\n\n\n\n<li>Publishing new operational documentation<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A deployment is the <strong>act of putting components live<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">b) Deployment vs release vs change (exam-critical clarity)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Change enablement<\/strong>\n<ul class=\"wp-block-list\">\n<li>Decides if\/when a change is allowed<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Release management<\/strong>\n<ul class=\"wp-block-list\">\n<li>Packages and prepares changes for use<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Deployment management<\/strong>\n<ul class=\"wp-block-list\">\n<li>Moves components into the live environment<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These are related but not the same.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">c) Controlled deployments in TakeCars<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why control matters:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Live bookings are always in progress<\/li>\n\n\n\n<li>Errors affect real trips immediately<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Good deployment practices include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deploying outside peak pickup times<\/li>\n\n\n\n<li>Feature toggles for gradual rollout<\/li>\n\n\n\n<li>Rollback capability<\/li>\n\n\n\n<li>Coordination with support<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Poor deployments become incidents.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">d) Minimising disruption<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">ITIL stresses minimising disruption, not eliminating change.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For TakeCars:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Small, frequent deployments are safer than big ones<\/li>\n\n\n\n<li>Visibility to operations reduces surprises<\/li>\n\n\n\n<li>Coordination reduces support spikes<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">e) Exam-critical insight<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">If the exam asks:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">\u201cWhat is the purpose of deployment management?\u201d<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Correct logic:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Move new or changed components into live use<\/li>\n\n\n\n<li>Do so in a controlled way<\/li>\n\n\n\n<li>Minimise service disruption<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Answers suggesting deployment management approves changes or designs releases are incorrect.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h1 class=\"wp-block-heading\">3. Key Things to Read \/ Remember Right Before the Exam<\/h1>\n\n\n\n<h3 class=\"wp-block-heading\">Deployment management (high probability)<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>A <strong>service management practice<\/strong><\/li>\n\n\n\n<li>Deploys components into live environments<\/li>\n\n\n\n<li>Minimises disruption<\/li>\n\n\n\n<li>Works with change enablement and release management<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">Common exam traps<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Deployment management decides what to change \u2192 False<\/li>\n\n\n\n<li>Deployment management is the same as release management \u2192 False<\/li>\n\n\n\n<li>Deployments should be unplanned \u2192 False<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h3 class=\"wp-block-heading\">One-line memory hook<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Deployment management carefully moves changes into live use without disrupting services.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n","protected":false},"excerpt":{"rendered":"<p>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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-204","post","type-post","status-publish","format-standard","hentry","category-practices"],"_links":{"self":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=204"}],"version-history":[{"count":1,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/204\/revisions"}],"predecessor-version":[{"id":205,"href":"https:\/\/ruck.nz\/index.php?rest_route=\/wp\/v2\/posts\/204\/revisions\/205"}],"wp:attachment":[{"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=204"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=204"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ruck.nz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}