{"id":8669,"date":"2026-11-21T07:58:53","date_gmt":"2026-11-21T07:58:53","guid":{"rendered":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669"},"modified":"2026-11-21T08:00:53","modified_gmt":"2026-11-21T08:00:53","slug":"devops-consulting-milestones-faq-checkpoints","status":"publish","type":"post","link":"https:\/\/www.devopsconsulting.in\/blog\/devops-consulting-milestones-faq-checkpoints\/","title":{"rendered":"DevOps Consulting Milestones: Your Questions Answered Plainly"},"content":{"rendered":"<p>Transformation programmes rarely fail with a bang. They fade: a kickoff full of energy, a long middle where nobody can say what has actually changed, and a quiet slide into &#8220;phase two&#8221;. The antidote is unglamorous. Treat the engagement as a series of small, named checkpoints and mark each one when it is complete. Below, the questions clients raise most often about <strong>DevOps consulting milestones<\/strong>, are answered without the fluff.<\/p>\n<h2>What is a milestone in a consulting engagement, exactly?<\/h2>\n<p>A milestone is a finished piece of work with a visible output that both the client team and the consultants can point at. &#8220;Improve deployment process&#8221; is a direction. &#8220;Release pipeline for one service runs end to end from a merged change to a staging environment, with the run history saved&#8221; is a milestone. The test is simple: could two people disagree about whether it is done? If yes, rewrite it until they could not.<\/p>\n<h2>Why do long engagements need checkpoints at all?<\/h2>\n<p>Because long efforts feel endless. A programme measured in quarters has no natural moment of completion, so people lose the feeling of progress even when real progress is happening. Checkpoints supply those moments. They also act as early warning lights. If three consecutive checkpoints slip by the same margin, the plan or the scope is wrong, and you want to know that in week six rather than month six.<\/p>\n<h2>How big should a checkpoint be?<\/h2>\n<p>Aim for something a small team can finish in one to two weeks. Smaller than that and you drown in administration; larger and you are back to vague, quarter-sized promises. A practical rule of thumb: if a checkpoint needs more than one sentence to describe its output, split it. The initial assessment phase is a good example. It can be cut into &#8220;service list agreed&#8221;, &#8220;current release path drawn for each service&#8221;, and &#8220;top three delivery pain points ranked by the people who feel them&#8221;.<\/p>\n<p>The staged approach described in <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-blueprint-for-a-successful-devops-consulting-engagement-from-assessment-to-enablement\/\">a staged blueprint for a successful engagement, covering everything between the opening review and building client capability<\/a> maps neatly onto this habit, because each phase there already has a natural handful of finishable pieces.<\/p>\n<h2>Who decides that a checkpoint is done?<\/h2>\n<p>Agree this at the start, in writing, and name the roles rather than relying on goodwill. The usual pattern is that the consultant proposes completion, and a named person on the client side confirms it by looking at the output, not by reading a status message. A one-line acceptance note in the shared tracker is enough. The aim is to avoid the situation in which a checkpoint is quietly considered done by one side and quietly considered open by the other.<\/p>\n<h2>What does a good set of early checkpoints look like?<\/h2>\n<p>Early checkpoints should be quick wins that build trust and teach the team how marking works. A typical opening run might be:<\/p>\n<ol>\n<li>Working agreement signed off: scope, contacts, meeting rhythm.<\/li>\n<li>Access to repositories, environments and monitoring confirmed for every consultant.<\/li>\n<li>One service chosen as the first candidate, with a reason written down.<\/li>\n<li>Baseline notes captured for that service: how a change travels today and how long it takes.<\/li>\n<li>First small improvement shipped to a non-critical environment.<\/li>\n<\/ol>\n<p>Five ticks in the first fortnight changes the mood of an engagement. Everyone can see movement, and the sceptics on the client side have something concrete to look at rather than a slide deck.<\/p>\n<h2>How do we avoid ticking boxes that do not matter?<\/h2>\n<p>This is the right worry. A tracker stuffed with trivial ticks does more harm than having none, since it breeds misplaced comfort. Two habits help. First, every checkpoint must connect to a stated goal; if you cannot name the goal it serves, drop it. Second, review the list at fixed points, perhaps every third checkpoint, and ask which finished items made the real work easier and which turned out to be decoration. Prune the decoration.<\/p>\n<p>The wider question of how consultants fit into cloud moves is covered in <a href=\"https:\/\/www.devopsconsulting.in\/blog\/the-role-of-devops-consulting-in-cloud-migration-a-complete-guide\/\">a guide to what advisers actually do during a migration to the cloud<\/a>, which shows how many separate pieces a large move contains, each of which could carry its own tick.<\/p>\n<h2>What should we do when a checkpoint slips?<\/h2>\n<p>Do three things, in order, and keep the tone factual rather than punitive.<\/p>\n<ol>\n<li><strong>Record the slip honestly.<\/strong> Write the original date, the new date and a one-line cause. Do not quietly edit the date.<\/li>\n<li><strong>Look for the pattern.<\/strong> One late checkpoint is noise. A run of late checkpoints that share a cause, such as waiting on approvals or on a shared environment, is a finding.<\/li>\n<li><strong>Decide: split, swap or accept.<\/strong> Split the checkpoint if it was too big, swap it for a more useful one if the situation changed, or accept the new date if the cause was one-off.<\/li>\n<\/ol>\n<p>What you should not do is pile extra checkpoints on top to &#8220;catch up&#8221;. That produces a longer list and a more tired team, not more progress.<\/p>\n<h2>How do we keep stakeholders informed without extra meetings?<\/h2>\n<p>Let the tracker do the talking. A shared page that shows finished checkpoints, the next three and any slips answers most stakeholder questions without a status meeting. Keep it short and dated. Many managers find that a weekly note of three lines, covering what finished, what is next and what is stuck, is read more reliably than a long report. If your organisation prefers a call, use the tracker as the agenda and keep it under twenty minutes.<\/p>\n<h2>What should each checkpoint record contain?<\/h2>\n<p>Keep the record lean. Five fields cover nearly every case: a short name, the output that proves completion, the owner, the planned date and the actual date. A sixth field for notes is optional. Resist the urge to add status colours, percentages and priority scores; they invite debate about the tracker instead of work on the programme. When the fields are few, people actually fill them in, and a tracker that gets filled in beats an elaborate one that does not.<\/p>\n<h2>What if a checkpoint depends on another team?<\/h2>\n<p>Name the dependency inside the checkpoint itself, along with the person who can unblock it, and tick a separate small checkpoint when the dependency is cleared. This makes waiting visible. A programme that quietly loses a fortnight to an approval queue looks identical to a healthy one until the dates are missed; a programme that shows &#8220;waiting on security review, requested on the fifth&#8221; in plain sight gets the review done sooner, because everyone can see it is the thing standing between the team and the next tick.<\/p>\n<h2>Is it worth celebrating small checkpoints?<\/h2>\n<p>Yes, in proportion. Nobody needs a party for an access confirmation, but a short acknowledgement when a real piece lands, for instance the first service reaching production through the new path, keeps morale from sagging through the long middle of the engagement. Teams that never acknowledge anything tend to experience a programme as a grind, and grinds produce attrition. Tiny rituals cost nothing: a mention in the weekly note, a thank-you to the people involved, a short word at the top of the next call.<\/p>\n<h2>Does this approach only work for technical projects?<\/h2>\n<p>No. The principle applies to any multi-step job. Planning a business trip is a fair example: dates fixed, route chosen, ride booked, itinerary shared. If the ride is a bike or car hired from a private owner, a website like <a href=\"https:\/\/motoshare.us\/\">MotoShare, an online listing site for peer-to-peer vehicle rentals in the USA<\/a>, is built around the same idea of separate, clearly ordered stages, with owners listing their vehicles and renters searching, picking and booking them. Each stage is a natural place for a tick, and teams that practise the habit on small tasks find it easier to apply to large ones.<\/p>\n<h2>What does the end of the engagement look like?<\/h2>\n<p>The last checkpoints should be about continuity rather than delivery: documentation reviewed by the client team, a run-through where the client&#8217;s own engineers perform the key tasks unaided, and a short written list of what remains open. The final tick is &#8220;client team operates the process without the consultants&#8221;. That is a better definition of success than a handover meeting, because it is something you can observe.<\/p>\n<p>If you want a quick reference, keep this list near the plan: write outputs, not intentions; keep checkpoints to one or two weeks; name who confirms completion; record slips honestly; review the list regularly; and finish with checkpoints that prove the team can carry on alone. Do those six things and the long middle of the programme stops being a fog and becomes a row of small, visible finished pieces that anyone can inspect.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Straight answers on how to cut a consulting engagement into small checkpoints, who confirms each one, and what to do when a checkpoint slips.<\/p>\n","protected":false},"author":8,"featured_media":8670,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5838],"tags":[],"class_list":["post-8669","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>DevOps Consulting Milestones: Your Questions Answered Plainly - DevOps Consulting<\/title>\n<meta name=\"description\" content=\"DevOps consulting milestones explained in plain FAQ form: how big checkpoints should be, who confirms them, and how to handle slips without losing momentum.\" \/>\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\/?p=8669\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DevOps Consulting Milestones: Your Questions Answered Plainly - DevOps Consulting\" \/>\n<meta property=\"og:description\" content=\"DevOps consulting milestones explained in plain FAQ form: how big checkpoints should be, who confirms them, and how to handle slips without losing momentum.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.devopsconsulting.in\/blog\/?p=8669\" \/>\n<meta property=\"og:site_name\" content=\"DevOps Consulting\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-21T07:58:53+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-21T08:00:53+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1228932-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\\\/?p=8669#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669\"},\"author\":{\"name\":\"Kabir Malhotra\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"headline\":\"DevOps Consulting Milestones: Your Questions Answered Plainly\",\"datePublished\":\"2026-11-21T07:58:53+00:00\",\"dateModified\":\"2026-11-21T08:00:53+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669\"},\"wordCount\":1460,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1228932-banner.png\",\"articleSection\":[\"DevSecOps\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669\",\"name\":\"DevOps Consulting Milestones: Your Questions Answered Plainly - DevOps Consulting\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1228932-banner.png\",\"datePublished\":\"2026-11-21T07:58:53+00:00\",\"dateModified\":\"2026-11-21T08:00:53+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/#\\\/schema\\\/person\\\/4cff11af81c93e658f55af13b267f093\"},\"description\":\"DevOps consulting milestones explained in plain FAQ form: how big checkpoints should be, who confirms them, and how to handle slips without losing momentum.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/?p=8669#primaryimage\",\"url\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1228932-banner.png\",\"contentUrl\":\"https:\\\/\\\/www.devopsconsulting.in\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/11\\\/b2a-banner-1228932-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":"DevOps Consulting Milestones: Your Questions Answered Plainly - DevOps Consulting","description":"DevOps consulting milestones explained in plain FAQ form: how big checkpoints should be, who confirms them, and how to handle slips without losing momentum.","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\/?p=8669","og_locale":"en_US","og_type":"article","og_title":"DevOps Consulting Milestones: Your Questions Answered Plainly - DevOps Consulting","og_description":"DevOps consulting milestones explained in plain FAQ form: how big checkpoints should be, who confirms them, and how to handle slips without losing momentum.","og_url":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669","og_site_name":"DevOps Consulting","article_published_time":"2026-11-21T07:58:53+00:00","article_modified_time":"2026-11-21T08:00:53+00:00","og_image":[{"width":1200,"height":630,"url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1228932-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\/?p=8669#article","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669"},"author":{"name":"Kabir Malhotra","@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"headline":"DevOps Consulting Milestones: Your Questions Answered Plainly","datePublished":"2026-11-21T07:58:53+00:00","dateModified":"2026-11-21T08:00:53+00:00","mainEntityOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669"},"wordCount":1460,"commentCount":0,"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1228932-banner.png","articleSection":["DevSecOps"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.devopsconsulting.in\/blog\/?p=8669#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669","url":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669","name":"DevOps Consulting Milestones: Your Questions Answered Plainly - DevOps Consulting","isPartOf":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669#primaryimage"},"image":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669#primaryimage"},"thumbnailUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1228932-banner.png","datePublished":"2026-11-21T07:58:53+00:00","dateModified":"2026-11-21T08:00:53+00:00","author":{"@id":"https:\/\/www.devopsconsulting.in\/blog\/#\/schema\/person\/4cff11af81c93e658f55af13b267f093"},"description":"DevOps consulting milestones explained in plain FAQ form: how big checkpoints should be, who confirms them, and how to handle slips without losing momentum.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.devopsconsulting.in\/blog\/?p=8669"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.devopsconsulting.in\/blog\/?p=8669#primaryimage","url":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1228932-banner.png","contentUrl":"https:\/\/www.devopsconsulting.in\/blog\/wp-content\/uploads\/2026\/11\/b2a-banner-1228932-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\/8669","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=8669"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8669\/revisions"}],"predecessor-version":[{"id":8765,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/posts\/8669\/revisions\/8765"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media\/8670"}],"wp:attachment":[{"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/media?parent=8669"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/categories?post=8669"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsconsulting.in\/blog\/wp-json\/wp\/v2\/tags?post=8669"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}