{"id":8589,"date":"2026-11-20T23:10:00","date_gmt":"2026-11-20T23:10:00","guid":{"rendered":"https:\/\/www.devopsconsulting.in\/blog\/?p=8589"},"modified":"2026-11-20T23:10:00","modified_gmt":"2026-11-20T23:10:00","slug":"programmes-slip-diagnosis-waiting-for-register","status":"publish","type":"post","link":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/","title":{"rendered":"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix"},"content":{"rendered":"<p>Symptom: a transformation programme that was on schedule in week two is visibly behind by week six, and nobody can point to a single technical failure. Pipelines were designed, environments sketched, backlog groomed. Yet milestones keep sliding. In our experience of delivery reviews, the root cause is rarely engineering difficulty. It is a cluster of requests sitting unanswered in other people&#8217;s queues. This article diagnoses that pattern and sets out a remedy that costs nothing to adopt: a disciplined waiting-for list.<\/p>\n<h2>The symptom in detail<\/h2>\n<p>Programme leads describe the same sequence. A workstream reaches a point where it needs something from outside its own team: a firewall rule, an approved service account, a decision on the target hosting model, a signed-off change window. A request goes out. The workstream continues with lower-priority tasks. Days pass. When the team eventually returns to the blocked item, the answer has not arrived and nobody remembers precisely when it was requested or of whom.<\/p>\n<p>The slippage is invisible in status reporting because every individual task is &#8220;in progress&#8221; or &#8220;waiting,&#8221; and waiting does not appear as a risk on most dashboards. By the time it becomes a headline, weeks of schedule have already been consumed.<\/p>\n<h2>Diagnosis: three underlying faults<\/h2>\n<p><strong>Fault one: requests are made but not recorded.<\/strong> They live in chat, email and meeting side conversations. Nothing aggregates them, so no one can see how many are open.<\/p>\n<p><strong>Fault two: no date attaches to the follow-up.<\/strong> A request without a planned nudge relies on someone remembering. Memory fails in proportion to workload, so the busiest periods generate the most abandoned requests.<\/p>\n<p><strong>Fault three: ownership on the other side is vague.<\/strong> A request addressed to &#8220;the network team&#8221; or &#8220;security&#8221; has no named recipient, which means no one feels the obligation personally.<\/p>\n<p>Each fault is mundane. Combined, they are enough to derail a programme with an excellent technical plan.<\/p>\n<h2>Remedy: a waiting-for list with five fields<\/h2>\n<p>The fix is a single shared register, owned by one person on the delivery side. Every row contains the following:<\/p>\n<ul>\n<li><strong>The request<\/strong>, stated precisely enough that a stranger could act on it.<\/li>\n<li><strong>The named owner<\/strong> on the receiving side, with their function.<\/li>\n<li><strong>The date raised<\/strong> and the channel used.<\/li>\n<li><strong>The dependent work<\/strong> that cannot proceed or will be at risk without the answer.<\/li>\n<li><strong>The next follow-up date<\/strong>, set at the time the row is created.<\/li>\n<\/ul>\n<p>Rows with no owner are not accepted into the list. If the requester cannot identify who owes the answer, that itself is the first thing to resolve, and the row&#8217;s first action becomes &#8220;find out who decides.&#8221;<\/p>\n<h2>Applying it to a typical engagement<\/h2>\n<p>Consider a team moving a set of build and deployment pipelines to a new platform. Early on the consultants raise six requests: network access for the build agents, a decision on secrets management, a test environment quota, access to the existing deployment scripts, confirmation of the change-freeze calendar, and a named approver for production releases.<\/p>\n<p>On the register, each carries an owner and a date. The access request has a short follow-up interval because it blocks the first pilot pipeline. The secrets decision is flagged as a dependency of three other tasks, so it gets an early nudge and a note to raise it at the next steering meeting if still open. The freeze calendar can wait a week.<\/p>\n<p>Every Monday the delivery lead scans the list, sends brief reminders to anyone past their date, and reports the count of overdue items to the sponsor. After a few weeks, the sponsor begins asking for the list before asking for the plan, because it shows where the real constraints sit.<\/p>\n<h2>How it complements the broader engagement structure<\/h2>\n<p>A register of this kind does not replace the structure of an engagement, from assessment through to enablement; it threads through it. Our article on <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-blueprint-for-a-successful-devops-consulting-engagement-from-assessment-to-enablement\/\">structuring a DevOps engagement from assessment to enablement<\/a> describes the phases, and every phase generates external requests. During assessment, the list tracks access to systems and interviews awaited. During build, it tracks approvals and environments. During handover, it tracks sign-offs and documentation owed by the client.<\/p>\n<p>The same applies to specialised workstreams. When security checks are woven into delivery, as discussed in our <a href=\"https:\/\/www.devopsconsulting.in\/blog\/devsecops-consulting-guide-how-to-integrate-security-into-devops-pipelines\/\">guide to integrating security into pipelines<\/a>, reviews and exceptions frequently depend on people outside the delivery team. Those are precisely the items to put on the list.<\/p>\n<h2>Writing a request that can actually be answered<\/h2>\n<p>Many rows stay open because the original request was ambiguous. &#8220;Need access to the environment&#8221; invites a reply asking which environment, for whom and for how long. A request that names the system, the accounts concerned, the purpose and the date by which the answer is useful can usually be actioned in one pass. When you record it, copy the exact wording into the row so that your reminder repeats it faithfully rather than paraphrasing from memory.<\/p>\n<p>Attach a reason to the date as well. &#8220;By Thursday, because the pilot pipeline cannot run without it&#8221; gives the recipient a legitimate basis for prioritising, and it gives you a clear trigger for escalation if Thursday passes.<\/p>\n<h2>Cadence and governance<\/h2>\n<p>Review the register at three levels. Individually, each practitioner checks their own rows daily. At team level, a brief weekly sweep identifies items older than their expected response time. At governance level, the sponsor sees only the overdue subset, with owners and ages, because that is where intervention is useful.<\/p>\n<p>When a row crosses a second nudge without reply, escalate it in the agreed way. The escalation path should be set at kickoff, not improvised in week six. A short note such as &#8220;raised on this date, reminded twice, blocking the following milestone&#8221; is clear, neutral and difficult to dispute.<\/p>\n<h2>Cloud migration: a specific hotspot<\/h2>\n<p>Migration work is especially prone to the problem because it crosses so many organisational boundaries. Our analysis of <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-role-of-devops-consulting-in-cloud-migration-a-complete-guide\/\">the part consulting plays in cloud migration<\/a> points to coordination as a recurring source of delay. Applying a waiting-for register at the very start of such a project, before the first request is sent, is cheaper than reconstructing the history afterwards.<\/p>\n<h2>Objections you will hear, and short replies<\/h2>\n<p><strong>&#8220;We already have a risk log.&#8221;<\/strong> A risk log records what might go wrong. The waiting-for register records what is already pending and whose move it is; the two feed one another, but the register changes daily.<\/p>\n<p><strong>&#8220;This looks like nagging.&#8221;<\/strong> Agreed dates make reminders routine instead of personal. If the follow-up schedule was shared at kickoff, a prompt arriving on the stated day is simply part of the process.<\/p>\n<p><strong>&#8220;The client will not read it.&#8221;<\/strong> They do not need to read all of it. A weekly extract showing only items overdue on their side is short, factual and difficult to ignore.<\/p>\n<h2>Checking that the remedy works<\/h2>\n<p>Do not rely on impressions. Track two simple measures over a month. First, the count of open items older than their expected response time. It should fall as nudges become routine. Second, the number of milestones moved because of an outstanding external answer. It should also fall, and any that do slip should be explainable by named rows on the register.<\/p>\n<p>If neither improves, check whether the list is actually being read. A register that nobody opens fails for the same reason the original problem occurred: the information exists but no one acts on it at the right time.<\/p>\n<h2>Wider applications<\/h2>\n<p>The pattern generalises to any large undertaking with many outside parties. A prospective home buyer, for instance, might consult a research site such as <a href=\"https:\/\/propraahi.com\/\">Propraahi, which presents property research guides and community discussion aimed at buyers in India<\/a>, and then find that the real work is coordinating answers from several sources. A register of asks and expected replies serves that person just as it serves a delivery lead.<\/p>\n<h2>Summary of the diagnosis and cure<\/h2>\n<ul>\n<li><strong>Symptom:<\/strong> milestones slip without a visible technical cause.<\/li>\n<li><strong>Cause:<\/strong> external requests are unrecorded, undated and unowned.<\/li>\n<li><strong>Cure:<\/strong> one shared waiting-for register with an owner, a date raised and a follow-up date on every row.<\/li>\n<li><strong>Cadence:<\/strong> daily personal glance, weekly team sweep, overdue subset to the sponsor.<\/li>\n<li><strong>Test:<\/strong> fewer aged items and fewer milestones moved by unanswered requests.<\/li>\n<\/ul>\n<p>Implementing this takes an afternoon. Maintaining it takes minutes each day. The return is a programme in which delays have names and dates attached, which is the first condition for resolving them.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Milestones slipping with no technical cause? The usual culprit is unrecorded external requests. Here is the diagnosis and a five-field register to cure it.<\/p>\n","protected":false},"author":8,"featured_media":8590,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5838],"tags":[],"class_list":["post-8589","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devsecops"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v28.7 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix - DevOps Consulting<\/title>\n<meta name=\"description\" content=\"Milestones slipping with no technical cause? Diagnose unrecorded external requests and fix them with a five-field waiting-for register.\" \/>\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\/programmes-slip-diagnosis-waiting-for-register\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix - DevOps Consulting\" \/>\n<meta property=\"og:description\" content=\"Milestones slipping with no technical cause? Diagnose unrecorded external requests and fix them with a five-field waiting-for register.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/\" \/>\n<meta property=\"og:site_name\" content=\"DevOps Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-20T23:10:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3916281-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=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/\"},\"author\":{\"name\":\"Kabir Malhotra\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"headline\":\"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix\",\"datePublished\":\"2026-11-20T23:10:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/\"},\"wordCount\":1411,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3916281-banner.png\",\"articleSection\":[\"DevSecOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/\",\"name\":\"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix - DevOps Consulting\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3916281-banner.png\",\"datePublished\":\"2026-11-20T23:10:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"description\":\"Milestones slipping with no technical cause? Diagnose unrecorded external requests and fix them with a five-field waiting-for register.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/programmes-slip-diagnosis-waiting-for-register\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3916281-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-3916281-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":"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix - DevOps Consulting","description":"Milestones slipping with no technical cause? Diagnose unrecorded external requests and fix them with a five-field waiting-for register.","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\/programmes-slip-diagnosis-waiting-for-register\/","og_locale":"en_US","og_type":"article","og_title":"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix - DevOps Consulting","og_description":"Milestones slipping with no technical cause? Diagnose unrecorded external requests and fix them with a five-field waiting-for register.","og_url":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/","og_site_name":"DevOps Consulting","article_published_time":"2026-11-20T23:10:00+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3916281-banner.png","type":"image\/png"}],"author":"Kabir Malhotra","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kabir Malhotra","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/#article","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/"},"author":{"name":"Kabir Malhotra","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"headline":"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix","datePublished":"2026-11-20T23:10:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/"},"wordCount":1411,"commentCount":0,"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3916281-banner.png","articleSection":["DevSecOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/","url":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/","name":"Why Programmes Slip Without a Cause: Diagnosis and a Waiting-For Fix - DevOps Consulting","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/#primaryimage"},"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3916281-banner.png","datePublished":"2026-11-20T23:10:00+00:00","author":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"description":"Milestones slipping with no technical cause? Diagnose unrecorded external requests and fix them with a five-field waiting-for register.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.devopsconsulting.in\/blog\/programmes-slip-diagnosis-waiting-for-register\/#primaryimage","url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3916281-banner.png","contentUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-3916281-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\/8589","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=8589"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8589\/revisions"}],"predecessor-version":[{"id":8753,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8589\/revisions\/8753"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media\/8590"}],"wp:attachment":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media?parent=8589"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/categories?post=8589"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/tags?post=8589"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}