{"id":1431,"date":"2026-02-25T10:41:35","date_gmt":"2026-02-25T10:41:35","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/"},"modified":"2026-02-25T10:41:35","modified_gmt":"2026-02-25T10:41:35","slug":"agile-manifesto-explained-origins-beginners","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/","title":{"rendered":"The Origins of Agile: From Manifesto to Modern Practices"},"content":{"rendered":"<p>What if the most powerful shift in software development wasn\u2019t driven by technology, but by people? That\u2019s the truth behind the Agile Manifesto. When I first encountered it, I was skeptical\u2014how could a document with just four values and twelve principles reshape the way teams build software?<\/p>\n<p>After two decades working across industries, guiding teams through transformation, I\u2019ve seen that Agile isn\u2019t a process. It\u2019s a mindset. The Agile Manifesto wasn\u2019t born in a boardroom. It emerged from a group of practitioners tired of rigid, bureaucratic methods that failed to deliver value quickly.<\/p>\n<p>This chapter walks you through the real history of Agile Manifesto, not as a historical artifact, but as a living framework for teams. You\u2019ll learn how its principles evolved from early software projects into modern Scrum, and how you can apply them\u2014even in non-software environments.<\/p>\n<p>By the end, you\u2019ll understand not just what the Agile Manifesto says, but why it matters. You\u2019ll be able to recognize Agile origins for beginners and apply them with confidence, clarity, and authenticity.<\/p>\n<h2>What Is the Agile Manifesto?<\/h2>\n<p>Formally introduced in 2001, the Agile Manifesto was created by 17 software development leaders during a meeting in Utah. Their goal? To articulate a better way to build software\u2014one that emphasized collaboration, adaptability, and real customer value.<\/p>\n<p>They didn\u2019t produce a new tool. They didn\u2019t invent a new framework. They wrote a set of values. And that simple act changed everything.<\/p>\n<p>The four core values are:<\/p>\n<ul>\n<li><strong>Individuals and interactions<\/strong> over processes and tools<\/li>\n<li><strong>Working software<\/strong> over comprehensive documentation<\/li>\n<li><strong>Customer collaboration<\/strong> over contract negotiation<\/li>\n<li><strong>Responding to change<\/strong> over following a plan<\/li>\n<\/ul>\n<p>These aren\u2019t abstract ideals. They were born from frustration. Teams were delivering documentation that no one read. They followed plans that didn\u2019t account for reality. They built features customers didn\u2019t want. The Manifesto was a direct response to that.<\/p>\n<p>When you hear \u201cAgile,\u201d you\u2019re really hearing about this philosophy. It\u2019s not about ceremonies or tools. It\u2019s about people solving real problems, together, in real time.<\/p>\n<h2>Why the Agile Manifesto Still Matters Today<\/h2>\n<p>Decades after its creation, the values still resonate. Why? Because they reflect the reality of complex work. No matter your field\u2014product development, marketing, operations\u2014people face uncertainty, changing needs, and feedback loops.<\/p>\n<p>Even if your team isn\u2019t building software, the principles apply. The key is not the domain, but the mindset: transparency, adaptability, and continuous improvement.<\/p>\n<p>The Manifesto doesn\u2019t tell you how to run a sprint or what a backlog should look like. But it tells you what matters: <em>people, collaboration, delivery, and responsiveness.<\/em> That\u2019s the foundation.<\/p>\n<h3>Real-World Context: The Birth of Agile<\/h3>\n<p>Before Agile, most software development followed the Waterfall model\u2014linear, phase-by-phase, with no feedback until the end. That meant months of work could go to waste if requirements changed.<\/p>\n<p>By the 1990s, teams were trying alternatives: extreme programming (XP), Scrum, DSDM, and others. Each had unique practices, but they shared one thing: a focus on iteration, feedback, and people.<\/p>\n<p>When the 17 pioneers met in 2001, they weren\u2019t creating a new method. They were recognizing patterns. They asked: \u201cWhat do these approaches have in common?\u201d The answer became the Manifesto.<\/p>\n<p>It wasn\u2019t about replacing one framework with another. It was about acknowledging that the best results come from adaptive processes, not rigid plans.<\/p>\n<h2>The 12 Agile Principles: More Than Just a List<\/h2>\n<p>While the four values are concise, the 12 principles expand them into actionable guidance. They\u2019re not optional. They\u2019re the blueprint for how a team works.<\/p>\n<p>Here are the most impactful principles, distilled with real-world meaning:<\/p>\n<ol>\n<li><strong>Customer satisfaction through early delivery<\/strong> \u2013 Deliver value early and often. A working product is better than a perfect plan.<\/li>\n<li><strong>Welcome changing requirements<\/strong> \u2013 Change is inevitable. The best teams adapt quickly without blame or delay.<\/li>\n<li><strong>Deliver working software frequently<\/strong> \u2013 Short cycles mean faster feedback. Teams that release every two weeks learn faster than those waiting six months.<\/li>\n<li><strong>Business and developers work together daily<\/strong> \u2013 No silos. The Product Owner and developers must collaborate constantly.<\/li>\n<li><strong>Build projects around motivated individuals<\/strong> \u2013 Trust your team. Support them with autonomy, resources, and respect.<\/li>\n<li><strong>Face-to-face conversation is best<\/strong> \u2013 In-person syncs reduce misunderstandings. Remote teams must prioritize clarity and empathy.<\/li>\n<li><strong>Working software is the primary measure of progress<\/strong> \u2013 Progress isn\u2019t hours logged. It\u2019s value delivered.<\/li>\n<li><strong>Sustainable pace<\/strong> \u2013 Teams can\u2019t burn out and still deliver. Protect their energy.<\/li>\n<li><strong>Continuous attention to technical excellence<\/strong> \u2013 Clean code, good design, and automated testing are not optional\u2014they\u2019re essential.<\/li>\n<li><strong>Simplicity<\/strong> \u2013 Focus on what\u2019s essential. Avoid over-engineering.<\/li>\n<li><strong>Self-organizing teams<\/strong> \u2013 Let teams decide how to do their work. The Scrum Master facilitates, not controls.<\/li>\n<li><strong>Regular reflection and adaptation<\/strong> \u2013 Review how you work. Improve incrementally.<\/li>\n<\/ol>\n<p>These principles aren\u2019t just theory. I\u2019ve seen teams fail when they ignore <em>Principle #8: sustainable pace<\/em>. Teams overcommit, burn out, and deliver nothing of quality. When they apply it, the results are immediate: better morale, faster delivery, and higher trust.<\/p>\n<h2>From Manifesto to Modern Practices: How Agile Evolved<\/h2>\n<p>The Agile Manifesto didn\u2019t create Scrum. But it provided the philosophical foundation for it to thrive.<\/p>\n<p>Scrum emerged as a response to the same problems\u2014complexity, unclear requirements, team dependency. Its events, artifacts, and roles are practical implementations of the Manifesto\u2019s values.<\/p>\n<p>Here\u2019s how the evolution unfolded:<\/p>\n<table border=\"1\" cellpadding=\"4\" cellspacing=\"0\">\n<tbody>\n<tr>\n<th>Timeline<\/th>\n<th>Key Event<\/th>\n<th>Impact on Agile<\/th>\n<\/tr>\n<tr>\n<td>1986<\/td>\n<td>Highsmith introduces iterative development<\/td>\n<td>Laid groundwork for adaptive methods<\/td>\n<\/tr>\n<tr>\n<td>1997<\/td>\n<td>First Scrum Guide published<\/td>\n<td>Provided first formal framework for Agile<\/td>\n<\/tr>\n<tr>\n<td>2001<\/td>\n<td>Agile Manifesto signed<\/td>\n<td>Unified diverse Agile practices under shared values<\/td>\n<\/tr>\n<tr>\n<td>2002<\/td>\n<td>First PSM certification<\/td>\n<td>Began formal validation of Agile knowledge<\/td>\n<\/tr>\n<tr>\n<td>2011\u20132020<\/td>\n<td>Scrum Guide updates (2011, 2017, 2020)<\/td>\n<td>Refined roles, events, and principles for modern use<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The Manifesto didn\u2019t replace Waterfall. It offered an alternative for teams working in uncertain environments. And Scrum, with its time-boxed sprints and empirical process control, became the most popular implementation of that alternative.<\/p>\n<p>But here\u2019s a truth many miss: Scrum is not Agile. Scrum is a *framework* that enables Agile. You can use Scrum without being Agile, but you can\u2019t be truly Agile without a framework like Scrum\u2014or Kanban, or SAFe, depending on scale.<\/p>\n<h2>Agile Origins for Beginners: The Real Story<\/h2>\n<p>When someone says &#8220;Agile,&#8221; they often mean &#8220;Scrum.&#8221; But the roots run deeper. The Agile Manifesto was a catalyst, not a starting point.<\/p>\n<p>Consider this: the values weren\u2019t created in a vacuum. They reflect years of practice in small, empowered teams who had learned the hard way: changing requirements aren\u2019t a flaw. They\u2019re a feature of complex work.<\/p>\n<p>Agile origins for beginners aren\u2019t about memorizing a list. They\u2019re about understanding that:<\/p>\n<ul>\n<li>Uncertainty is normal, not a failure<\/li>\n<li>Feedback drives improvement<\/li>\n<li>Trust and collaboration beat command and control<\/li>\n<li>Progress is measured by working outcomes, not hours spent<\/li>\n<\/ul>\n<p>These aren\u2019t new ideas. They\u2019ve been practiced for decades\u2014just not in formal, documented ways. The Manifesto simply gave them a name.<\/p>\n<p>That\u2019s why the history of Agile Manifesto matters. It reminds us that Agile isn\u2019t a trend. It\u2019s a return to human-centered development.<\/p>\n<h2>Agile Manifesto vs. Scrum: How They Connect<\/h2>\n<p>Scrum is the framework. The Agile Manifesto is the philosophy.<\/p>\n<p>Every Scrum event\u2014Sprint Planning, Daily Scrum, Sprint Review, Retrospective\u2014is a practical expression of one or more Agile principles.<\/p>\n<p>For example:<\/p>\n<ul>\n<li><strong>Daily Scum<\/strong> supports <em>Face-to-face conversation<\/em> and <em>Continuous attention to technical excellence<\/em>.<\/li>\n<li><strong>Sprint Review<\/strong> embodies <em>Customer collaboration<\/em> and <em>Working software<\/em>.<\/li>\n<li><strong>Retrospective<\/strong> reflects <em>Regular reflection and adaptation<\/em>.<\/li>\n<\/ul>\n<p>Scrum doesn\u2019t replace the Manifesto. It makes it real.<\/p>\n<p>When your team runs a sprint and delivers a working feature, that\u2019s the Manifesto in action. When a developer asks, \u201cDoes this meet the Definition of Done?\u201d\u2014that\u2019s a question rooted in <em>technical excellence<\/em>.<\/p>\n<h2>Common Misconceptions About the Agile Manifesto<\/h2>\n<p>Let\u2019s clear up a few myths:<\/p>\n<ul>\n<li><strong>Myth: Agile means no documentation.<\/strong><br \/>Reality: Agile values <em>working software over comprehensive documentation<\/em>. It doesn\u2019t eliminate documentation. It prioritizes deliverables.<\/li>\n<li><strong>Myth: Agile is only for software teams.<\/strong><br \/>Reality: The principles apply to any complex, adaptive work\u2014marketing, HR, product design, operations.<\/li>\n<li><strong>Myth: Agile is chaotic.<\/strong><br \/>Reality: It\u2019s the opposite. Agile embraces structure\u2014but it\u2019s flexible structure. Scrum\u2019s time-boxing and transparency prevent chaos.<\/li>\n<li><strong>Myth: You must follow the Manifesto exactly.<\/strong><br \/>Reality: It\u2019s a guide, not a rulebook. The values are meant to be interpreted and adapted.<\/li>\n<\/ul>\n<p>Agile isn\u2019t about doing everything differently. It\u2019s about doing the right things\u2014better.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What is the Agile Manifesto in simple terms?<\/h3>\n<p>The Agile Manifesto is a set of values that prioritize people, collaboration, working solutions, and adaptability over rigid processes, documentation, contracts, and fixed plans. It\u2019s a philosophy for building better products through teamwork and feedback.<\/p>\n<h3>Why was the Agile Manifesto created?<\/h3>\n<p>It was created to counter the inefficiencies of traditional project management, especially in software development. Teams were spending months building features that customers didn\u2019t want. The Manifesto offered a new way: iterate fast, deliver early, and adapt to change.<\/p>\n<h3>Is Scrum the same as the Agile Manifesto?<\/h3>\n<p>No. Scrum is a framework. The Agile Manifesto is a guiding philosophy. You can practice Scrum without being Agile, but true Agile requires the mindset behind the Manifesto.<\/p>\n<h3>How can I apply the Agile Manifesto in my daily work?<\/h3>\n<p>Ask yourself: am I focusing on people and collaboration? Am I delivering working results? Am I open to change? If yes, you\u2019re already applying the Manifesto.<\/p>\n<h3>Did the Agile Manifesto replace Waterfall?<\/h3>\n<p>No. The Manifesto offered an alternative for complex, changing environments. Waterfall still works for predictable, stable projects. Agile is better for uncertainty.<\/p>\n<h3>Who wrote the Agile Manifesto?<\/h3>\n<p>17 software professionals, including Kent Beck, Martin Fowler, and Jeff Sutherland, met in 2001 to draft it. They represented various Agile practices and sought to unify them under common values.<\/p>\n<p><strong>Agile Manifesto explained<\/strong> isn\u2019t about memorizing a list. It\u2019s about understanding the mindset that drives high-performing teams. The history of Agile Manifesto shows that real change comes not from tools, but from people choosing to collaborate, adapt, and deliver value\u2014every day.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>What if the most powerful shift in software development [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1430,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-1431","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Agile Manifesto Explained: Origins for Beginners<\/title>\n<meta name=\"description\" content=\"Discover the history of Agile Manifesto and Agile origins for beginners. Understand the 4 values and 12 principles behind Scrum and modern Agile practices with real-world context and actionable insights.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/\" \/>\n<meta property=\"og:locale\" content=\"zh_CN\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Agile Manifesto Explained: Origins for Beginners\" \/>\n<meta property=\"og:description\" content=\"Discover the history of Agile Manifesto and Agile origins for beginners. Understand the 4 values and 12 principles behind Scrum and modern Agile practices with real-world context and actionable insights.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 \u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/\",\"name\":\"Agile Manifesto Explained: Origins for Beginners\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\"},\"datePublished\":\"2026-02-25T10:41:35+00:00\",\"description\":\"Discover the history of Agile Manifesto and Agile origins for beginners. Understand the 4 values and 12 principles behind Scrum and modern Agile practices with real-world context and actionable insights.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/#breadcrumb\"},\"inLanguage\":\"zh-Hans\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum Essentials: Beginner\u2019s Guide to Agile\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Introduction to Agile Fundamentals\",\"item\":\"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"The Origins of Agile: From Manifesto to Modern Practices\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-Hans\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#organization\",\"name\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-Hans\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Agile Manifesto Explained: Origins for Beginners","description":"Discover the history of Agile Manifesto and Agile origins for beginners. Understand the 4 values and 12 principles behind Scrum and modern Agile practices with real-world context and actionable insights.","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:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/","og_locale":"zh_CN","og_type":"article","og_title":"Agile Manifesto Explained: Origins for Beginners","og_description":"Discover the history of Agile Manifesto and Agile origins for beginners. Understand the 4 values and 12 principles behind Scrum and modern Agile practices with real-world context and actionable insights.","og_url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/","og_site_name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","twitter_card":"summary_large_image","twitter_misc":{"\u9884\u8ba1\u9605\u8bfb\u65f6\u95f4":"8 \u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/","name":"Agile Manifesto Explained: Origins for Beginners","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website"},"datePublished":"2026-02-25T10:41:35+00:00","description":"Discover the history of Agile Manifesto and Agile origins for beginners. Understand the 4 values and 12 principles behind Scrum and modern Agile practices with real-world context and actionable insights.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/#breadcrumb"},"inLanguage":"zh-Hans","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/agile-manifesto-explained-origins-beginners\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/cn\/"},{"@type":"ListItem","position":2,"name":"Scrum Essentials: Beginner\u2019s Guide to Agile","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/"},{"@type":"ListItem","position":3,"name":"Introduction to Agile Fundamentals","item":"https:\/\/skills.visual-paradigm.com\/cn\/docs\/scrum-essentials-beginners-guide-to-agile\/agile-fundamentals-beginners\/"},{"@type":"ListItem","position":4,"name":"The Origins of Agile: From Manifesto to Modern Practices"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#website","url":"https:\/\/skills.visual-paradigm.com\/cn\/","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/cn\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-Hans"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#organization","name":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/cn\/","logo":{"@type":"ImageObject","inLanguage":"zh-Hans","@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/cn\/wp-content\/uploads\/sites\/3\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7b80\u4f53\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/cn\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1431","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1431\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/docs\/1430"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/media?parent=1431"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/cn\/wp-json\/wp\/v2\/doc_tag?post=1431"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}