{"id":5856,"date":"2025-03-25T14:56:17","date_gmt":"2025-03-25T14:56:17","guid":{"rendered":"https:\/\/www.goodcore.co.uk\/blog\/?p=5856"},"modified":"2025-07-04T07:15:29","modified_gmt":"2025-07-04T07:15:29","slug":"what-are-the-different-agile-methodologies","status":"publish","type":"post","link":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/","title":{"rendered":"What Are the Different Agile Methodologies?"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Agile has changed the way teams build software, making it more flexible, collaborative, and focused on customer needs.\u00a0<\/span><span style=\"font-weight: 400;\">But Agile isn\u2019t just one way of working, it\u2019s a set of principles that can be used in different ways to fit different teams and projects.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this post, we\u2019ll explore some of the most popular Agile methodologies, how they work, and when to use them. By the end, you\u2019ll have a better idea of which one might be right for your team.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">What is Agile software development?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">In <\/span><a href=\"https:\/\/www.goodcore.co.uk\/blog\/software-development-a-complete-guide\/\"><span style=\"font-weight: 400;\">software development<\/span><\/a><span style=\"font-weight: 400;\">, Agile is a set of principles that prioritise functionality, customer focus, flexibility, and responsiveness to change. Its origins can be traced back to 2001 when a group of software developers formed a more flexible approach to software development that could facilitate evolving requirements.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">They drafted the <\/span><a href=\"https:\/\/agilemanifesto.org\/\"><span style=\"font-weight: 400;\">Agile Manifesto<\/span><\/a><span style=\"font-weight: 400;\">, a document that outlines four key values and twelve principles that form the foundation of the Agile development life cycle. By utilising iterative and incremental development techniques, the Agile SDLC was designed to produce high-quality software quickly and efficiently by manifesting agile values and principles.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">The four key Agile values<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">These values emphasise a people-centric approach to software development, where delivering business value is the primary objective:\u00a0<\/span><\/p>\n<ol>\n<li><b>Individuals and interactions<\/b><span style=\"font-weight: 400;\"> over processes and tools.<\/span><\/li>\n<li><b>Working software<\/b><span style=\"font-weight: 400;\"> over comprehensive documentation.<\/span><\/li>\n<li><b>Customer collaboration<\/b><span style=\"font-weight: 400;\"> over contract negotiation.<\/span><\/li>\n<li><b>Responding to change<\/b><span style=\"font-weight: 400;\"> over following a plan.<\/span><\/li>\n<\/ol>\n<h3><span style=\"font-weight: 400;\">12 Agile principles<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Here are 12 essential principles that shape agile practices:<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-4614 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2024\/04\/agile-principles.jpg\" alt=\"\" width=\"800\" height=\"916\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2024\/04\/agile-principles.jpg 800w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2024\/04\/agile-principles-262x300.jpg 262w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2024\/04\/agile-principles-131x150.jpg 131w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2024\/04\/agile-principles-768x879.jpg 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">For more information on Agile SDLC, check out our blog: <\/span><a href=\"https:\/\/www.goodcore.co.uk\/blog\/agile-software-development-life-cycle-exploring-use-cases-phases-and-challenges\/\"><span style=\"font-weight: 400;\">What is Agile Software Development Life Cycle and how does it work?<\/span><\/a><\/p>\n<h2><span style=\"font-weight: 400;\">Why are there different Agile methodologies?<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Agile is a framework, not a single, rigid methodology. It provides a set of principles, like prioritising collaboration, customer feedback, and adaptability that teams can apply in various ways.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Different projects, teams, and industries have unique needs, so Agile methodologies were created to address this diversity.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">For example, Scrum is great for teams needing structured sprints, while Kanban focuses on continuous workflow management. By offering different approaches, Agile allows organisations to stay flexible and tailor their processes to fit specific goals, team sizes, and project complexities.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">These variations ensure that Agile principles can work for anything from software development to marketing campaigns, making it a versatile and dynamic framework.<\/span><\/p>\n<div style=\"text-align: center;\">\n<div class=\"cta-section\">\n<h3 class=\"cta-heading\">Bespoke Software That Adapts to Your Business<\/h3>\n<p class=\"cta-text\"><span style=\"font-weight: 400;\">Just like Agile, your software should be flexible, scalable, and built to evolve. Our bespoke solutions grow with your business needs.<\/span><br \/>\n<a class=\"cta-btn\" href=\"https:\/\/www.goodcore.co.uk\/services\/bespoke-software-development\/\" target=\"_blank\" rel=\"noopener\">Software development services<\/a><\/p>\n<\/div>\n<\/div>\n<h2><span style=\"font-weight: 400;\">Types of Agile methodologies<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">In this section, we will discuss the different types of Agile methodologies, how they work, and when to use them.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Scrum<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Scrum is one of the most popular Agile methodologies, and for good reason. It helps teams break work into small, manageable chunks, adapt to changes quickly, and deliver value at a steady pace.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Instead of trying to plan everything upfront, Scrum teams work in short, focused cycles called sprints, usually lasting two weeks. In a sprint, work moves forward through five key events:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sprint planning.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Daily scrum.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Implementation.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sprint review.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Sprint retrospective.<\/span><\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5857 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint.jpg\" alt=\"\" width=\"1669\" height=\"523\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint.jpg 1669w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint-300x94.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint-1024x321.jpg 1024w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint-150x47.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint-768x241.jpg 768w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/sprint-1536x481.jpg 1536w\" sizes=\"(max-width: 1669px) 100vw, 1669px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">When it comes to the team structure, a Scrum team is small but highly collaborative &#8211; usually no more than 10 people. Everyone has a clear role:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Product owner \u2013 defines what needs to be built, prioritises tasks, and keeps the product vision on track.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scrum master \u2013 coaches the team, removes roadblocks, and ensures Scrum practices are followed.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Development team \u2013 the people doing the actual work, designers, developers, and testers, who plan and deliver each sprint&#8217;s goals.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">In short, Scrum keeps teams focused without locking them into rigid plans. It is structured but flexible, allowing for constant learning and adjustment.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Kanban<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Kanban methodology is all about flow &#8211; keeping work moving smoothly without overwhelming the team. Instead of rigid sprints, like in Scrum, Kanban lets teams work continuously, focusing on what\u2019s in progress and what\u2019s blocking progress.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At the heart of Kanban is its visual approach. A Kanban board, either a physical whiteboard or a digital tool like Trello or Jira, maps out your work. Tasks are represented as cards and move through different stages often labelled as &#8220;To Do,&#8221; &#8220;In Progress,&#8221; and &#8220;Done.&#8221;\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This setup makes it easy to see what\u2019s happening at a glance and spot bottlenecks before they slow things down.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5858 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board.png\" alt=\"\" width=\"1848\" height=\"1136\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board.png 1848w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board-300x184.png 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board-1024x629.png 1024w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board-150x92.png 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board-768x472.png 768w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/kanban-board-1536x944.png 1536w\" sizes=\"(max-width: 1848px) 100vw, 1848px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Kanban operates on the following six key practices:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Make work visible \u2013 if you can see it, you can manage it. A clear workflow means fewer surprises and less chaos.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Limit work in progress (WIP) \u2013 too many tasks at once slow down the progress. Setting limits (e.g., only three tasks in &#8220;In Progress&#8221;) keeps the team focused and prevents overload.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Keep things moving \u2013 if tasks get stuck, identify why and fix the flow. Efficiency matters more than just being busy.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Be clear about how work gets done \u2013 define and communicate expectations so everyone understands the process.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Use feedback loops \u2013 regular check-ins, like quick stand-ups or retrospectives, help teams adapt and improve.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Evolve through small, steady improvements \u2013 change doesn\u2019t have to be drastic. Tweak, test, and refine over time.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">One of the biggest advantages of Kanban is flexibility. Since work is pulled in as capacity allows, rather than assigned in fixed batches, teams can adjust priorities on the fly. It\u2019s a great fit for teams handling unpredictable workloads or continuous delivery.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Scrumban<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Sometimes, one Agile approach alone isn\u2019t enough. Maybe you like Scrum\u2019s clear structure but find sprints too rigid. Or perhaps Kanban\u2019s flexibility appeals to you, but you still want some of Scrum\u2019s planning discipline.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Scrumban bridges that gap, blending Scrum\u2019s structure and Kanban\u2019s flexibility into one balanced method.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Rather than sticking to sprint cycles, teams using Scrumban pull tasks into their workflow as space becomes available, much like in Kanban. They still benefit from Scrum\u2019s clear roles and daily check-ins, but planning and review meetings become less formal, fitting naturally in your workflow.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Scrumban keeps the familiar visual board from Kanban, columns like To Do, In Progress, and Done, so everyone can quickly see progress and spot where tasks stall.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This hybrid approach works especially well if your team\u2019s workload constantly shifts or if you\u2019re transitioning from Scrum to a more fluid way of working. It gives you structure without rigidity to keep the team aligned without feeling constrained.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Extreme programming (XP)<\/span><\/h3>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5859 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Extreme-programming-process.jpg\" alt=\"\" width=\"800\" height=\"500\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Extreme-programming-process.jpg 800w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Extreme-programming-process-300x188.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Extreme-programming-process-150x94.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Extreme-programming-process-768x480.jpg 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Extreme programming, or XP, is all about writing high-quality software quickly while staying adaptable to change.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It\u2019s a developer-focused methodology that emphasises teamwork, continuous feedback, and delivering small, frequent updates.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Instead of long, drawn-out development cycles, XP encourages rapid iterations, ensuring customer needs are met at every step.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">XP operates on the following eight practices that guide its use:<\/span><\/p>\n<ol>\n<li><b> Test-driven development (TDD):<\/b><span style=\"font-weight: 400;\"> Developers write automated tests before writing the code itself. This ensures the code is functional and meets requirements from the start.\u00a0<\/span><\/li>\n<li><b> Pair programming:<\/b><span style=\"font-weight: 400;\"> Two developers work together on the same piece of code. One writes the code while the other reviews it in real-time. This practice improves code quality and reduces errors.<\/span><\/li>\n<li><b> Continuous integration:<\/b><span style=\"font-weight: 400;\"> Code changes are integrated frequently (often multiple times a day) into a shared repository. Automated tests are run after each integration to ensure new changes do not break existing functionality.<\/span><\/li>\n<li><b> Small releases:<\/b><span style=\"font-weight: 400;\"> XP emphasises releasing small, incremental updates to customers frequently. This approach ensures continuous delivery of value and allows for early feedback to guide development.<\/span><\/li>\n<li><b> Simple design:<\/b><span style=\"font-weight: 400;\"> XP encourages designing only what is necessary for the current iteration. This avoids over-engineering and ensures the system remains flexible to future changes.<\/span><\/li>\n<li><b> Refactoring:<\/b><span style=\"font-weight: 400;\"> Developers regularly revisit and improve existing code to enhance its structure, readability, and maintainability without altering its functionality.<\/span><\/li>\n<li><b> Onsite customer:<\/b><span style=\"font-weight: 400;\"> An actual customer or a representative is present with the team to provide immediate feedback and clarify requirements.\u00a0<\/span><\/li>\n<li><b> 40-hour workweek:<\/b><span style=\"font-weight: 400;\"> XP emphasises sustainable work practices, discouraging overtime to maintain team morale and productivity.<\/span><\/li>\n<\/ol>\n<h3><span style=\"font-weight: 400;\">Lean software development<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Lean software development is an Agile methodology inspired by Lean Manufacturing principles. It takes a no-nonsense approach to software development, focusing on what truly matters to customers and eliminating anything that doesn\u2019t.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">A key part of Lean is just-in-time development to keep things streamlined. Features are built only when they\u2019re actually needed, not months in advance. This avoids overproduction, reduces waste, and ensures resources go where they matter most.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5860 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/7-wastes-of-software-development.jpg\" alt=\"\" width=\"800\" height=\"616\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/7-wastes-of-software-development.jpg 800w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/7-wastes-of-software-development-300x231.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/7-wastes-of-software-development-150x116.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/7-wastes-of-software-development-768x591.jpg 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Lean embraces continuous delivery, breaking work into small, frequent updates so customers see improvements fast. Rather than piling on tasks and risking slowdowns, teams use a pull system, taking on new work only when they have the capacity to handle it. This keeps everything moving smoothly without overwhelming anyone.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Lean also thrives on empowered teams. Developers have the freedom to make decisions, solve problems, and improve processes on their own. This methodology works best for teams that need to move fast, stay flexible, and keep quality high.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Lean startup<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The lean startup methodology focuses on moving fast, testing ideas, and learning as you go. instead of spending months (or years) developing a product only to find out no one wants it, lean startup encourages teams to start small, get real feedback, and pivot or improve based on what actually works.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">At the heart of lean startup is the build-measure-learn feedback loop. Everything starts with a problem or an opportunity. Rather than assuming what customers want, teams define their key assumptions and build a minimum viable product (MVP), a simple version of the product designed to test those assumptions as quickly as possible.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Once the MVP is released, real users provide feedback through surveys, analytics, and interactions. If the data shows the idea works, the team improves and scales it. If not, they pivot, adjusting their strategy until they land on something that sticks. This cycle repeats until they achieve product-market fit, that sweet spot where the product perfectly aligns with customer needs.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5861 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Build-Measure-Learn-Loop.jpg\" alt=\"\" width=\"800\" height=\"609\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Build-Measure-Learn-Loop.jpg 800w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Build-Measure-Learn-Loop-300x228.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Build-Measure-Learn-Loop-150x114.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Build-Measure-Learn-Loop-768x585.jpg 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Lean Startup thrives in uncertain environments, where traditional planning just doesn\u2019t cut it. Startups use it to launch new products, but even established companies apply it when testing new ideas or entering unfamiliar markets. This methodology is all about learning fast and making smart moves before running out of time or money.<\/span><\/p>\n<div style=\"text-align: center;\">\n<div class=\"cta-section\">\n<h3 class=\"cta-heading\">Need a Scalable, High-Quality Product?<\/h3>\n<p class=\"cta-text\"><span style=\"font-weight: 400;\">With Agile at the core of our development process, we rapidly build, test, and refine your product to ensure market success.<\/span><br \/>\n<a class=\"cta-btn\" href=\"https:\/\/www.goodcore.co.uk\/services\/product-development\/\" target=\"_blank\" rel=\"noopener\">Learn more<\/a><\/p>\n<\/div>\n<\/div>\n<h3><span style=\"font-weight: 400;\">Feature-driven development (FDD)<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Feature-driven development is exactly what it sounds like &#8211; building software by focusing on small, meaningful features that deliver real value. Instead of trying to tackle an entire system at once, teams break projects into bite-sized, client-focused features, making progress more measurable, predictable, and structured.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Feature-driven development follows a structured five-step process:<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5862 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Feature-driven-development-process.jpg\" alt=\"\" width=\"800\" height=\"400\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Feature-driven-development-process.jpg 800w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Feature-driven-development-process-300x150.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Feature-driven-development-process-150x75.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/Feature-driven-development-process-768x384.jpg 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<ol>\n<li><b> Develop an overall model<\/b><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">At the start of the project, the team collaborates to create a domain model, which provides a high-level view of the system. This model serves as the foundation for the project\u2019s design and development.<\/span><\/p>\n<ol start=\"2\">\n<li><b> Build a features list<\/b><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">The team identifies and organises all the features that need to be developed. Features are small, client-valued functions, typically written in a simple format like: \u201c&lt;action&gt; the &lt;result&gt; &lt;by\/for\/from&gt; a &lt;object&gt;.\u201d<\/span><\/p>\n<ol start=\"3\">\n<li><b> Plan by feature<\/b><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">The team prioritises and schedules the features, organising them into a sequence of short development cycles.<\/span><\/p>\n<ol start=\"4\">\n<li><b> Design by feature<\/b><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">For each feature, a detailed design is created. This step involves collaboration between developers, architects, and domain experts to ensure the design aligns with the overall model and business requirements.<\/span><\/p>\n<ol start=\"5\">\n<li><b> Build by feature<\/b><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">Developers implement the feature based on the design, adhering to coding standards and best practices. The feature is tested and integrated into the system once complete.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">FDD works best for large, complex projects where a strong framework is needed to keep everything on track. One of the biggest advantages? Clear visibility. Since work is tracked feature by feature, teams and stakeholders always know what\u2019s done and what\u2019s coming next. This makes FDD a great fit for teams that need structure without being too rigid, offering just the right balance of planning and flexibility.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Rapid application development (RAD)<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">If speed is the priority, rapid application development is the way to go. Instead of spending months planning every detail before writing a single line of code, RAD jumps straight into building prototypes. The goal? Create something tangible, gather feedback fast, and refine it until it\u2019s right.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">RAD thrives on prototyping &#8211; teams quickly build working models of the application to test ideas early. Users get hands-on experience with these prototypes, providing immediate feedback so developers can tweak and improve features before committing to a final version. This cycle of iterative development keeps things flexible, each version builds on the last, ensuring the product evolves in the right direction.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5451 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/Rapid-application-development-RAD-model.jpg\" alt=\"RAD model\" width=\"1200\" height=\"531\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/Rapid-application-development-RAD-model.jpg 1200w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/Rapid-application-development-RAD-model-300x133.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/Rapid-application-development-RAD-model-1024x453.jpg 1024w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/Rapid-application-development-RAD-model-150x66.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/Rapid-application-development-RAD-model-768x340.jpg 768w\" sizes=\"(max-width: 1200px) 100vw, 1200px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Unlike traditional methods, where user input often comes too late, RAD keeps end users involved from start to finish. Their feedback shapes the product in real-time, making sure it actually meets their needs rather than forcing changes after launch.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">This approach works best for projects with tight deadlines, evolving requirements, or a strong need for user-driven development. It\u2019s especially useful for web and mobile applications, where rapid testing and iteration lead to better user experiences.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Adaptive software development (ASD)<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">When requirements are constantly shifting, rigid planning just doesn\u2019t work. Adaptive software development is built for uncertainty, focusing on flexibility, teamwork, and continuous learning instead of sticking to a fixed roadmap.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">ASD is guided by three core principles:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Speculate \u2013 instead of locking down a detailed plan upfront, teams make informed assumptions about the project\u2019s direction. Development starts with the expectation that things will evolve, not stay the same.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Collaborate \u2013 success depends on constant communication between developers, stakeholders, and customers. The more closely everyone works together, the faster issues are solved and ideas are refined.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Learn \u2013 every iteration is an opportunity to improve. Teams gather feedback, adjust their approach, and fine-tune both the product and the process to better meet user needs.<\/span><\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-5863 size-full\" src=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/ASD.jpg\" alt=\"\" width=\"800\" height=\"653\" srcset=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/ASD.jpg 800w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/ASD-300x245.jpg 300w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/ASD-150x122.jpg 150w, https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/ASD-768x627.jpg 768w\" sizes=\"(max-width: 800px) 100vw, 800px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">At the heart of ASD is iterative development and continuous feedback. Instead of waiting until the end to deliver a finished product, teams release small, functional increments in short cycles.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Feedback loops play a critical role, allowing developers to learn from stakeholders, users, and even the system itself. This constant flow of feedback helps teams refine their work, adjust priorities, and quickly respond to evolving requirements.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Agile modeling<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Agile modeling is a flexible and lightweight approach to software development that focuses on creating models and documentation while keeping the process simple, fast, and collaborative.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Unlike traditional, rigid modeling methods that demand heavy documentation before development begins, Agile modeling embraces change and adapts to evolving project needs.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">It follows Agile principles, meaning teams prioritise working software over excessive paperwork, value collaboration over rigid processes, and respond to change quickly rather than sticking to a fixed plan.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Agile modeling isn&#8217;t a standalone methodology but a set of best practices that support Agile development frameworks like Scrum, Kanban, or XP. It encourages just-in-time modeling, where teams create diagrams, sketches, and documentation only when needed, ensuring they remain relevant and useful.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Some common types of models used in agile modeling include:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User stories \u2013 simple, written descriptions of a feature or requirement from the user&#8217;s perspective.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Diagrams \u2013 visual representations such as flowcharts, class diagrams, or sequence diagrams to illustrate system behavior or design.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Wireframes and mockups \u2013 low-fidelity sketches that represent the user interface or application structure.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Domain models \u2013 conceptual representations of the business domain, including entities and relationships.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Architecture models \u2013 high-level diagrams that outline the system\u2019s structure and components.<\/span><\/li>\n<\/ul>\n<h3><span style=\"font-weight: 400;\">Disciplined agile delivery (DAD)<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Agile works great for small teams, but what happens when you\u2019re dealing with large projects, enterprise systems, or strict governance requirements? That\u2019s where disciplined agile delivery comes in.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">DAD is a flexible framework that extends Agile principles to the entire delivery process, including architecture, DevOps, and operations. DAD follows three main phases:<\/span><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Inception \u2013 The team lays the groundwork, defining the project\u2019s goals, scope, stakeholders, and risks. This phase ensures everyone is aligned before development begins.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Construction \u2013 The real work happens here. Teams build, test, and refine the product in short cycles, constantly incorporating feedback to stay on track.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transition \u2013 Once the product is ready, it\u2019s time to deploy, train users, and ensure everything runs smoothly in production.<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400;\">So how DAD differs from Agile? Traditional Agile frameworks like Scrum and Kanban provide lightweight structures, but they mainly focus on software development rather than the entire delivery process.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Disciplined agile delivery takes Agile beyond development. It provides a structured framework that covers the entire lifecycle of a project, including architecture, DevOps, governance, and deployment.\u00a0<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Feature<\/b><\/td>\n<td><b>Agile\u00a0<\/b><\/td>\n<td><b>Disciplined Agile Delivery (DAD)<\/b><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Focus<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Primarily software development within a project<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Entire enterprise solution delivery lifecycle<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Nature<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Framework with defined processes<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Toolkit with adaptable practices<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Scope<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Project-level<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Enterprise-level<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Scaling<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Can require additional frameworks for scaling<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Built-in guidance for scaling<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Flexibility<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Relatively structured<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Highly adaptable and context-driven<\/span><\/td>\n<\/tr>\n<tr>\n<td><span style=\"font-weight: 400;\">Gaps adressed<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Can leave gaps in enterprise level concerns<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Fills in the gaps that traditional agile methods leave behind<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span style=\"font-weight: 400;\">Dynamic systems development method (DSDM)<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Dynamic systems development method is a software development approach that blends the flexibility of Agile with strong governance, making it a go-to choice for projects in corporate or highly regulated environments.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Instead of just focusing on software, DSDM ensures that every project aligns with real business needs and delivers measurable value. At its core, DSDM follows a few key principles:<\/span><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Business first \u2013 every project must serve a clear business purpose and deliver tangible value.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time matters \u2013 work is timeboxed, meaning deadlines are fixed, and features are prioritised to ensure delivery stays on track.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Collaboration is key \u2013 teams, stakeholders, and users work closely together to keep things aligned and moving efficiently.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Quality isn\u2019t optional \u2013 high standards are built into the process, ensuring reliable, effective solutions.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Stay in control \u2013 defined roles and governance ensure accountability and keep projects on track.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-weight: 400;\">DSDM is ideal for large-scale or complex projects where stakeholder involvement and structured feedback loops are critical. It\u2019s perfect for teams that need Agile flexibility but also strong oversight, ensuring projects don\u2019t just move fast, they move in the right direction.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Key factors to consider when choosing an Agile methodology<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">As you\u2019ve seen by now, not all Agile frameworks are one-size-fits-all. Selecting the right methodology requires understanding your team\u2019s unique needs, project requirements, and organisational goals. Below are key factors to consider when making your choice.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Team size<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The size of your team influences how communication, coordination, and decision-making are managed. Smaller teams often thrive in environments with direct communication and minimal structure. Larger teams or those spread across multiple locations require more structured approaches to ensure consistency and collaboration. Understanding how your team size impacts workflow and communication can help you choose a methodology that promotes efficiency.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Project complexity and timeline<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The level of complexity in your project determines how much structure and planning are necessary. Complex projects with multiple dependencies may require detailed planning and rigorous management to reduce risks and ensure alignment. On the other hand, projects with tight deadlines or evolving goals benefit from methodologies that prioritise adaptability and rapid delivery.\u00a0<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Stakeholder involvement<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The degree of stakeholder involvement needed during the project lifecycle can impact the choice of methodology. Projects that require frequent feedback and close collaboration with stakeholders need processes that facilitate regular communication. On the contrary, if stakeholders are less involved or only need periodic updates, a methodology with less dependency on their active participation may be more effective.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Level of uncertainty<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Projects with uncertain or rapidly changing requirements need approaches that emphasise adaptability and iterative development. Early feedback and continuous refinement help navigate ambiguity and ensure alignment with evolving goals. For projects with stable and well-defined requirements, more structured approaches that focus on predictability may be more effective.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Organisational culture<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The organisation\u2019s culture and mindset play a critical role in determining the right methodology. Agile thrives in environments that encourage collaboration, trust, and empowerment. Organisations with a more hierarchical or process-driven culture may require methods that balance agility with governance to integrate seamlessly into existing practices. Assessing the cultural readiness for Agile can significantly influence the success of its implementation.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Industry and domain requirements<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Certain industries have unique challenges, such as regulatory compliance, safety standards, or market volatility. The nature of the industry or domain often dictates whether a lightweight and flexible approach is feasible or whether a more robust and structured process is required. Projects in regulated industries may need methodologies that ensure documentation and compliance, while innovation-driven domains may prioritise speed and adaptability.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Team expertise and maturity<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">The experience level of the team significantly affects how well they can adapt to an Agile approach. Teams with less Agile experience may benefit from methodologies that provide clear roles, guidelines, and processes to follow. Experienced and self-organising teams, on the other hand, may excel with more flexible approaches that give them autonomy to make decisions and optimise their workflow.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Resource availability<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">Resource constraints, including budget, time, and tools, influence the choice of methodology. Teams working with limited resources may need to prioritise methods that maximise efficiency and focus on delivering the most value with minimal waste. The availability of technology and tools to support Agile practices, such as task management or automated testing, also plays a role in effective implementation.<\/span><\/p>\n<h3><span style=\"font-weight: 400;\">Scalability needs<\/span><\/h3>\n<p><span style=\"font-weight: 400;\">For projects that involve multiple teams or need to scale across an organisation, the chosen methodology must support scalability. The ability to coordinate work across teams, manage dependencies, and ensure alignment becomes critical in larger projects. Identifying whether the project or organisation requires a methodology suitable for scaling Agile practices can guide your decision.<\/span><\/p>\n<h2><span style=\"font-weight: 400;\">Agile methodologies comparison table<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Here\u2019s a comparison table for different Agile methodologies discussed above. You can explore and analyse the table to understand how each methodology aligns with different factors.<\/span><\/p>\n<table>\n<tbody>\n<tr>\n<td><b>Methodology<\/b><\/td>\n<td><b>Best For<\/b><\/td>\n<td><b>Team size<\/b><\/td>\n<td><b>Complexity<\/b><\/td>\n<td><b>Timeline flexibility<\/b><\/td>\n<td><b>Scalability<\/b><\/td>\n<\/tr>\n<tr>\n<td><b>Scrum<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Teams needing structured sprints<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Small to medium<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate to high<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Fixed-length sprints<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Limited<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Kanban<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Continuous workflow management<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Any size<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate to low<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Flexible<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Scrumban<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Hybrid of Scrum &amp; Kanban<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Any size<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Flexible<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Extreme Programming (XP)<\/b><\/td>\n<td><span style=\"font-weight: 400;\">High-quality software dev teams<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Small to medium<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate to high<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Short iterations<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Limited<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Lean Software Development<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Reducing waste, improving flow<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Any size<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Flexible<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Lean Startup<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Startups testing new ideas<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Small to medium<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Short cycles<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Limited<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Feature-Driven Development (FDD)<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Large projects with clear features<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Medium to large<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Defined but iterative<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Rapid Application Development (RAD)<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Fast prototyping &amp; quick delivery<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Small to medium<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Rapid<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Adaptive Software Development (ASD)<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Highly flexible &amp; evolving projects<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Medium to large<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Flexible<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Agile Modeling<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Teams needing lightweight planning<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Any size<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate to high<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Flexible<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Moderate<\/span><\/td>\n<\/tr>\n<tr>\n<td><b>Disciplined Agile Delivery (DAD)<\/b><\/td>\n<td><span style=\"font-weight: 400;\">Large enterprises needing structure<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Medium to large<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<td><span style=\"font-weight: 400;\">Flexible<\/span><\/td>\n<td><span style=\"font-weight: 400;\">High<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span style=\"font-weight: 400;\">TL;DR<\/span><\/h3>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If you need structure and clear roles, Scrum and FDD are good choices.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If flexibility is your priority, consider Kanban, Scrumban, or ASD.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">For rapid delivery and prototyping, RAD and Lean Startup work best.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">For large, scalable teams, DAD and FDD are excellent.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">If quality and engineering practices are key, XP is the way to go.<\/span><\/li>\n<\/ul>\n<h2><span style=\"font-weight: 400;\">Final thoughts<\/span><\/h2>\n<p><span style=\"font-weight: 400;\">Agile isn\u2019t a one-size-fits-all solution. With so many methodologies out there, understanding their differences is key to choosing the right one for your team and project. Each approach has its own strengths, and sometimes, a little experimentation is the best way to find what works.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">If you\u2019re ready to embrace Agile practices and drive success in your projects, GoodCore Software is here to help. Our team specialise in implementing Agile practices to streamline software development and deliver exceptional results.<\/span><\/p>\n<div style=\"text-align: center;\">\n<div class=\"cta-section\">\n<p class=\"cta-text\"><span style=\"font-weight: 400;\">Contact us today to learn how we can support your bespoke software development needs.<\/span><br \/>\n<a class=\"cta-btn\" href=\"https:\/\/www.goodcore.co.uk\/contact\/\" target=\"_blank\" rel=\"noopener\">Book a consultation<\/a><\/p>\n<\/div>\n<h2 style=\"text-align: left;\">FAQs<\/h2>\n<h3 style=\"text-align: left;\">What\u2019s better for MVP development: Waterfall or Agile?<\/h3>\n<p style=\"text-align: left;\">Agile is generally the better choice for MVP development, especially for startups and fast-moving projects. Unlike the rigid, step-by-step Waterfall approach, Agile allows for iterative development, quick feedback loops, and flexibility to adapt as new insights emerge. Most MVP agencies prefer Agile because it supports faster launches, continuous improvement, and better alignment with evolving business needs.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Agile has changed the way teams build software, making it more flexible, collaborative, and focused on customer needs.\u00a0But Agile isn\u2019t just one way of working, it\u2019s a set of principles that can be used in different ways to fit different teams and projects.\u00a0 In this post, we\u2019ll explore some of the most popular Agile methodologies, [&hellip;]<\/p>\n","protected":false},"author":22,"featured_media":5864,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[104],"tags":[],"class_list":{"0":"post-5856","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-software-development"},"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v25.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>What are the Different Agile Methodologies? A Comprehensive Guide<\/title>\n<meta name=\"description\" content=\"Learn more about key Agile methodologies, their differences, and how to choose the right one for your project&#039;s needs in this simple, practical guide.\" \/>\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.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What are the Different Agile Methodologies? A Comprehensive Guide\" \/>\n<meta property=\"og:description\" content=\"Learn more about key Agile methodologies, their differences, and how to choose the right one for your project&#039;s needs in this simple, practical guide.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\" \/>\n<meta property=\"og:site_name\" content=\"GoodCore Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-03-25T14:56:17+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-04T07:15:29+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1440\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Inamullah Khan\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Inamullah Khan\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\"},\"author\":{\"name\":\"Inamullah Khan\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/person\/b51c4e63a6f339dce86539b303eca16f\"},\"headline\":\"What Are the Different Agile Methodologies?\",\"datePublished\":\"2025-03-25T14:56:17+00:00\",\"dateModified\":\"2025-07-04T07:15:29+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\"},\"wordCount\":4024,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg\",\"articleSection\":[\"Software Development\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\",\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\",\"name\":\"What are the Different Agile Methodologies? A Comprehensive Guide\",\"isPartOf\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg\",\"datePublished\":\"2025-03-25T14:56:17+00:00\",\"dateModified\":\"2025-07-04T07:15:29+00:00\",\"description\":\"Learn more about key Agile methodologies, their differences, and how to choose the right one for your project's needs in this simple, practical guide.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage\",\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg\",\"contentUrl\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg\",\"width\":2560,\"height\":1440},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Blog\",\"item\":\"https:\/\/www.goodcore.co.uk\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What Are the Different Agile Methodologies?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#website\",\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/\",\"name\":\"GoodCore Blog\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.goodcore.co.uk\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#organization\",\"name\":\"GoodCore Software Ltd\",\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2019\/08\/goodcore_logo.jpg\",\"contentUrl\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2019\/08\/goodcore_logo.jpg\",\"width\":313,\"height\":54,\"caption\":\"GoodCore Software Ltd\"},\"image\":{\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/person\/b51c4e63a6f339dce86539b303eca16f\",\"name\":\"Inamullah Khan\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/inam-105x105.png\",\"contentUrl\":\"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/inam-105x105.png\",\"caption\":\"Inamullah Khan\"},\"description\":\"Inamullah Khan is a seasoned IT professional in the technology industry. With a keen eye for detail and a strong analytical mindset, he excels as a business analyst and product owner, bridging the gap between technical teams and business objectives to deliver impactful software solutions. His expertise spans custom software development, product strategy, and aligning technology with business goals to drive innovation. Over the years, Inamullah has played a pivotal role in shaping successful products, from conceptualization to launch, ensuring they meet user needs while achieving business objectives. A tech enthusiast at heart, Inamullah is passionate about exploring the latest industry trends, staying ahead of the curve in an ever-evolving field.\",\"sameAs\":[\"https:\/\/www.linkedin.com\/in\/inamullah\/\"],\"url\":\"https:\/\/www.goodcore.co.uk\/blog\/author\/inamullah\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"What are the Different Agile Methodologies? A Comprehensive Guide","description":"Learn more about key Agile methodologies, their differences, and how to choose the right one for your project's needs in this simple, practical guide.","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.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/","og_locale":"en_GB","og_type":"article","og_title":"What are the Different Agile Methodologies? A Comprehensive Guide","og_description":"Learn more about key Agile methodologies, their differences, and how to choose the right one for your project's needs in this simple, practical guide.","og_url":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/","og_site_name":"GoodCore Blog","article_published_time":"2025-03-25T14:56:17+00:00","article_modified_time":"2025-07-04T07:15:29+00:00","og_image":[{"width":2560,"height":1440,"url":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg","type":"image\/jpeg"}],"author":"Inamullah Khan","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Inamullah Khan","Estimated reading time":"20 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#article","isPartOf":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/"},"author":{"name":"Inamullah Khan","@id":"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/person\/b51c4e63a6f339dce86539b303eca16f"},"headline":"What Are the Different Agile Methodologies?","datePublished":"2025-03-25T14:56:17+00:00","dateModified":"2025-07-04T07:15:29+00:00","mainEntityOfPage":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/"},"wordCount":4024,"commentCount":0,"publisher":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/#organization"},"image":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage"},"thumbnailUrl":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg","articleSection":["Software Development"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/","url":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/","name":"What are the Different Agile Methodologies? A Comprehensive Guide","isPartOf":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage"},"image":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage"},"thumbnailUrl":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg","datePublished":"2025-03-25T14:56:17+00:00","dateModified":"2025-07-04T07:15:29+00:00","description":"Learn more about key Agile methodologies, their differences, and how to choose the right one for your project's needs in this simple, practical guide.","breadcrumb":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/"]}]},{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#primaryimage","url":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg","contentUrl":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/03\/agile-methodologies-scaled.jpg","width":2560,"height":1440},{"@type":"BreadcrumbList","@id":"https:\/\/www.goodcore.co.uk\/blog\/what-are-the-different-agile-methodologies\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Blog","item":"https:\/\/www.goodcore.co.uk\/blog\/"},{"@type":"ListItem","position":2,"name":"What Are the Different Agile Methodologies?"}]},{"@type":"WebSite","@id":"https:\/\/www.goodcore.co.uk\/blog\/#website","url":"https:\/\/www.goodcore.co.uk\/blog\/","name":"GoodCore Blog","description":"","publisher":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.goodcore.co.uk\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":"Organization","@id":"https:\/\/www.goodcore.co.uk\/blog\/#organization","name":"GoodCore Software Ltd","url":"https:\/\/www.goodcore.co.uk\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2019\/08\/goodcore_logo.jpg","contentUrl":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2019\/08\/goodcore_logo.jpg","width":313,"height":54,"caption":"GoodCore Software Ltd"},"image":{"@id":"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/person\/b51c4e63a6f339dce86539b303eca16f","name":"Inamullah Khan","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/www.goodcore.co.uk\/blog\/#\/schema\/person\/image\/","url":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/inam-105x105.png","contentUrl":"https:\/\/www.goodcore.co.uk\/blog\/wp-content\/uploads\/2025\/01\/inam-105x105.png","caption":"Inamullah Khan"},"description":"Inamullah Khan is a seasoned IT professional in the technology industry. With a keen eye for detail and a strong analytical mindset, he excels as a business analyst and product owner, bridging the gap between technical teams and business objectives to deliver impactful software solutions. His expertise spans custom software development, product strategy, and aligning technology with business goals to drive innovation. Over the years, Inamullah has played a pivotal role in shaping successful products, from conceptualization to launch, ensuring they meet user needs while achieving business objectives. A tech enthusiast at heart, Inamullah is passionate about exploring the latest industry trends, staying ahead of the curve in an ever-evolving field.","sameAs":["https:\/\/www.linkedin.com\/in\/inamullah\/"],"url":"https:\/\/www.goodcore.co.uk\/blog\/author\/inamullah\/"}]}},"_links":{"self":[{"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/posts\/5856"}],"collection":[{"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=5856"}],"version-history":[{"count":4,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/posts\/5856\/revisions"}],"predecessor-version":[{"id":6205,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/posts\/5856\/revisions\/6205"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/media\/5864"}],"wp:attachment":[{"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=5856"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=5856"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.goodcore.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=5856"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}