{"id":8377,"date":"2026-11-14T04:10:00","date_gmt":"2026-11-14T04:10:00","guid":{"rendered":"https:\/\/www.devopsconsulting.in\/blog\/?p=8377"},"modified":"2026-11-14T08:10:00","modified_gmt":"2026-11-14T08:10:00","slug":"release-rehearsal-myths","status":"publish","type":"post","link":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/","title":{"rendered":"Six Release Rehearsal Myths That Keep Teams From Practising"},"content":{"rendered":"<p>Ask a room of engineers whether they rehearse releases and most will say yes. Ask to see the last rehearsal&#8217;s notes and the room gets quiet. In DevOps consulting work, the release rehearsal is one of the most agreed-with and least-practised ideas, partly because a handful of myths give teams permission to skip it. Here are six of those myths, with the plain facts that answer each.<\/p>\n<h2>Myth 1: &#8220;Our automated tests already are the rehearsal&#8221;<\/h2>\n<p>Tests check that code behaves as specified. A rehearsal checks that people, tooling and timing behave as planned. Those are different questions. A suite can pass on every commit while the deployment still fails because a certificate expired, a migration locks a table for twenty minutes, or the person with approval rights is on a flight. Tests are necessary. They simply cannot discover steps nobody wrote down.<\/p>\n<p>The practical fix is to treat the release itself as the thing under test. Run the same pipeline, the same scripts and the same approvals against a staging copy, and have the people who would run the real thing do it.<\/p>\n<h2>Myth 2: &#8220;Staging never matches production, so it proves nothing&#8221;<\/h2>\n<p>Environments do drift apart over time, and that is an argument for improving staging, not for abandoning it. Even an imperfect environment catches the large share of release problems that have nothing to do with scale: missing environment variables, wrong ordering of steps, forgotten config flags, scripts that assume a path that exists only on one machine. Make a short list of the known differences between staging and production, keep it visible, and treat each difference as a risk you accept knowingly.<\/p>\n<h2>Myth 3: &#8220;A rehearsal doubles the work&#8221;<\/h2>\n<p>It adds work up front and removes work later. Consulting engagements repeatedly show the same arithmetic: a release that runs smoothly takes a small fraction of the time of one that triggers an incident, and incidents consume days of attention from several people afterwards. The rehearsal is also repeatable. Once the steps are scripted for staging, the same script runs against production with a change of target, so most of the cost is paid once.<\/p>\n<h2>Myth 4: &#8220;Only big releases need one&#8221;<\/h2>\n<p>Size is a poor predictor of trouble. A one-line configuration change can take a service down faster than a quarter&#8217;s worth of features, because it bypasses the habits people use for large changes. Instead of rehearsing by size, rehearse by novelty and by blast radius. If the change touches something the team has not changed before, or something many customers depend on, run it once on a safe copy. Small, routine changes can follow a lighter version of the same practice.<\/p>\n<h2>Myth 5: &#8220;We can rehearse in our heads&#8221;<\/h2>\n<p>A walkthrough in a meeting has value, but it tests the plan as understood, not the plan as executed. Real execution is where you find that step four needs a command that only one laptop has, or that the runbook refers to a dashboard that was renamed. The only reliable method is to do the steps. Make people type the commands, click the buttons, and read the output. Keep a timer running and a scribe taking notes of every pause.<\/p>\n<h2>Myth 6: &#8220;If the rehearsal passes, the release is safe&#8221;<\/h2>\n<p>A clean rehearsal reduces the chances of avoidable error. It does not remove uncertainty about real traffic, real data volumes or third-party behaviour. Pair it with sensible release practice: a clear point at which you stop and roll back, someone watching the right signals, and a communication plan. Think of the rehearsal as removing the dull surprises so that attention can go to the interesting ones.<\/p>\n<p>A related trap is rehearsing with the wrong cast. If the most senior engineer always drives, everyone else on the team stays unfamiliar with the steps, and the rehearsal proves only that one person can do the job. Put the newest capable person at the keyboard and let the experts watch. Every hesitation is then a gap in the documentation, not a gap in anyone&#8217;s skill, and fixing it makes the procedure safer for the night when the expert is unavailable.<\/p>\n<h2>What a useful rehearsal looks like in practice<\/h2>\n<ol>\n<li>Agree the scope: which release, which environment, which people.<\/li>\n<li>Freeze the plan, then run it literally, including approvals and notifications.<\/li>\n<li>Capture timings for each stage and compare them with what the schedule assumed.<\/li>\n<li>Exercise the rollback at least once, from a state that resembles the post-release one.<\/li>\n<li>Hold a ten-minute review and update the runbook before leaving the room.<\/li>\n<\/ol>\n<p>Notice what is missing: heavy tooling, long meetings, formal sign-off. The value comes from doing the real steps once in a place where a mistake has no customers attached to it.<\/p>\n<h2>Connecting the rehearsal to the wider engagement<\/h2>\n<p>For organisations just starting out, the rehearsal fits naturally into the assessment and enablement stages described in this overview of <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-blueprint-for-a-successful-devops-consulting-engagement-from-assessment-to-enablement\/\">how a successful consulting engagement moves from first assessment to a team that can run on its own<\/a>. Security-minded readers will also find that the rehearsal is a convenient place to try new scanning and approval steps, as discussed in the <a href=\"https:\/\/www.devopsconsulting.in\/blog\/devsecops-consulting-guide-how-to-integrate-security-into-devops-pipelines\/\">consulting guide on weaving security into delivery pipelines<\/a>, before they become mandatory for everyone.<\/p>\n<h2>Lessons from outside engineering<\/h2>\n<p>Practices like this are not unique to software. Anyone who has cooked a heritage recipe for a crowd knows to try a small trial first. Projects that preserve such know-how, for example <a href=\"https:\/\/www.blendz.com\/\">Blendz, an open food-heritage archive built around traditional recipes, rare ingredients and community-submitted stories<\/a>, rely on cooks who have tested and refined each method. Release teams should hold their own procedures to that standard.<\/p>\n<h2>How to start without a big programme<\/h2>\n<p>Pick the next release that scares anyone on the team. Block two hours, one week before the date. Run it against staging with the people who will run the real thing, keep a timer and a notes document, and rehearse the rollback too. Afterwards fix the top three problems, then schedule the real release. If the rehearsal finds nothing, you have lost two hours. If it finds something, you have gained a calm release day and a more accurate runbook, and the argument for the next rehearsal makes itself.<\/p>\n<p>Over time, you can fold the rehearsal into the pipeline itself, running it automatically on every release candidate and keeping the human version for the largest or most novel changes. The goal is not ceremony. It is a team that treats the first real run as the second run.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Six common excuses for skipping a release rehearsal, from &#8216;our tests cover it&#8217; to &#8216;staging is different&#8217;, with the plain facts that answer each one.<\/p>\n","protected":false},"author":8,"featured_media":8378,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30],"tags":[],"class_list":["post-8377","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-consulting"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Six Release Rehearsal Myths That Keep Teams From Practising - DevOps Consulting<\/title>\n<meta name=\"description\" content=\"Six myths about release rehearsals, from tests being enough to staging never matching production, and what DevOps teams should do instead.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Six Release Rehearsal Myths That Keep Teams From Practising - DevOps Consulting\" \/>\n<meta property=\"og:description\" content=\"Six myths about release rehearsals, from tests being enough to staging never matching production, and what DevOps teams should do instead.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/\" \/>\n<meta property=\"og:site_name\" content=\"DevOps Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-14T04:10:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-14T08:10:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-301992-banner.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Kabir Malhotra\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kabir Malhotra\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/\"},\"author\":{\"name\":\"Kabir Malhotra\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"headline\":\"Six Release Rehearsal Myths That Keep Teams From Practising\",\"datePublished\":\"2026-11-14T04:10:00+00:00\",\"dateModified\":\"2026-11-14T08:10:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/\"},\"wordCount\":1092,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-301992-banner.png\",\"articleSection\":[\"DevOps consulting\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/\",\"name\":\"Six Release Rehearsal Myths That Keep Teams From Practising - DevOps Consulting\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-301992-banner.png\",\"datePublished\":\"2026-11-14T04:10:00+00:00\",\"dateModified\":\"2026-11-14T08:10:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"description\":\"Six myths about release rehearsals, from tests being enough to staging never matching production, and what DevOps teams should do instead.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/release-rehearsal-myths\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-301992-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-301992-banner.png\",\"width\":1200,\"height\":630},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/\",\"name\":\"DevOps Consulting\",\"description\":\"DevOps Consulting | SRE Consulting | DevSecOps Consulting | MLOps Consulting\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\",\"name\":\"Kabir Malhotra\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g\",\"caption\":\"Kabir Malhotra\"},\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/author\\\/kabir-malhotra\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Six Release Rehearsal Myths That Keep Teams From Practising - DevOps Consulting","description":"Six myths about release rehearsals, from tests being enough to staging never matching production, and what DevOps teams should do instead.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/","og_locale":"en_US","og_type":"article","og_title":"Six Release Rehearsal Myths That Keep Teams From Practising - DevOps Consulting","og_description":"Six myths about release rehearsals, from tests being enough to staging never matching production, and what DevOps teams should do instead.","og_url":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/","og_site_name":"DevOps Consulting","article_published_time":"2026-11-14T04:10:00+00:00","article_modified_time":"2026-11-14T08:10:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-301992-banner.png","type":"image\/png"}],"author":"Kabir Malhotra","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kabir Malhotra","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/#article","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/"},"author":{"name":"Kabir Malhotra","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"headline":"Six Release Rehearsal Myths That Keep Teams From Practising","datePublished":"2026-11-14T04:10:00+00:00","dateModified":"2026-11-14T08:10:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/"},"wordCount":1092,"commentCount":0,"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-301992-banner.png","articleSection":["DevOps consulting"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/","url":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/","name":"Six Release Rehearsal Myths That Keep Teams From Practising - DevOps Consulting","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/#primaryimage"},"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-301992-banner.png","datePublished":"2026-11-14T04:10:00+00:00","dateModified":"2026-11-14T08:10:00+00:00","author":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"description":"Six myths about release rehearsals, from tests being enough to staging never matching production, and what DevOps teams should do instead.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.devopsconsulting.in\/blog\/release-rehearsal-myths\/#primaryimage","url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-301992-banner.png","contentUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-301992-banner.png","width":1200,"height":630},{"@type":"WebSite","@id":"https:\/\/www.devopsconsulting.in\/blog\/#website","url":"https:\/\/www.devopsconsulting.in\/blog\/","name":"DevOps Consulting","description":"DevOps Consulting | SRE Consulting | DevSecOps Consulting | MLOps Consulting","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.devopsconsulting.in\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093","name":"Kabir Malhotra","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d77044c5c70611f0b6d1131a1758057dcb873aae1740ec1c40a13a6428461d0b?s=96&d=mm&r=g","caption":"Kabir Malhotra"},"url":"https:\/\/www.devopsconsulting.in\/blog\/author\/kabir-malhotra\/"}]}},"_links":{"self":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8377","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/comments?post=8377"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8377\/revisions"}],"predecessor-version":[{"id":8508,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8377\/revisions\/8508"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media\/8378"}],"wp:attachment":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media?parent=8377"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/categories?post=8377"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/tags?post=8377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}