{"id":1445,"date":"2026-02-25T10:41:41","date_gmt":"2026-02-25T10:41:41","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/"},"modified":"2026-02-25T10:41:41","modified_gmt":"2026-02-25T10:41:41","slug":"scrum-sprint-backlog-planning-execution","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/","title":{"rendered":"Sprint Backlog Breakdown: From Planning to Execution"},"content":{"rendered":"

Starting a sprint feels exciting\u2014your team has committed to deliverables, the backlog is clear, and everyone is ready. But too often, what follows is confusion: tasks aren\u2019t broken down clearly, estimation drifts off, and progress stalls mid-sprint. The issue isn\u2019t effort\u2014it\u2019s structure. Many beginners treat the sprint backlog as a to-do list rather than a living plan shaped through collaboration.<\/p>\n

I\u2019ve seen teams jump straight into tasking without refining the work, only to find out mid-sprint that critical dependencies were overlooked. That\u2019s where the real friction begins. The sprint backlog isn\u2019t just a list of work\u2014it\u2019s a tactical blueprint for delivery, built not by command, but by the team. My advice? Never skip the task breakdown step. It\u2019s the bridge between vision and execution.<\/p>\n

In this chapter, you\u2019ll learn how to turn product backlog items into actionable, estimable tasks\u2014using story points, effective task breakdown techniques, and visual modeling. You\u2019ll discover how to avoid common missteps, plan with clarity, and keep momentum through the sprint. Whether you\u2019re new to Scrum or re-evaluating your process, this is where strategy becomes action.<\/p>\n

From Backlog to Action: The Sprint Backlog Process<\/h2>\n

Every sprint begins with the sprint goal and selected backlog items. But the real work happens when those high-level stories are transformed into concrete, manageable tasks. This is where the sprint backlog comes alive.<\/p>\n

Think of the sprint backlog as a team-owned roadmap\u2014not a directive from above. It evolves during sprint planning and daily stand-ups. The Product Owner presents the selected backlog items. The Development Team answers: \u201cWhat\u2019s needed to deliver this?\u201d<\/p>\n

Here\u2019s how to build it right:<\/p>\n

    \n
  1. Start with a clearly refined product backlog item.<\/li>\n
  2. Break it into tasks that are small enough to complete within a day or two.<\/li>\n
  3. Estimate effort using story points\u2014never ideal days.<\/li>\n
  4. Ensure every task is testable and contributes to the sprint goal.<\/li>\n
  5. Review with the team to confirm completeness and clarity.<\/li>\n<\/ol>\n

    Each task should answer: Who will do it? What\u2019s the expected outcome? What dependencies exist?<\/p>\n

    Why Story Points Over Ideal Days?<\/h3>\n

    Story points are not a measure of time\u2014they represent relative effort, complexity, and risk. I\u2019ve worked with teams that tried ideal days and quickly fell into overcommitment. A task estimated as \u201c2 days\u201d often becomes \u201c3\u201d or \u201c5\u201d in reality because they didn\u2019t account for interruptions, dependencies, or unknowns.<\/p>\n

    Story points, based on the Fibonacci sequence (1, 2, 3, 5, 8, 13\u2026), reflect that effort grows non-linearly. A task rated 8 is significantly more complex than one rated 3. This forces teams to think comparatively, not quantitatively.<\/p>\n

    Story points also preserve team velocity. If your team completes 20 points per sprint consistently, you can forecast delivery with confidence\u2014without relying on calendar time.<\/p>\n

    Scrum Task Breakdown Techniques<\/h2>\n

    Breaking down work isn\u2019t just about splitting features into smaller tasks. It\u2019s about making the invisible visible and the complex manageable. Here are proven techniques I\u2019ve used across dozens of teams:<\/p>\n

    1. The \u201cHow?\u201d Technique<\/h3>\n

    Ask: \u201cHow will we deliver this?\u201d For a user story like \u201cAs a user, I want to reset my password,\u201d the team might ask:<\/p>\n

      \n
    • How do we validate the email address?<\/li>\n
    • How do we generate a secure token?<\/li>\n
    • How do we update the password after verification?<\/li>\n
    • How do we ensure the token expires?<\/li>\n<\/ul>\n

      Each \u201chow\u201d becomes a task. This method ensures all technical and user-facing parts are accounted for.<\/p>\n

      2. The Three Amigos Approach<\/h3>\n

      Collaborate across roles: Product Owner, Scrum Master, and Development Team. Before finalizing tasks, run a quick \u201cThree Amigos\u201d check:<\/p>\n

        \n
      • Product Owner:<\/strong> Does this support the sprint goal?<\/li>\n
      • Scrum Master:<\/strong> Are there impediments or dependencies?<\/li>\n
      • Development Team:<\/strong> Can this be completed in one sprint? Is it testable?<\/li>\n<\/ul>\n

        This ensures alignment and early problem detection.<\/p>\n

        3. Use the \u201cDefinition of Ready\u201d Checklist<\/h3>\n

        Before a backlog item enters the sprint, it must meet the Definition of Ready (DoR). Use this checklist to guide task breakdown:<\/p>\n\n\n\n\n\n\n\n\n
        DoR Criteria<\/th>\nChecked?<\/th>\n<\/tr>\n
        Clear acceptance criteria<\/td>\n\u2705<\/td>\n<\/tr>\n
        Acceptable story format (As a… I want… so that…)<\/td>\n\u2705<\/td>\n<\/tr>\n
        Estimation completed<\/td>\n\u2705<\/td>\n<\/tr>\n
        Dependencies identified<\/td>\n\u2705<\/td>\n<\/tr>\n
        Team agrees it\u2019s ready<\/td>\n\u2705<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Only items meeting all criteria should be pulled into the sprint backlog.<\/p>\n

        Visualizing the Sprint Backlog with Flowcharts<\/h2>\n

        Not every task needs a flowchart\u2014but complex features do. Visual modeling helps teams see logic, identify bottlenecks, and avoid rework.<\/p>\n

        For example, a login flow might involve:<\/p>\n

          \n
        • Input email<\/li>\n
        • Validate format<\/li>\n
        • Check if user exists<\/li>\n
        • Send password reset link<\/li>\n
        • Store token with expiry<\/li>\n
        • Redirect to confirmation page<\/li>\n<\/ul>\n

          Turning this into a flowchart\u2014using tools like Visual Paradigm or even simple whiteboarding\u2014makes it impossible to miss steps. It also becomes a living document: during daily stand-ups, the team can refer to it to track progress.<\/p>\n

          I recommend using a simple flowcharting tool during sprint planning. It doesn\u2019t need to be complex. The goal is clarity, not perfection. A flowchart can be revised during the sprint if new information emerges.<\/p>\n

          Creating Sprint Backlog Beginners: A Step-by-Step Guide<\/h2>\n

          For those just getting started, here\u2019s a practical approach to creating a sprint backlog that actually works:<\/p>\n

            \n
          1. Review the sprint goal.<\/strong> Ensure every task aligns with it.<\/li>\n
          2. Break down selected items.<\/strong> Use the \u201cHow?\u201d and \u201cThree Amigos\u201d techniques.<\/li>\n
          3. Assign story points.<\/strong> Use planning poker or affinity estimation.<\/li>\n
          4. Create task cards.<\/strong> Use a physical or digital Scrum board with columns: To Do, In Progress, Done.<\/li>\n
          5. Map critical workflows.<\/strong> Use visual flowcharts for complex processes.<\/li>\n
          6. Review with the team.<\/strong> Confirm all tasks are clear, testable, and estimable.<\/li>\n<\/ol>\n

            At the end of this process, your sprint backlog should be more than a list\u2014it should be a shared understanding of how the team will deliver value.<\/p>\n

            Common Pitfalls and How to Avoid Them<\/h2>\n

            Even experienced teams stumble. Here are the most frequent issues\u2014and how to fix them:<\/p>\n

              \n
            • Tasks are too large.<\/strong> If a task takes more than two days, break it further. Ask: \u201cWhat\u2019s the smallest piece we can deliver that adds value?\u201d<\/li>\n
            • No estimation.<\/strong> Never skip estimation. Even rough sizing builds team alignment and forecasting capability.<\/li>\n
            • Tasks lack ownership.<\/strong> Assign every task to a team member. Ambiguity leads to delays.<\/li>\n
            • No visual tracking.<\/strong> Use a board. A burndown chart helps track progress\u2014but the board shows who\u2019s doing what.<\/li>\n
            • Ignoring dependencies.<\/strong> Document them. Use color coding or labels to flag blocked tasks.<\/li>\n<\/ul>\n

              These aren\u2019t just warnings\u2014they\u2019re guardrails. When teams follow them, sprint execution becomes predictable and sustainable.<\/p>\n

              Frequently Asked Questions<\/h2>\n

              What is the ideal sprint backlog size?<\/h3>\n

              There\u2019s no fixed number. Focus on capacity, not count. A sprint backlog with 15\u201320 story points is typical for an average team. The size depends on team velocity and sprint length. Prioritize clarity and realism over quantity.<\/p>\n

              Can a sprint backlog item have no tasks?<\/h3>\n

              No. Every item in the sprint backlog must be decomposed into tasks. If a story has no tasks, it\u2019s not ready for the sprint. It may be too large, poorly defined, or missing acceptance criteria.<\/p>\n

              Should the Scrum Master create the sprint backlog?<\/h3>\n

              No. The Development Team owns the sprint backlog. The Scrum Master facilitates, coaches, and removes impediments\u2014but does not dictate tasks. If tasks are imposed from outside, the team loses autonomy and ownership.<\/p>\n

              How often should we update the sprint backlog?<\/h3>\n

              Update it during the sprint as needed\u2014especially when new risks or dependencies emerge. But avoid constant rework. Changes should be rare and only if they don\u2019t violate the sprint goal. Use the Daily Scrum to surface issues early.<\/p>\n

              What if our team can\u2019t estimate a task?<\/h3>\n

              That\u2019s a red flag. If a task can\u2019t be estimated, it\u2019s likely too large or poorly understood. Break it down further. If it still can\u2019t be estimated, the team needs more refinement. Do not commit to it in the sprint.<\/p>\n

              How do flowcharts help in sprint planning?<\/h3>\n

              Flowcharts clarify logic, identify decision points, and prevent missing steps. They help teams visualize workflows before coding, reducing rework. Tools like Visual Paradigm allow you to create professional diagrams quickly and integrate them into your backlog.<\/p>\n","protected":false},"excerpt":{"rendered":"

              Starting a sprint feels exciting\u2014your team has committed to deliverables, the backlog is clear, and everyone is ready. But too often, what follows is confusion: tasks aren\u2019t broken down clearly, estimation drifts off, and progress stalls mid-sprint. The issue isn\u2019t effort\u2014it\u2019s structure. Many beginners treat the sprint backlog as a to-do list rather than a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1443,"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":"","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-1445","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"\nScrum Sprint Backlog: From Planning to Execution<\/title>\n<meta name=\"description\" content=\"Master creating sprint backlog beginners' work with Scrum task breakdown techniques. Learn how to turn product backlog items into actionable tasks, estimate effort, and visualize workflows for effective sprint planning.\" \/>\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\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/\" \/>\n<meta property=\"og:locale\" content=\"id_ID\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scrum Sprint Backlog: From Planning to Execution\" \/>\n<meta property=\"og:description\" content=\"Master creating sprint backlog beginners' work with Scrum task breakdown techniques. Learn how to turn product backlog items into actionable tasks, estimate effort, and visualize workflows for effective sprint planning.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Indonesia\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimasi waktu membaca\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 menit\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/\",\"name\":\"Scrum Sprint Backlog: From Planning to Execution\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\"},\"datePublished\":\"2026-02-25T10:41:41+00:00\",\"description\":\"Master creating sprint backlog beginners' work with Scrum task breakdown techniques. Learn how to turn product backlog items into actionable tasks, estimate effort, and visualize workflows for effective sprint planning.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/#breadcrumb\"},\"inLanguage\":\"id\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum Essentials: Beginner\u2019s Guide to Agile\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Mastering Scrum Artifacts\",\"item\":\"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Sprint Backlog Breakdown: From Planning to Execution\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"name\":\"Visual Paradigm Skills Indonesia\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"id\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#organization\",\"name\":\"Visual Paradigm Skills Indonesia\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"id\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Indonesia\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scrum Sprint Backlog: From Planning to Execution","description":"Master creating sprint backlog beginners' work with Scrum task breakdown techniques. Learn how to turn product backlog items into actionable tasks, estimate effort, and visualize workflows for effective sprint planning.","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\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/","og_locale":"id_ID","og_type":"article","og_title":"Scrum Sprint Backlog: From Planning to Execution","og_description":"Master creating sprint backlog beginners' work with Scrum task breakdown techniques. Learn how to turn product backlog items into actionable tasks, estimate effort, and visualize workflows for effective sprint planning.","og_url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/","og_site_name":"Visual Paradigm Skills Indonesia","twitter_card":"summary_large_image","twitter_misc":{"Estimasi waktu membaca":"7 menit"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/","url":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/","name":"Scrum Sprint Backlog: From Planning to Execution","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#website"},"datePublished":"2026-02-25T10:41:41+00:00","description":"Master creating sprint backlog beginners' work with Scrum task breakdown techniques. Learn how to turn product backlog items into actionable tasks, estimate effort, and visualize workflows for effective sprint planning.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/#breadcrumb"},"inLanguage":"id","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/scrum-sprint-backlog-planning-execution\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/id\/"},{"@type":"ListItem","position":2,"name":"Scrum Essentials: Beginner\u2019s Guide to Agile","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/"},{"@type":"ListItem","position":3,"name":"Mastering Scrum Artifacts","item":"https:\/\/skills.visual-paradigm.com\/id\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-artifacts\/"},{"@type":"ListItem","position":4,"name":"Sprint Backlog Breakdown: From Planning to Execution"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/id\/#website","url":"https:\/\/skills.visual-paradigm.com\/id\/","name":"Visual Paradigm Skills Indonesia","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/id\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"id"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/id\/#organization","name":"Visual Paradigm Skills Indonesia","url":"https:\/\/skills.visual-paradigm.com\/id\/","logo":{"@type":"ImageObject","inLanguage":"id","@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/id\/wp-content\/uploads\/sites\/7\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Indonesia"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/id\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1445","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1445\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/docs\/1443"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/media?parent=1445"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/id\/wp-json\/wp\/v2\/doc_tag?post=1445"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}