{"id":475,"date":"2026-03-18T19:00:26","date_gmt":"2026-03-18T19:00:26","guid":{"rendered":"https:\/\/www.itheight.com\/blog\/?p=475"},"modified":"2026-10-26T18:04:43","modified_gmt":"2026-10-26T18:04:43","slug":"mastering-requirements-in-project-management-from-elicitation-to-traceability","status":"publish","type":"post","link":"https:\/\/www.itheight.com\/blog\/mastering-requirements-in-project-management-from-elicitation-to-traceability\/","title":{"rendered":"Mastering Requirements in Project Management: From Elicitation to Traceability"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">In the world of project management especially for professionals preparing for PMP certification understanding how to gather, analyze, and track requirements is not just a skill, it is an art. Whether you are building a software system, launching a product, or even planning a vacation with friends, the ability to clearly define and manage requirements determines the success of your project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s explore this journey step by step, in a way that feels practical, engaging, and deeply insightful.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is Requirements Collection (Now Called \u201cElicit and Analyze Requirements\u201d)?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Traditionally, in earlier editions of PMBOK, this process was known as <em>Collect Requirements<\/em>. However, in the <em>PMBOK 8th Edition, the terminology has evolved to \u201cElicit and Analyze Requirements\u201d<\/em>, reflecting a more mature and realistic understanding of how requirements are discovered and refined. At its core, this process is about:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Eliciting requirements (drawing them out from stakeholders)<\/li>\n\n\n\n<li>Analyzing them (refining, validating, and structuring them)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Rather than simply asking, \u201cWhat do you want?\u201d, a skilled project manager or business analyst facilitates a thoughtful exploration. <\/p>\n\n\n\n<p class=\"is-style-text-display is-style-text-display--1 wp-block-paragraph\">Requirements are not always obvious they must be uncovered, refined, and validated.<\/p>\n\n\n\n<p class=\"is-style-text-subtitle is-style-text-subtitle--2 wp-block-paragraph\">Think of it like fishing in a vast ocean. The requirements are not lying on the surface, you must use the right techniques to catch them.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Understanding Requirements Through a Simple Analogy<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Imagine planning a group vacation. Each person has different preferences, someone wants a luxury hotel, another prefers budget-friendly options, someone wants adventure, and someone just wants relaxation. Your job is to balance all these expectations into one workable plan. Similarly, in a project:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Each stakeholder has unique needs<\/li>\n\n\n\n<li>Constraints like budget and time exist<\/li>\n\n\n\n<li>Trade-offs are inevitable (cannot be avoided)<\/li>\n<\/ul>\n\n\n\n<p class=\"is-style-text-display is-style-text-display--3 wp-block-paragraph\">The phrase \u201cTrade-offs are inevitable\u201d means that in any project (or even in real life), you cannot get everything exactly the way you want, you must give up something to gain something else.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A successful outcome doesn\u2019t mean everyone gets everything\u2014it means everyone gets enough to feel satisfied.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Key Techniques for Eliciting and Analyzing Requirements<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The shift in terminology from <em>Collect<\/em> to <em><strong>Elicit and Analyze<\/strong><\/em> also highlights that this is not a passive activity&#8230; it requires structured techniques and active engagement.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Document Analysis (Learning from the Past)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most powerful starting points is reviewing existing documents such as:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li>Business plans<\/li>\n\n\n\n<li>Process diagrams<\/li>\n\n\n\n<li>User manuals<\/li>\n\n\n\n<li>Contracts and reports<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">These documents provide valuable insights into current systems and help you build a strong foundation.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Interviews (Deep and Focused Conversations)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Interviews allow you to dive deeper into stakeholder expectations. Unlike surveys, interviews enable you to:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li>Ask follow-up questions<\/li>\n\n\n\n<li>Clarify ambiguities<\/li>\n\n\n\n<li>Explore hidden needs<\/li>\n<\/ul>\n\n\n\n<p class=\"is-style-text-display is-style-text-display--4 wp-block-paragraph\">For example, asking \u201cWhy is this feature important?\u201d often reveals more valuable insights than the feature itself.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Surveys and Questionnaires (Reaching the Masses)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When dealing with a large audience, surveys become extremely useful. They help you:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li>Collect data quickly<\/li>\n\n\n\n<li>Identify trends<\/li>\n\n\n\n<li>Capture diverse opinions<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">However, the quality of insights depends heavily on asking the right questions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Observation \/ Job Shadowing (Experiencing Reality)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Sometimes, the best way to understand a problem is to live it. For instance:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>If you are automating a manual process, observe how people currently perform it<\/li>\n\n\n\n<li>If building a ride sharing app, experience commuting challenges yourself<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Observation reveals what stakeholders may not articulate.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">5. Workshops vs Focus Groups<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These two are often confused but serve different purposes:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li><strong><em>Focus Groups:<\/em><\/strong> Gather diverse opinions (no consensus expected)<\/li>\n\n\n\n<li><strong><em>Workshops:<\/em><\/strong> Aim to reach agreement (consensus-driven)<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Workshops are especially powerful in complex projects where alignment is critical.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">6. Prototyping (Making Ideas Tangible)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Prototypes bring ideas to life. They can be:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li>Wireframes<\/li>\n\n\n\n<li>Mockups<\/li>\n\n\n\n<li>Working models<\/li>\n\n\n\n<li>Even simple sketches<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">When stakeholders see something visual, their feedback becomes clearer and more actionable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">7. Visual Techniques (Mind Maps &amp; Affinity Diagrams)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Visual representation makes requirements easier to understand. These techniques simplify complexity and improve clarity.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><em>Mind Maps:<\/em><\/strong> Show relationships between features<\/li>\n\n\n\n<li><strong><em>Affinity Diagrams:<\/em><\/strong> Group similar ideas into categories<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Types of Requirements We Must Understand<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When working on any project, one of the most critical skills is the ability to differentiate between various types of requirements. Many project failures occur not because teams don\u2019t work hard!!! but because they misunderstand what type of requirement they are dealing with.<\/p>\n\n\n\n<p class=\"is-style-text-subtitle is-style-text-subtitle--5 wp-block-paragraph\">Understanding these layers helps you move from \u201cWhy are we doing this?\u201d \u2192 \u201cWhat should be built?\u201d \u2192 \u201cHow will it be delivered?\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Let\u2019s explore each type in depth. A well structured project distinguishes between different types of requirements:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Business Requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These define why the project exists, such as increasing revenue or improving efficiency. Business requirements define the core purpose of the project. They answer the fundamental question:<\/p>\n\n\n\n<p class=\"is-style-text-subtitle is-style-text-subtitle--6 wp-block-paragraph\">&#8220;Why are we doing this project at all?&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><mark style=\"background-color:#fff6b1\" class=\"has-inline-color\">These are high level and strategic in nature. They focus on <em>business value<\/em>, <em>not technical details<\/em><\/mark>.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Examples<\/h4>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Increase revenue by 20%<\/li>\n\n\n\n<li>Reduce operational costs<\/li>\n\n\n\n<li>Improve customer satisfaction<\/li>\n\n\n\n<li>Expand into a new market<\/li>\n<\/ul>\n\n\n\n<h5 class=\"wp-block-heading\">Real Life Scenario<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">If a company launches an e-commerce website, the business requirement could be: \u201cIncrease online sales and reach a wider customer base.\u201d <\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><mark style=\"background-color:#ffe2fd\" class=\"has-inline-color\"><em>Notice:<\/em> there is no mention of features yet. It\u2019s purely about the business goal.<\/mark><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Stakeholder Requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">These reflect expectations of users and stakeholders for example, \u201cone-click checkout\u201d in an e-commerce system.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Solution Requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Solution requirements explain <mark style=\"background-color:#fff6b1\" class=\"has-inline-color\">how the system will fulfill stakeholder needs<\/mark>. Solution requirements are of two types:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Functional requirements (features)<\/li>\n\n\n\n<li>Non-functional requirements (performance, security)<\/li>\n<\/ul>\n\n\n\n<h4 class=\"wp-block-heading\">A. Functional Requirements (Features &amp; Functions)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">These define what the system should do. <mark style=\"background-color:#fff6b1\" class=\"has-inline-color\">Think of them as <em>capabilities<\/em> or <em>features<\/em><\/mark>.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Examples<\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li>User can register\/login<\/li>\n\n\n\n<li>Add items to cart<\/li>\n\n\n\n<li>Make online payment<\/li>\n\n\n\n<li>Generate invoice<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group rcrec has-accent-5-background-color has-background has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<h6 class=\"wp-block-heading\">Simple Understanding<\/h6>\n\n\n\n<p class=\"wp-block-paragraph\">If stakeholder says: \u201cI want to transfer money\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Functional requirement becomes: \u201cSystem should allow user to add beneficiary and transfer funds.\u201d<\/p>\n<\/div>\n\n\n\n<h4 class=\"wp-block-heading\">B. Non-Functional Requirements (Performance &amp; Quality)<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">These define how well the system performs. <mark style=\"background-color:#fff6b1\" class=\"has-inline-color\">They are not about features, but about quality attributes<\/mark>.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Examples<\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li>System should load within 2 seconds<\/li>\n\n\n\n<li>Website should handle 10,000 users simultaneously<\/li>\n\n\n\n<li>Data must be encrypted<\/li>\n\n\n\n<li>System uptime should be 99.9%<\/li>\n<\/ul>\n\n\n\n<h5 class=\"wp-block-heading\">Example<\/h5>\n\n\n\n<p class=\"wp-block-paragraph\">A banking app that allows money to transfer is it&#8217;s Functional Requirement, however if it crashes frequently it is not fit for use, thus it&#8217;s Non-Functional aspect hindered it to work nicely.<\/p>\n\n\n\n<div class=\"wp-block-group rcrec has-accent-2-background-color has-background has-global-padding is-layout-constrained wp-block-group-is-layout-constrained\">\n<h6 class=\"wp-block-heading\">Powerful Concept (Very Important for PMP)<\/h6>\n\n\n\n<p class=\"wp-block-paragraph\">Functional = Fit for Purpose (Does it do the job?)<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Non-Functional = Fit for Use (Does it do it well?)<\/p>\n<\/div>\n\n\n\n<h3 class=\"wp-block-heading\">Project Requirements (Constraints &amp; Conditions)<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Constraints like time, cost, and scope. Project requirements define how the project will be executed, <mark style=\"background-color:#fff6b1\" class=\"has-inline-color\">not the product itself<\/mark>. They are related to project management constraints.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Key Insight<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">They ensure the project stays within boundaries. These requirements guide:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li>Planning<\/li>\n\n\n\n<li>Execution<\/li>\n\n\n\n<li>Monitoring<\/li>\n<\/ul>\n\n\n\n<h5 class=\"wp-block-heading\">Examples<\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Project must be completed in 6 months<\/li>\n\n\n\n<li>Budget is limited to $50,000<\/li>\n\n\n\n<li>Must comply with company policies<\/li>\n\n\n\n<li>Must follow Agile methodology<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Transition Requirements<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Transition requirements are <mark style=\"background-color:#fff6b1\" class=\"has-inline-color\">temporary requirements needed to move from the current state to the future state<\/mark>. Once the transition is complete, these are no longer needed.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\">Real-Life Example<\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">A builder creates a sample flat to show customers. Once the building is complete, that sample flat is removed. That\u2019s a transition requirement.<\/p>\n\n\n\n<h5 class=\"wp-block-heading\">Examples<\/h5>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Data migration from old system to new system<\/li>\n\n\n\n<li>User training sessions<\/li>\n\n\n\n<li>Parallel system run (old + new system together)<\/li>\n\n\n\n<li>Temporary reporting setup<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">How All These Requirements Are Connected<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Requirement Type<\/th><th><\/th><th>Example<\/th><\/tr><\/thead><tbody><tr><td>Business Requirement<\/td><td>Why are we doing this?<\/td><td>\u201cI want a comfortable home for my family\u201d<\/td><\/tr><tr><td>Stakeholder Requirement<\/td><td><\/td><td>\u201cWe need 3 bedrooms and a garden\u201d<\/td><\/tr><tr><td>Solution Requirement<\/td><td>How will we build it?<\/td><td><em><mark style=\"background-color:#ffe2fd\" class=\"has-inline-color\">Functional Requirement:<\/mark><\/em> \u201cBuild rooms, kitchen, bathrooms\u201d<br><em><mark style=\"background-color:#ffe2fd\" class=\"has-inline-color\">Non-Functional Requirement:<\/mark><\/em> \u201cStrong structure, proper ventilation\u201d<\/td><\/tr><tr><td>Project Requirement<\/td><td>Under what constraints?<\/td><td>\u201cComplete within 6 months, budget 50 lakh\u201d<\/td><\/tr><tr><td>Transition Requirement<\/td><td>How do we move from old to new?<\/td><td>\u201cTemporary living arrangement during construction\u201d<\/td><\/tr><tr><td>Quality Requirements<\/td><td><\/td><td><em>Part of Non-Functional Requirements<\/em><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Requirement Traceability Matrix (RTM)<\/h2>\n\n\n\n<p class=\"is-style-text-subtitle is-style-text-subtitle--7 wp-block-paragraph\">Your Control System<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most powerful tools in project management is the Requirement Traceability Matrix (RTM). It ensures that every requirement is:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Clearly defined<\/li>\n\n\n\n<li>Properly implemented<\/li>\n\n\n\n<li>Thoroughly tested<\/li>\n<\/ul>\n\n\n\n<p class=\"is-style-text-display is-style-text-display--8 wp-block-paragraph\">RTM provides complete traceability&#8230; from idea to execution.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Why RTM is Essential<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Imagine giving multiple requirements to your team and later wondering:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which requirements are completed?<\/li>\n\n\n\n<li>Which are still pending?<\/li>\n\n\n\n<li>Where is each requirement implemented?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">RTM answers all these questions by linking:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requirement \u2192 Design \u2192 Development \u2192 Testing \u2192 Delivery<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">It acts as a single source of truth throughout the project lifecycle.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Elements of RTM<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A typical RTM includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requirement ID<\/li>\n\n\n\n<li>Description<\/li>\n\n\n\n<li>Source (who requested it)<\/li>\n\n\n\n<li>Priority<\/li>\n\n\n\n<li>Status (e.g., discussed, implemented, tested)<\/li>\n\n\n\n<li>Mapping to deliverables and test cases<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This ensures end to end visibility and control.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Decision-Making in Requirements<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When stakeholders disagree, decision-making becomes critical. Common approaches include:<\/p>\n\n\n\n<ul class=\"wp-block-list is-style-checkmark-list\">\n<li>Unanimity: Everyone agrees<\/li>\n\n\n\n<li>Majority: More than 50% agree<\/li>\n\n\n\n<li>Plurality: Largest group wins (even without majority)<\/li>\n\n\n\n<li>Autocratic: Project manager decides<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">In real world projects, a balanced approach is often required.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">A Practical Insight: Requirements Evolve<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">One important reality: requirements are not static. They evolve as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Stakeholders gain clarity<\/li>\n\n\n\n<li>Market conditions change<\/li>\n\n\n\n<li>New constraints emerge<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">That is why tools like RTM are continuously updated\u2014not created once and forgotten.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Final Thoughts<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The evolution from \u201cCollect Requirements\u201d to \u201cElicit and Analyze Requirements\u201d is not just a change in wording it reflects a deeper shift in mindset.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Requirements are no longer something you simply gather.<br>They are something you discover, shape, validate, and continuously refine.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you truly want to master concepts like requirement elicitation, analysis, RTM, and real world project scenarios, <a href=\"https:\/\/www.itheight.com\/\" target=\"_blank\" rel=\"noreferrer noopener\" class=\"noul\">ITHeight<\/a> is the best PMP institute offering expert mentoring, structured study lectures by Sir Shahid Naseer, and exceptional exam preparation ability helping you succeed with confidence.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In the world of project management especially for professionals preparing for PMP certification understanding how to gather, analyze, and track requirements is not just a skill, it is an art. Whether you are building a software system, launching a product, or even planning a vacation with friends, the ability to clearly define and manage requirements [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-475","post","type-post","status-publish","format-standard","hentry","category-pmp"],"_links":{"self":[{"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/posts\/475","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/comments?post=475"}],"version-history":[{"count":9,"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/posts\/475\/revisions"}],"predecessor-version":[{"id":490,"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/posts\/475\/revisions\/490"}],"wp:attachment":[{"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/media?parent=475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/categories?post=475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itheight.com\/blog\/wp-json\/wp\/v2\/tags?post=475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}