{"id":10912,"date":"2022-01-24T11:00:14","date_gmt":"2022-01-24T11:00:14","guid":{"rendered":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/?p=10912"},"modified":"2023-12-21T06:51:57","modified_gmt":"2023-12-21T06:51:57","slug":"balance-ramp-ups-and-ramp-downs-in-a-project","status":"publish","type":"post","link":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/","title":{"rendered":"How to Balance Ramp-Ups and Ramp-Downs in a Project?"},"content":{"rendered":"

While managing resources in a multi-project environment<\/a>, you must have faced the challenges of handling several requirements simultaneously. Indeed, it\u2019s a daunting task. Managers have to strategically prioritize projects, identify suitable resources, ensure a 100% or a near-perfect fill rate for every project, to stay competitive.<\/p>\n

In fact, in a multi-project scenario, managers receive these resource requests<\/strong> in a staggered manner. Moreover, they are not usually forewarned of the project closure. Hence, keeping track of varying timelines (including both onset and end dates) and staying abreast of roll-offs<\/strong> or release of the resources makes it all the more arduous.<\/p>\n

This inability to stay atop of all project and resource schedules results in unmanaged ramp-up and ramp-down that can negatively affect the organization\u2019s bottom line.<\/span><\/p>\n

Therefore, it is imperative for resource managers<\/a> to formulate effective strategies to manage frequently changing resource requests. This blog discusses the negative consequences of unmanaged ramp-up and ramp-down<\/strong> and a few proven techniques to tackle them.<\/p>\n

But first, let\u2019s understand the processes in detail.<\/p>\n

\"Effectively<\/a><\/p>\n

Understanding ramp-up and ramp-down<\/h2>\n

Before going into the details of these two terms, it is essential to get a brief idea of the project lifecycle<\/a>.<\/p>\n

A project\u2019s lifecycle primarily comprises five stages as follows:<\/p>\n

    \n
  1. First, initiation,<\/strong> involves defining deliverables, objectives, risks, and requirements, selecting the project management methods, etc.<\/li>\n
  2. Planning<\/strong> entails documenting a project plan<\/a><\/strong>, creating a work breakdown structure, defining roles and responsibilities, allocating resources to tasks, scheduling, etc.<\/li>\n
  3. Execution<\/strong> constitutes maintaining communication flow amongst the resource pool, tracking and handling change requests and dependencies<\/a>, and providing extra time, budget, or resources if required.<\/li>\n
  4. Control and Monitor,<\/strong> run in parallel with the execution phase, which comprises tracking KPIs, conducting status meetings<\/a> with stakeholders and teammates, etc.<\/li>\n
  5. Closure<\/strong> encompasses terminating the project officially, releasing resources, submitting deliverables, and documenting lessons learned.<\/li>\n<\/ol>\n

    Given the five stages of the project\u2019s lifecycle, let\u2019s understand how ramp-up and ramp-down occur based on various scenarios.<\/p>\n

    \"project<\/a><\/p>\n

    Case 1 – Ramp-up due to the initiation\/peak time in a project<\/h3>\n

    In the planning phase, when the project manager creates a work breakdown structure<\/strong>, they identify resource requirements<\/a> and raise requests. A sudden increase in resource requirement is known as ramp up. The resource manager identifies and allocates the appropriate resources to fulfill the resource requests.<\/p>\n

    Ramp-up occurs during \u201cexecution\u201d<\/em> stage when additional resources are needed to complete different tasks. Let\u2019s consider an IT project, for example. In its development phase, the project needs multiple resources with different skills. The resources will be required in a staggered manner within the project. Accordingly, the project manager provides a monthly resource requirement so that it gives sufficient lead time to the resource manager for fulfillment.<\/p>\n

    Case 2 – Ramp-down due to a large-scale roll-off from a project.<\/h3>\n

    When a project has passed through its peak or the \u201cexecution\u201d phase and reaches \u201ccontrol\u201d or \u201cclosure,\u201d resource requirements decrease. It requires only limited resources to handle operational activities while other team members can be released in a phased manner. At this stage, the project manager rolls off the excess resources from the project, causing a ramp-down. Apart from project closure<\/strong>, an abrupt halt, incorrect resource estimation<\/a>, or project failure can also cause a ramp-down.<\/p>\n

    For example, after the development and final delivery of the IT project, the \u201cmaintenance\u201d phase begins. Depending on the nature of the contract, the organization may only require certain developers to add new functionalities or testers to fix bugs, etc. Thus, the manager will release other resources from the project.<\/p>\n

    Now that the basics of ramp up and ramp down are clear, let\u2019s understand their repercussions if not managed proactively.
    \n    \"Project<\/a><\/p>\n

    Negative effects of ineffective ramp up & ramp-down management<\/h2>\n

    Ramp-up and ramp-down are inherent to every project. However, if not tackled properly, it can negatively impact the organizational efficiency and resource health index<\/strong>.<\/p>\n

    Enlisted below are some consequences:<\/p>\n

    Increase in bench size<\/h3>\n

    Due to a lack of visibility into projects and resources\u2019 schedules, the resource manager fails to identify the projects approaching ramp-down. Consequently, resources from multiple projects hit the bench, increasing the bench size<\/strong>. Since people on the bench do not generate any revenue and are on the company\u2019s payroll, it affects the bottom line.<\/p>\n

    Rise in unplanned attritions<\/h3>\n

    As stated earlier, poorly managed ramp-down can increase bench size and disengage the workforce. When resources don\u2019t have enough work and their skills are not utilized effectively, it results in disengagement, lowered morale, and reduced productivity. It may further erode the sense of purpose and belonging. Eventually, they may decide to look for better opportunities elsewhere, causing unplanned attritions<\/a>.<\/p>\n

    \"effective<\/a><\/p>\n

    Billing losses due to unavailability of resources<\/h3>\n

    Ideally, when a project manager estimates skill requirements and raises resource requests<\/a>, the resource manager should fulfill them before the due date. However, if a large number of resource requirements<\/strong> come at the eleventh hour, they cannot be timely fulfilled, leading to billing losses.<\/p>\n

    Timeline delays & budget overruns<\/h3>\n

    A lack of foresight into project demands can result in a failure to manage the sudden resource requirement effectively.<\/span><\/p>\n

    When projects don\u2019t get the requisite resources on time, it may lead to delays in their timelines. Moreover, hiring a contingent workforce<\/a> to meet the last-minute demands<\/strong> can compromise quality, and will also be costlier, eventually causing budget overruns.<\/p>\n

    Lost opportunities and decline in company revenue<\/h3>\n

    Inability to foresee the approaching ramp-downs gives the resource manager an impression that all the resources are involved in one or the other project. As a result, when a new project arrives, they think they don\u2019t have the visibility of resource availability<\/a>. As a result, the project delivery team<\/strong> can refuse new work or delay its timeline, causing a loss of opportunities and a decline in company revenue.<\/p>\n

    Last-minute firefighting for resources<\/h3>\n

    When resource managers fail to foresee the future or pipeline project<\/a> demand or do not receive the resource requests on time, they do not get sufficient lead time to procure the right resource. Thus, this triggers the last-minute firefighting<\/strong> for resources which may even lead to the hiring of a mismatched skillset, further deteriorating the project quality.<\/p>\n

    \"Resource<\/a>
    \nIt is evident that both ill-managed ramp-up and ramp-down activities can have various ramifications. Nevertheless, implementing modern resource management software can help you stay forewarned of these activities and manage them proactively.<\/p>\n

    The following section explains how.<\/p>\n

    Ways resource management software can help manage ramp-ups and ramp-downs effectively<\/h2>\n

    The art of managing ramp-up and ramp-down activities across multiple projects is crucial for successful project execution and maintaining resource health index. Implementing a resource management tool<\/strong> along with soft skills<\/a> such as quick decision-making, negotiation power, etc., will help the resource manager master this process.<\/p>\n

    Enlisted below are a few prominent ways a resource management tool can help.<\/p>\n

    Provides enterprise-wide visibility of resource and project schedules<\/h3>\n

    A robust resource management software<\/a> provides 360-degree visibility of resources, their schedules, other attributes such as skills, location, experience, etc. Moreover, resource managers get a comprehensive view of future projects as and when project managers create vacancies via generic booking. It helps the resource managers stay abreast of the upcoming projects and expected ramp-ups, which further assists them in taking proactive actions to fill the spot in advance.<\/p>\n

    Similarly, with an overview of current and future resource schedules<\/strong>, managers can foresee when they will be released from projects. Thus, they can find appropriate projects and allocate them before they hit the bench. It will help reduce the resources\u2019 bench time between two projects, facilitating a well-managed ramp-down.<\/p>\n

    Offers foresight into future project demands<\/h3>\n

    With clear visibility into pipeline projects, the resource manager can stay forewarned of future resource requirements and skill demand. They can look into the existing workforce to analyze and determine the capacity vs. demand<\/a> gaps. This will help them initiate the right resourcing measures ahead of time to avoid any hassle at the eleventh hour.<\/p>\n

    For partial skill matches, proper upskilling, cross-skilling, and training measures can help close the existing gaps. In cases where the resources don\u2019t possess the required skillsets at all, planned hiring<\/a> can help recruit the right talent at the right costs. However, hiring a contingent workforce can be a better choice for projects with demands that are one-off in nature. This proactive resource planning<\/strong> facilitates efficient management of ramp-ups.<\/p>\n

    \"perfect<\/a><\/p>\n

    Delivers data-driven BI reports<\/h3>\n

    A resource management tool provides various reports generated using Business Intelligence<\/strong> in real-time. When a project manager sends resource requests or creates a vacancy, they immediately reflect in the project vacancy report. With this, the resource manager can get a complete idea of the future resource demand. Accordingly, they can start appropriate resourcing techniques to fulfill them and avert an unmanaged ramp-up.<\/p>\n

    The people-on-the-bench report, on the other hand, plays a key role in monitoring the bench size. It also helps identify resources that will hit the bench in the future. Resource managers can leverage this report to initiate training or upskilling<\/a> and prepare them to take on future projects or align their competencies to fill project vacancies.<\/p>\n

    Align sales with delivery<\/h3>\n

    Involving the delivery team at the early stage of the sales process is essential. When a sales opportunity attains a particular probable stage for closure, the sales team should coordinate with the delivery team. It can help determine the project’s viability and decide whether it can be accepted or not.<\/p>\n

    Accordingly, in coordination with the project manager, the resource manager can start preparing to fulfill the upcoming demand in advance. With complete visibility into the resource pool<\/strong>, the manager can find or hire suitable resources ahead of time. It helps achieve on-time fulfillment of resource requests and prevents last-minute hassle in managing ramp-ups.<\/p>\n

    Allows out rotation and backfill for critical projects’ demands<\/h3>\n

    Sometimes a project may experience a shortage of niche expertise. Finding these people outside the organization may be arduous and time-consuming. Also, when these critical resources get rolled off, finding projects for them may again be challenging.<\/p>\n

    Resource management software maintains an enterprise-wide record of resource profiles and schedules<\/a>.<\/span><\/p>\n

    Based on that, the resource manager can out rotate<\/strong> some resources from the projects reaching the closure or maintenance phase. Then, they can fill the vacant positions with suitable backfills. This way, they can handle the ramp-up efficiently.<\/p>\n

    Takeaway<\/h2>\n

    Rise and fall in resource demands across multiple projects are inevitable. What matters more is how efficiently you can combat them and keep all the ongoing and future projects optimally staffed with appropriate resources.<\/p>\n

    It is where handling both ramp-up and ramp-down efficiently plays a pivotal role. By combining your management and soft skills with robust resource management software, you can streamline resource planning and stay on top of them.<\/p>\n

    The Glossary<\/h2>\n

    \"the<\/a><\/p>\n

    The SAVIOM Solution<\/h2>\n

    SAVIOM is the market leader in helping multinational clients manage their resources efficiently and effectively. With over 20 years of experience, this Australian-based MNC has a global presence across 50 countries and has helped 100+ clients with their Workforce Planning Software<\/a>. Saviom also provides tools for Enterprise Project Resource Management<\/a>, Project Portfolio Management<\/a>, and Professional Service Automation<\/a>. Boost your remote team collaboration with Saviom.<\/p>\n","protected":false},"excerpt":{"rendered":"

    While managing resources in a multi-project environment, you must have faced the challenges of handling several requirements simultaneously. Indeed, it\u2019s a daunting task. Managers have to strategically prioritize projects, identify suitable resources, ensure a 100% or a near-perfect fill rate for every project, to stay competitive. In fact, in a multi-project scenario, managers receive these […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"yoast_head":"\nbalancing ramp-ups ramp-downs in a project<\/title>\n<meta name=\"description\" content=\"Ramp-ups and ramp-downs are inevitable in every project but need to be managed effectively to maintain organizational health index and efficiency. Learn how.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Balance Ramp-Ups and Ramp-Downs in a Project?\" \/>\n<meta property=\"og:description\" content=\"Ramp-ups and ramp-downs are inevitable in every project but need to be managed effectively to maintain organizational health index and efficiency. Learn how.\" \/>\n<meta property=\"og:url\" content=\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/\" \/>\n<meta property=\"og:site_name\" content=\"Resources Library\" \/>\n<meta property=\"article:published_time\" content=\"2022-01-24T11:00:14+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-12-21T06:51:57+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2022\/01\/MicrosoftTeams-image-146.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"536\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Mahendra Gupta\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"How to Balance Ramp-Ups and Ramp-Downs in a Project?\" \/>\n<meta name=\"twitter:image\" content=\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2022\/01\/MicrosoftTeams-image-146.jpg\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mahendra Gupta\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/\",\"url\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/\",\"name\":\"balancing ramp-ups ramp-downs in a project\",\"isPartOf\":{\"@id\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#website\"},\"datePublished\":\"2022-01-24T11:00:14+00:00\",\"dateModified\":\"2023-12-21T06:51:57+00:00\",\"author\":{\"@id\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#\/schema\/person\/363ad412d3216940f49f43339e52883b\"},\"description\":\"Ramp-ups and ramp-downs are inevitable in every project but need to be managed effectively to maintain organizational health index and efficiency. Learn how.\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/\"]}]},{\"@type\":\"WebSite\",\"@id\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#website\",\"url\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/\",\"name\":\"Resources Library\",\"description\":\"Saviom\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#\/schema\/person\/363ad412d3216940f49f43339e52883b\",\"name\":\"Mahendra Gupta\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#\/schema\/person\/image\/\",\"url\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2023\/08\/Mahendra-gupta.jpg\",\"contentUrl\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2023\/08\/Mahendra-gupta.jpg\",\"caption\":\"Mahendra Gupta\"},\"url\":\"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/author\/mahendra-gupta\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"balancing ramp-ups ramp-downs in a project","description":"Ramp-ups and ramp-downs are inevitable in every project but need to be managed effectively to maintain organizational health index and efficiency. Learn how.","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":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/","og_locale":"en_US","og_type":"article","og_title":"How to Balance Ramp-Ups and Ramp-Downs in a Project?","og_description":"Ramp-ups and ramp-downs are inevitable in every project but need to be managed effectively to maintain organizational health index and efficiency. Learn how.","og_url":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/","og_site_name":"Resources Library","article_published_time":"2022-01-24T11:00:14+00:00","article_modified_time":"2023-12-21T06:51:57+00:00","og_image":[{"width":1024,"height":536,"url":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2022\/01\/MicrosoftTeams-image-146.jpg","type":"image\/jpeg"}],"author":"Mahendra Gupta","twitter_card":"summary_large_image","twitter_title":"How to Balance Ramp-Ups and Ramp-Downs in a Project?","twitter_image":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2022\/01\/MicrosoftTeams-image-146.jpg","twitter_misc":{"Written by":"Mahendra Gupta","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/","url":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/","name":"balancing ramp-ups ramp-downs in a project","isPartOf":{"@id":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#website"},"datePublished":"2022-01-24T11:00:14+00:00","dateModified":"2023-12-21T06:51:57+00:00","author":{"@id":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#\/schema\/person\/363ad412d3216940f49f43339e52883b"},"description":"Ramp-ups and ramp-downs are inevitable in every project but need to be managed effectively to maintain organizational health index and efficiency. Learn how.","inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/balance-ramp-ups-and-ramp-downs-in-a-project\/"]}]},{"@type":"WebSite","@id":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#website","url":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/","name":"Resources Library","description":"Saviom","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#\/schema\/person\/363ad412d3216940f49f43339e52883b","name":"Mahendra Gupta","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/#\/schema\/person\/image\/","url":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2023\/08\/Mahendra-gupta.jpg","contentUrl":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-content\/uploads\/2023\/08\/Mahendra-gupta.jpg","caption":"Mahendra Gupta"},"url":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/author\/mahendra-gupta\/"}]}},"_links":{"self":[{"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/posts\/10912"}],"collection":[{"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/comments?post=10912"}],"version-history":[{"count":5,"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/posts\/10912\/revisions"}],"predecessor-version":[{"id":17676,"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/posts\/10912\/revisions\/17676"}],"wp:attachment":[{"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/media?parent=10912"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/categories?post=10912"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/ec2-52-95-249-27.ap-south-1.compute.amazonaws.com:8000\/blog\/wp-json\/wp\/v2\/tags?post=10912"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}