{"id":1709,"date":"2026-02-25T10:44:58","date_gmt":"2026-02-25T10:44:58","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/"},"modified":"2026-03-02T09:10:44","modified_gmt":"2026-03-02T09:10:44","slug":"uml-in-agile-lightweight-modeling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/","title":{"rendered":"Integrating UML with Agile Workflows"},"content":{"rendered":"<p>Agile teams often resist formal modeling, fearing it slows them down. But UML in agile doesn&#8217;t mean full documentation or rigid processes. It means using UML as a shared language\u2014focused, fast, and purpose-driven.<\/p>\n<p>I\u2019ve led teams through multiple agile transformations, and the most successful ones didn\u2019t eliminate diagrams\u2014they redefined their purpose. The key insight? UML isn\u2019t about perfection. It\u2019s about clarity, alignment, and reducing ambiguity in just a few minutes of work.<\/p>\n<p>Here, you\u2019ll learn how to make UML serve your sprint goals. No fluff. No over-engineering. Just real, practical ways to apply UML for agile beginners who want to model with intent, not overhead.<\/p>\n<h2>Why UML Still Belongs in Agile<\/h2>\n<p>Agile doesn\u2019t reject modeling\u2014it embraces *just enough* modeling. UML is one of the few tools that can be both concise and expressive when used correctly.<\/p>\n<p>Consider this: a single well-placed use case diagram during sprint planning can clarify what \u201cuser authentication\u201d really means across the team. That\u2019s not overhead. It\u2019s alignment.<\/p>\n<p>UML in agile works best when you treat it as a communication aid, not a deliverable. It\u2019s not about creating a perfect diagram\u2014it\u2019s about preventing misunderstandings before coding begins.<\/p>\n<h3>Agile modeling with UML: Core Principles<\/h3>\n<ul>\n<li>Use UML only when it adds value\u2014skip it if the team already understands the flow.<\/li>\n<li>Keep diagrams small: 1\u20133 pages max. A single screen of notation is enough.<\/li>\n<li>Update diagrams iteratively. Treat them as living artifacts, not static documents.<\/li>\n<li>Use visual simplicity\u2014avoid complex notation unless needed.<\/li>\n<li>Focus on clarity over completeness. A simple, accurate diagram beats a detailed but confusing one.<\/li>\n<\/ul>\n<h2>Integrating UML into Your Agile Sprints<\/h2>\n<p>Think of UML as a sprint tool\u2014not a phase gate. Use it to shape upcoming work, clarify complexity, and align expectations.<\/p>\n<p>Here\u2019s how I\u2019ve seen teams use UML effectively in 2-week sprints:<\/p>\n<h3>Step 1: Start with the User Story<\/h3>\n<p>Begin with the story: \u201cAs a user, I want to reset my password so I can regain access.\u201d<\/p>\n<p>Now, ask: What does \u201creset\u201d actually involve? Use a simple sequence diagram or activity diagram to map it. This isn\u2019t design\u2014it\u2019s clarification.<\/p>\n<h3>Step 2: Use a Lightweight Diagram<\/h3>\n<p>For this story, a 2\u20133-step activity diagram often suffices:<\/p>\n<ol>\n<li>User clicks \u201cForgot Password\u201d<\/li>\n<li>System emails a token<\/li>\n<li>User enters token and new password<\/li>\n<\/ol>\n<p>That\u2019s enough to define acceptance criteria and avoid ambiguity.<\/p>\n<h3>Step 3: Refactor &amp; Reuse Across Sprints<\/h3>\n<p>When a similar flow appears in another story (e.g., \u201cVerify email address\u201d), reference the existing diagram. Update it if needed. This builds a shared model library.<\/p>\n<p>You\u2019re not building a full system model in one sprint. You&#8217;re building trust through shared understanding.<\/p>\n<h2>Linking UML to User Stories: A Practical Framework<\/h2>\n<p>Every user story should have a corresponding lightweight UML artifact. Not every story needs a diagram\u2014but every complex story should.<\/p>\n<p>Use this simple checklist to decide when to model:<\/p>\n<ul>\n<li>The story involves &gt;2 steps or decision points.<\/li>\n<li>Team members have different interpretations of the flow.<\/li>\n<li>It involves external systems or integration points.<\/li>\n<li>It\u2019s a recurring pattern (e.g., login, payment, verification).<\/li>\n<\/ul>\n<p>When any of these apply, a short diagram is not a burden\u2014it\u2019s a preventative measure.<\/p>\n<h3>Mapping Stories to UML Diagrams<\/h3>\n<table>\n<tbody>\n<tr>\n<th>User Story<\/th>\n<th>Recommended UML Diagram<\/th>\n<th>Use Case<\/th>\n<\/tr>\n<tr>\n<td>As a customer, I want to track my order so I can know delivery status.<\/td>\n<td>Activity diagram<\/td>\n<td>Visualize status flow: placed \u2192 shipped \u2192 delivered<\/td>\n<\/tr>\n<tr>\n<td>As a user, I want to log in with my email and password.<\/td>\n<td>Sequence diagram<\/td>\n<td>Model login flow including error handling<\/td>\n<\/tr>\n<tr>\n<td>As a manager, I want to see daily sales reports.<\/td>\n<td>Use case diagram<\/td>\n<td>Show interaction between manager and reporting system<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>These aren\u2019t mandatory for every story\u2014but when used purposefully, they prevent rework and misalignment.<\/p>\n<h2>UML for Agile Beginners: Real-World Examples<\/h2>\n<p>In my experience, the most common mistake beginners make is trying to model everything. Instead, focus on the high-risk, high-ambiguity areas.<\/p>\n<p>Example: A startup needed to model a refund process. The user story was simple: \u201cAs a customer, I want to request a refund.\u201d<\/p>\n<p>But what happens if the order was shipped? If it\u2019s been 30 days? If the product is damaged?<\/p>\n<p>We used a decision-based activity diagram to map the rules. It revealed a gap: no policy for partial refunds. That insight led to a new requirement, not a design flaw.<\/p>\n<p>This is how UML adds real value in agile. It exposes hidden complexity before development begins.<\/p>\n<h2>Common Pitfalls and How to Avoid Them<\/h2>\n<p>Even when used correctly, UML in agile can go off track. Here are the top three issues and how to fix them:<\/p>\n<ol>\n<li><strong>Over-modeling<\/strong>: A diagram with 20+ elements is hard to read. Fix: Limit to 5\u20137 key elements. Use swimlanes to separate roles.<\/li>\n<li><strong>Out-of-sync diagrams<\/strong>: A diagram that doesn\u2019t match current code. Fix: Keep diagrams in the same repo as code. Update them during refactoring.<\/li>\n<li><strong>Too formal<\/strong>: Using UML notation correctly but with no context. Fix: Add brief notes explaining why the diagram matters.<\/li>\n<\/ol>\n<p>Remember: the goal isn\u2019t to create a textbook diagram. It\u2019s to enable faster, clearer communication.<\/p>\n<h2>Integrate UML in Agile Projects: A Final Checklist<\/h2>\n<p>Before your next sprint planning, ask:<\/p>\n<ul>\n<li>Is this user story complex enough to need a diagram?<\/li>\n<li>Can I explain the flow in 30 seconds with a sketch?<\/li>\n<li>Will this help prevent rework or misunderstanding?<\/li>\n<li>Is the diagram simple enough for anyone on the team to understand?<\/li>\n<li>Can I update it in under 10 minutes if requirements change?<\/li>\n<\/ul>\n<p>If you answer \u201cyes\u201d to most, you\u2019re using UML in agile the right way.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can I use UML in agile without a dedicated designer?<\/h3>\n<p>Absolutely. UML for agile beginners doesn\u2019t require a modeling expert. Anyone on the team\u2014product owner, developer, QA\u2014can create a quick diagram. The goal is clarity, not perfection.<\/p>\n<h3>Do I need to update UML diagrams every sprint?<\/h3>\n<p>No. Only update when the behavior changes. Keep diagrams in sync with code. If the feature is deleted, delete the diagram. If it evolves, refine it.<\/p>\n<h3>How do I handle conflicting interpretations in UML?<\/h3>\n<p>Use a collaborative session. Draw the flow together. Let the team vote on the sequence. The diagram becomes a tool for consensus, not a decision from above.<\/p>\n<h3>What\u2019s the best UML tool for agile teams?<\/h3>\n<p>Look for tools that support lightweight creation, team collaboration, and integration with your workflow. Visual Paradigm offers agile-friendly interfaces.<\/p>\n<h3>Should I teach UML to new developers in agile?<\/h3>\n<p>Yes\u2014but start with one diagram. Use the activity diagram to model a simple workflow. After they can read and draw it, introduce others. Focus on purpose, not notation.<\/p>\n<h3>Can UML work in extreme programming (XP) or Kanban?<\/h3>\n<p>Yes. UML in agile isn\u2019t limited to Scrum. Use it to clarify flows, define acceptance criteria, and track dependencies. In Kanban, use diagrams as visual aids on the board.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Agile teams often re [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1707,"menu_order":1,"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":"default","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","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-1709","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>UML in Agile: Lightweight Modeling That Works<\/title>\n<meta name=\"description\" content=\"Learn how to integrate UML in agile projects with lightweight, iterative modeling. Practical guidance for agile beginners on aligning UML with sprints, user stories, and team workflows.\" \/>\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\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/\" \/>\n<meta property=\"og:locale\" content=\"zh_TW\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"UML in Agile: Lightweight Modeling That Works\" \/>\n<meta property=\"og:description\" content=\"Learn how to integrate UML in agile projects with lightweight, iterative modeling. Practical guidance for agile beginners on aligning UML with sprints, user stories, and team workflows.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-02T09:10:44+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u9810\u4f30\u95b1\u8b80\u6642\u9593\" \/>\n\t<meta name=\"twitter:data1\" content=\"5 \u5206\u9418\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/\",\"name\":\"UML in Agile: Lightweight Modeling That Works\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\"},\"datePublished\":\"2026-02-25T10:44:58+00:00\",\"dateModified\":\"2026-03-02T09:10:44+00:00\",\"description\":\"Learn how to integrate UML in agile projects with lightweight, iterative modeling. Practical guidance for agile beginners on aligning UML with sprints, user stories, and team workflows.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/#breadcrumb\"},\"inLanguage\":\"zh-TW\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"UML Basics: Diagrams for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Best Practices and Common Pitfalls\",\"item\":\"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Integrating UML with Agile Workflows\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"zh-TW\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#organization\",\"name\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"zh-TW\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"UML in Agile: Lightweight Modeling That Works","description":"Learn how to integrate UML in agile projects with lightweight, iterative modeling. Practical guidance for agile beginners on aligning UML with sprints, user stories, and team workflows.","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\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/","og_locale":"zh_TW","og_type":"article","og_title":"UML in Agile: Lightweight Modeling That Works","og_description":"Learn how to integrate UML in agile projects with lightweight, iterative modeling. Practical guidance for agile beginners on aligning UML with sprints, user stories, and team workflows.","og_url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/","og_site_name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","article_modified_time":"2026-03-02T09:10:44+00:00","twitter_card":"summary_large_image","twitter_misc":{"\u9810\u4f30\u95b1\u8b80\u6642\u9593":"5 \u5206\u9418"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/","name":"UML in Agile: Lightweight Modeling That Works","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website"},"datePublished":"2026-02-25T10:44:58+00:00","dateModified":"2026-03-02T09:10:44+00:00","description":"Learn how to integrate UML in agile projects with lightweight, iterative modeling. Practical guidance for agile beginners on aligning UML with sprints, user stories, and team workflows.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/#breadcrumb"},"inLanguage":"zh-TW","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/uml-in-agile-lightweight-modeling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/tw\/"},{"@type":"ListItem","position":2,"name":"UML Basics: Diagrams for Beginners","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Best Practices and Common Pitfalls","item":"https:\/\/skills.visual-paradigm.com\/tw\/docs\/uml-basics-diagrams-for-beginners\/uml-best-practices\/"},{"@type":"ListItem","position":4,"name":"Integrating UML with Agile Workflows"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#website","url":"https:\/\/skills.visual-paradigm.com\/tw\/","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/tw\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"zh-TW"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#organization","name":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587","url":"https:\/\/skills.visual-paradigm.com\/tw\/","logo":{"@type":"ImageObject","inLanguage":"zh-TW","@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/tw\/wp-content\/uploads\/sites\/2\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u7e41\u9ad4\u4e2d\u6587"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/tw\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1709","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":2,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1709\/revisions"}],"predecessor-version":[{"id":2410,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1709\/revisions\/2410"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/docs\/1707"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/media?parent=1709"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/tw\/wp-json\/wp\/v2\/doc_tag?post=1709"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}