{"id":85452,"date":"2025-08-26T17:58:04","date_gmt":"2025-08-26T12:28:04","guid":{"rendered":"https:\/\/www.guvi.in\/blog\/?p=85452"},"modified":"2026-07-21T14:38:33","modified_gmt":"2026-07-21T09:08:33","slug":"agile-methodology-in-software-development","status":"publish","type":"post","link":"https:\/\/www.guvi.in\/blog\/agile-methodology-in-software-development\/","title":{"rendered":"What is Agile Methodology in Software Development? (2026)"},"content":{"rendered":"\n<p>Agile methodology is an iterative approach to building software where teams work in short cycles called sprints instead of planning the entire project upfront. It values working software, customer collaboration, and adapting to change over rigid documentation and fixed plans.<\/p>\n\n\n\n<p><strong>The 4 core Agile values:<\/strong><\/p>\n\n\n\n<ul>\n<li>Individuals and interactions over processes and tools<\/li>\n\n\n\n<li>Working software over comprehensive documentation<\/li>\n\n\n\n<li>Customer collaboration over contract negotiation<\/li>\n\n\n\n<li>Responding to change over following a plan<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>TL;DR Summary<\/strong><\/h2>\n\n\n\n<ul>\n<li>Agile breaks software projects into short sprints (usually 1 to 4 weeks) instead of one long delivery cycle<\/li>\n\n\n\n<li>It is built on 4 core values and 12 principles from the 2001 Agile Manifesto<\/li>\n\n\n\n<li>Scrum, Kanban, and XP are the most common Agile frameworks, each suited to different team sizes and work styles<\/li>\n\n\n\n<li>Agile is now standard practice at most Indian IT companies, though enterprise-wide adoption varies by organization<\/li>\n\n\n\n<li>You can validate Agile skills with certifications like PSM, CSM, or PMI-ACP depending on your career track<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What is Agile Methodology?<\/strong><\/h2>\n\n\n\n<p>Agile methodology is an approach to <a href=\"https:\/\/www.guvi.in\/blog\/is-software-development-hard\/\" target=\"_blank\" rel=\"noreferrer noopener\">software development<\/a> that focuses on flexibility, collaboration, and delivering value quickly. It encourages a progressive and collaborative approach by prioritizing incremental iterations over more linear traditional methods (e.g., Waterfall methodology). <\/p>\n\n\n\n<p>Instead of waiting months (or even years) for a final product, Agile teams release smaller pieces of working software early and improve them continuously based on user feedback.<\/p>\n\n\n\n<p>In short:<\/p>\n\n\n\n<ul>\n<li>Agile is primarily about responding to change, rather than following a detailed plan.<\/li>\n\n\n\n<li>It values individuals and interactions more than extensive documentation.<\/li>\n\n\n\n<li>It focuses on customer satisfaction by enabling customers to receive value early, and often.<\/li>\n<\/ul>\n\n\n\n<div style=\"background-color: #099f4e; border: 3px solid #110053; border-radius: 12px; padding: 18px 22px; color: #FFFFFF; font-size: 18px; font-family: Montserrat, Helvetica, sans-serif; line-height: 1.6; box-shadow: 0 4px 12px rgba(0, 0, 0, 0.15); max-width: 750px;\"> \n  <strong style=\"font-size: 22px; color: #FFFFFF;\">\ud83d\udca1 Did You Know?<\/strong> \n  <br \/><br \/> \n  <strong style=\"color: #FFFFFF;\">Agile<\/strong> was born in <strong style=\"color: #FFFFFF;\">2001<\/strong> when 17 software developers created the <strong style=\"color: #FFFFFF;\">Agile Manifesto<\/strong>, introducing a new way of building software that prioritized <em>flexibility<\/em>, <em>collaboration<\/em>, and <em>customer interaction<\/em> over rigid planning. Fast forward to today, and more than <strong style=\"color: #FFFFFF;\">71% of companies worldwide<\/strong> use Agile practices not only in software development, but also in <strong style=\"color: #FFFFFF;\">marketing<\/strong>, <strong style=\"color: #FFFFFF;\">product design<\/strong>, and even <strong style=\"color: #FFFFFF;\">education<\/strong> to deliver adaptability in fast-moving environments.\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Agile vs Waterfall vs Scrum vs Kanban: Complete Comparison<\/strong><\/h2>\n\n\n\n<p>People often use these terms interchangeably, but they&#8217;re not the same thing. Waterfall and Agile are philosophies. Scrum and Kanban are frameworks that sit inside Agile.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Framework<\/th><th>Best For<\/th><th>Team Size<\/th><th>Sprint Length<\/th><th>Key Tool<\/th><\/tr><\/thead><tbody><tr><td>Waterfall<\/td><td>Fixed-scope projects (banking, government)<\/td><td>Any size<\/td><td>No sprints, sequential phases<\/td><td>Gantt charts<\/td><\/tr><tr><td>Agile (general)<\/td><td>Evolving requirements, fast-changing markets<\/td><td>Small to large<\/td><td>1 to 4 weeks<\/td><td>Product backlog<\/td><\/tr><tr><td>Scrum<\/td><td>Teams needing structure and defined roles<\/td><td>5 to 9 members<\/td><td>2 to 4 weeks<\/td><td>Sprint board<\/td><\/tr><tr><td>Kanban<\/td><td>Continuous, ongoing work with variable priorities<\/td><td>Any size<\/td><td>No fixed sprints<\/td><td>Kanban board<\/td><\/tr><\/tbody><\/table><figcaption class=\"wp-element-caption\"><strong>Agile vs Waterfall vs Scrum vs Kanban: Complete Comparison<\/strong><\/figcaption><\/figure>\n\n\n\n<p>Waterfall moves in a straight line. You finish requirements, then design, then development, then testing, then deployment, in that exact order. There&#8217;s no going back once a phase closes. This works well when requirements genuinely won&#8217;t change, but it becomes risky the moment they do.<\/p>\n\n\n\n<p>Agile does the opposite. It treats the plan as something you improve continuously, not something you lock in at the start. Scrum adds structure to that flexibility through defined roles and time-boxed sprints, while Kanban skips the sprints entirely and focuses on visualizing work as it flows through stages.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How Agile Works: The Sprint Cycle<\/strong><\/h2>\n\n\n\n<p>To get a better understanding of Agile, let\u2019s place it into the <a href=\"https:\/\/www.guvi.in\/blog\/software-development-life-cycle\/\" target=\"_blank\" rel=\"noreferrer noopener\">software development life cycle<\/a> (SDLC).<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1200\" height=\"630\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-1200x630.png\" alt=\"\" class=\"wp-image-86599\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-1200x630.png 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-300x158.png 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-768x403.png 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-1536x806.png 1536w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-2048x1075.png 2048w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/09\/01@2x-150x79.png 150w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Requirements and Backlog Grooming<\/strong><\/h3>\n\n\n\n<p>You don&#8217;t need every requirement locked in before starting. Agile teams gather enough to begin, then keep adding and reprioritizing items in the backlog as the project unfolds.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Sprint Planning<\/strong><\/h3>\n\n\n\n<p>The team picks a set of backlog items to complete in the upcoming sprint, usually 1 to 4 weeks long, and defines what &#8220;done&#8221; looks like for each one.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Development and Testing<\/strong><\/h3>\n\n\n\n<p>Unlike Waterfall, coding and testing happen together, not as separate phases. This catches bugs early instead of at the very end.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Review and Deployment<\/strong><\/h3>\n\n\n\n<p>At the end of each sprint, you have a working, demoable piece of software. Feedback from this review shapes what goes into the next sprint.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Retrospective<\/strong><\/h3>\n\n\n\n<p>The team reflects on what worked and what didn&#8217;t, then adjusts. This is what keeps Agile teams actually improving instead of repeating the same mistakes sprint after sprint.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Popular Agile Frameworks Compared<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1200\" height=\"900\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_58_13-AM-1200x900.webp\" alt=\"Popular Agile Frameworks Compared\" class=\"wp-image-124294\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_58_13-AM-1200x900.webp 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_58_13-AM-300x225.webp 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_58_13-AM-768x576.webp 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_58_13-AM-150x113.webp 150w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_58_13-AM.webp 1448w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<p>You&#8217;ll mostly encounter three frameworks on the job:<\/p>\n\n\n\n<ul>\n<li><strong>Scrum:<\/strong> Organizes work into sprints with three defined roles: Product Owner, Scrum Master, and the Development Team. It&#8217;s the most widely used framework in startups and enterprises alike.<\/li>\n\n\n\n<li><strong>Kanban:<\/strong> Visualizes tasks on a board with columns like &#8220;To Do,&#8221; &#8220;In Progress,&#8221; and &#8220;Done.&#8221; There are no fixed sprints, just a continuous flow of work.<\/li>\n\n\n\n<li><strong>Extreme Programming (XP):<\/strong> Focuses heavily on technical practices like pair programming and test-driven development to keep code quality high while shipping fast.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Agile in Indian IT Companies: How It Is Actually Implemented<\/strong><\/h2>\n\n\n\n<p>Agile adoption looks different at a 50-person startup than it does at a 500,000-employee IT services company, and that gap is worth understanding before your first job.<\/p>\n\n\n\n<p>TCS is a useful example here. The company set a public goal of becoming &#8220;Enterprise Agile&#8221; and has trained hundreds of thousands of employees in Agile delivery, building dedicated agile development zones across its offices. But even at that scale, full enterprise-wide Agile has taken years to roll out, moving from a small percentage of Agile projects in 2017 toward much broader adoption since.<\/p>\n\n\n\n<p>For most freshers joining service-based companies like TCS, Infosys, or Wipro, you&#8217;re more likely to work within a hybrid setup. Client-facing project delivery might still follow Waterfall-style milestones and documentation, while the actual engineering team runs 2-week Scrum sprints internally.<\/p>\n\n\n\n<p>A few things to expect:<\/p>\n\n\n\n<ul>\n<li>Daily standups are common even in hybrid teams<\/li>\n\n\n\n<li>Jira and Azure DevOps are the most widely used Agile tracking tools in Indian IT<\/li>\n\n\n\n<li>Client contracts sometimes force a Waterfall-style reporting layer even when the dev team works in sprints<\/li>\n\n\n\n<li>Product-based companies (as opposed to service-based) tend to run &#8220;purer&#8221; Agile with more team autonomy<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Benefits of Agile Methodology<\/strong><\/h2>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1200\" height=\"675\" src=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM-1200x675.webp\" alt=\"Benefits of Agile Methodology\" class=\"wp-image-124295\" srcset=\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM-1200x675.webp 1200w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM-300x169.webp 300w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM-768x432.webp 768w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM-1536x864.webp 1536w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM-150x84.webp 150w, https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/07\/ChatGPT-Image-Jul-20-2026-07_59_12-AM.webp 1672w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" title=\"\"><\/figure>\n\n\n\n<ul>\n<li><strong>Faster delivery:<\/strong> You ship usable software every sprint instead of waiting months for one release<\/li>\n\n\n\n<li><strong>Better adaptability:<\/strong> Changing requirements don&#8217;t derail the whole project<\/li>\n\n\n\n<li><strong>Continuous feedback:<\/strong> Customers see progress early and often, so surprises are rare<\/li>\n\n\n\n<li><strong>Lower risk:<\/strong> Bugs and misaligned features get caught within weeks, not at the finish line<\/li>\n\n\n\n<li><strong>Stronger collaboration:<\/strong> Daily standups and sprint reviews keep everyone aligned<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common Mistakes Teams Make With Agile<\/strong><\/h2>\n\n\n\n<ol>\n<li><strong>Treating sprints as mini-Waterfalls:<\/strong> Some teams still plan everything upfront within a sprint and refuse to adjust mid-cycle, which defeats the purpose of Agile.<\/li>\n\n\n\n<li><strong>Skipping retrospectives:<\/strong> Without honest retros, teams repeat the same process problems sprint after sprint.<\/li>\n\n\n\n<li><strong>Overloading the backlog:<\/strong> Cramming too many items into one sprint leads to rushed, low-quality work.<\/li>\n\n\n\n<li><strong>No clear Product Owner:<\/strong> Without one person owning priorities, the backlog turns into a free-for-all.<\/li>\n\n\n\n<li><strong>Confusing &#8220;Agile&#8221; with &#8220;no planning&#8221;:<\/strong> Agile still requires planning; it just happens in smaller, more frequent cycles.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Agile Certifications Worth Getting: PSM, CSM, PMI-ACP<\/strong><\/h2>\n\n\n\n<p>If you want proof of Agile knowledge on your resume, these three certifications carry the most weight in 2026:<\/p>\n\n\n\n<ul>\n<li><strong><a href=\"https:\/\/www.scrum.org\/assessments\/professional-scrum-master-i-certification\" target=\"_blank\" rel=\"noreferrer noopener nofollow\">PSM I<\/a> (Professional Scrum Master, Scrum.org):<\/strong> No mandatory training required, exam-only pathway, costs around $200. It has a tougher passing bar than CSM, which makes it attractive if you&#8217;re comfortable self-studying.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.scrumalliance.org\/get-certified\/scrum-master-track\/certified-scrummaster\" data-type=\"link\" data-id=\"https:\/\/www.scrumalliance.org\/get-certified\/scrum-master-track\/certified-scrummaster\" target=\"_blank\" rel=\"noopener\">CSM<\/a> (Certified ScrumMaster, Scrum Alliance):<\/strong> Requires a mandatory 2-day instructor-led course, typically costing $400 to $1,000 depending on the provider. It&#8217;s the most commonly requested Agile certification on job boards.<\/li>\n\n\n\n<li><strong>PMI-ACP (PMI Agile Certified Practitioner):<\/strong> Covers Scrum, Kanban, Lean, and XP rather than just Scrum. It requires 2 years of Agile project experience and 21 hours of Agile training, so it suits people already working in the field rather than absolute beginners.<\/li>\n<\/ul>\n\n\n\n<p>If you&#8217;re just starting out, CSM or PSM I gets you certified faster. PMI-ACP is a stronger fit once you have hands-on experience and want a credential recognized outside the Scrum-specific world.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Agile Interview Questions for Software Developers<\/strong><\/h2>\n\n\n\n<ul>\n<li>What is the difference between Agile and Waterfall?<\/li>\n\n\n\n<li>What are the four core values of the Agile Manifesto?<\/li>\n\n\n\n<li>How is Scrum different from Kanban?<\/li>\n\n\n\n<li>What happens during a sprint retrospective, and why does it matter?<\/li>\n\n\n\n<li>How would you handle a client who wants to add scope mid-sprint?<\/li>\n\n\n\n<li>What is a product backlog, and who owns it?<\/li>\n\n\n\n<li>Can you describe a time you worked in an Agile team? What was your role?<\/li>\n<\/ul>\n\n\n\n<p>For roles at Indian IT companies, expect at least one or two of these paired with a follow-up about how you&#8217;d apply Agile in a client-facing, hybrid project setup.<\/p>\n\n\n\n<p>If this is something that interests you, and you want to become a software developer, then take the chance to get started and learn with HCL GUVI&#8217;s IITM Pravartak and MongoDB Certified Online <a href=\"https:\/\/www.guvi.in\/zen-class\/ai-software-development-course\/?utm_source=blog&amp;utm_medium=hyperlink&amp;utm_campaign=agile-methodology-in-software-development\" target=\"_blank\" rel=\"noreferrer noopener\">AI Software Development Course<\/a>. This NSDC-approved course offers a certificate recognized globally, which adds serious bragging rights to your r\u00e9sum\u00e9 and will help you set yourself apart in a highly competitive employment market.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>Agile has become the default way software gets built, not because it&#8217;s trendy, but because it solves a real problem: requirements change, and rigid processes can&#8217;t keep up. Whether you end up on a Scrum team, a Kanban board, or a hybrid setup at an Indian IT company, understanding how sprints, backlogs, and retrospectives fit together will make you useful from day one. <\/p>\n\n\n\n<p>Start by getting comfortable with the vocabulary, then look for a chance to work in an actual sprint cycle, even a small student project run as Agile will teach you more than any definition can.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>FAQs<\/strong><\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1756208755153\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>1. What is Agile methodology in simple words?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Agile is a way of building software in small, working pieces delivered every few weeks, instead of waiting months for one final release.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1756208785893\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>2. Is Agile better than Waterfall?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Neither is universally better. Agile suits projects with changing requirements, while Waterfall works well for fixed-scope projects like banking or government systems.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1756208813107\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>3. What are the main types of Agile?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Scrum and Kanban are the most common, followed by Extreme Programming (XP) and Lean.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1756208845387\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>4. How long is an Agile sprint?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Most sprints run 1 to 4 weeks, with 2 weeks being the most common length in practice.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1756208867370\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \">5. <strong>Do Indian IT companies actually use Agile?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Yes, though implementation varies. Companies like TCS have invested heavily in enterprise-wide Agile training, but many client projects still run in a hybrid model with Waterfall-style reporting layered over Agile sprints.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1784514270779\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>6. Which Agile certification should a fresher get first?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>PSM I or CSM are the most accessible starting points. PMI-ACP is better suited once you have a couple of years of Agile project experience.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1784514280077\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \"><strong>7. What is the difference between Scrum Master and Product Owner?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>The Scrum Master facilitates the process and removes blockers for the team. The Product Owner defines priorities and represents the customer&#8217;s needs.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Agile methodology is an iterative approach to building software where teams work in short cycles called sprints instead of planning the entire project upfront. It values working software, customer collaboration, and adapting to change over rigid documentation and fixed plans. The 4 core Agile values: TL;DR Summary What is Agile Methodology? Agile methodology is an [&hellip;]<\/p>\n","protected":false},"author":63,"featured_media":124293,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[959],"tags":[],"views":"3468","authorinfo":{"name":"Vishalini Devarajan","url":"https:\/\/www.guvi.in\/blog\/author\/vishalini\/"},"thumbnailURL":"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2025\/08\/feature-300x116.webp","_links":{"self":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/85452"}],"collection":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/users\/63"}],"replies":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/comments?post=85452"}],"version-history":[{"count":22,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/85452\/revisions"}],"predecessor-version":[{"id":124953,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/posts\/85452\/revisions\/124953"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media\/124293"}],"wp:attachment":[{"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/media?parent=85452"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/categories?post=85452"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.guvi.in\/blog\/wp-json\/wp\/v2\/tags?post=85452"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}