{"id":1806,"date":"2026-02-25T10:46:12","date_gmt":"2026-02-25T10:46:12","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/"},"modified":"2026-02-25T10:46:12","modified_gmt":"2026-02-25T10:46:12","slug":"agile-risk-management-stories","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/","title":{"rendered":"Risk Management Through Story Dependencies"},"content":{"rendered":"<p>\u201cWe\u2019ll figure it out when we get there\u201d \u2014 that\u2019s how most teams begin tackling complex dependencies. But in large-scale Agile, that mindset often leads to bottlenecks, missed releases, and frustrated stakeholders.<\/p>\n<p>Dependency risk agile isn\u2019t a problem that surfaces at sprint end. It\u2019s baked into how we write, link, and prioritize stories from day one.<\/p>\n<p>Over two decades of guiding enterprise teams through transformation, I\u2019ve learned that agility isn\u2019t about avoiding risk \u2014 it\u2019s about surfacing it early, measuring its impact, and owning it before it steals velocity.<\/p>\n<p>This chapter equips you with practical, field-tested methods to model risk at the backlog level \u2014 not through heavy documentation, but through story-based risk visualization. You\u2019ll learn to identify hidden delays, assess their cost, and embed mitigation into story refinement \u2014 all while preserving team autonomy and flow.<\/p>\n<h2>Why Dependency Risk Escalates in Large-Scale Agile<\/h2>\n<p>At scale, stories rarely exist in isolation. A feature in one team\u2019s backlog often depends on a story in another \u2014 and that dependency can carry hidden risk.<\/p>\n<p>But most teams only flag these risks during sprint planning or PI planning. By then, the damage is already done.<\/p>\n<p>Proactive risk management starts with recognizing that every dependency is a potential delay \u2014 and every delay has a cost. That cost isn\u2019t just about missed deadlines. It\u2019s about opportunity cost, team morale, and erosion of trust.<\/p>\n<p>Consider this: a story that blocks three teams may incur a delay cost of 120 story points across the board. That\u2019s not \u201ca small delay.\u201d It\u2019s a structural flaw in the backlog.<\/p>\n<h3>Hidden Risks in Dependency Chains<\/h3>\n<p>Dependencies don\u2019t exist in a vacuum. They form chains \u2014 and chains amplify risk.<\/p>\n<p>For example: Story A (Team X) depends on Story B (Team Y), which depends on Story C (Team Z). If Story C slips, the entire chain fails \u2014 even if Teams X and Y are ready.<\/p>\n<p>Many teams miss this because they only track dependencies at the story level. They don\u2019t model the cumulative delay cost across the chain.<\/p>\n<p>That\u2019s where story based risk visualization becomes essential.<\/p>\n<h2>Modeling Dependency Risk with Risk Tables<\/h2>\n<p>Instead of relying solely on dependency arrows in story maps, I recommend using a simple but powerful tool: the <strong>Dependency Risk Table<\/strong>.<\/p>\n<p>Each dependency gets scored on three dimensions:<\/p>\n<ul>\n<li><strong>Dependency Type<\/strong> (e.g., technical, data, integration, process)<\/li>\n<li><strong>Delay Cost<\/strong> (in story points lost if delayed by one sprint)<\/li>\n<li><strong>Mitigation Action<\/strong> (e.g., spike, parallel development, buffer story)<\/li>\n<\/ul>\n<p>Here\u2019s how it looks in practice:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Story ID<\/th>\n<th>Depends On<\/th>\n<th>Dependency Type<\/th>\n<th>Delay Cost (story points)<\/th>\n<th>Mitigation Action<\/th>\n<\/tr>\n<tr>\n<td>FEAT-120<\/td>\n<td>DEV-204<\/td>\n<td>Integration<\/td>\n<td>13<\/td>\n<td>Build mock interface; align on contract<\/td>\n<\/tr>\n<tr>\n<td>FIN-301<\/td>\n<td>DATA-402<\/td>\n<td>Data<\/td>\n<td>21<\/td>\n<td>Pre-load data model; validate with test data<\/td>\n<\/tr>\n<tr>\n<td>UI-505<\/td>\n<td>API-600<\/td>\n<td>Technical<\/td>\n<td>18<\/td>\n<td>Run architectural spike; document interface<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>By the time this table is complete, you\u2019re not just managing dependencies \u2014 you\u2019re quantifying their risk.<\/p>\n<p>Teams can now prioritize stories not just by value, but by risk exposure. The story with a 21-point delay cost becomes a top candidate for early refinement \u2014 not because it\u2019s complex, but because it\u2019s high-impact.<\/p>\n<h3>Integrating Risk into Backlog Refinement<\/h3>\n<p>Every backlog refinement session should include a risk review \u2014 not as a checklist, but as a conversation.<\/p>\n<p>Ask these questions:<\/p>\n<ol>\n<li>What happens if this story is delayed by one sprint?<\/li>\n<li>Who depends on this story? How many?<\/li>\n<li>Can we reduce that delay cost through a buffer story or spike?<\/li>\n<\/ol>\n<p>These aren\u2019t hypotheticals \u2014 they\u2019re real decisions that shape delivery cadence.<\/p>\n<p>One team I coached had a story that delayed two other teams. After adding a \u201cdata contract\u201d story as a buffer, the dependency risk dropped from 21 to 7 story points. A simple change \u2014 but one that prevented a three-week bottleneck.<\/p>\n<h2>Practical Techniques for Story-Based Risk Visualization<\/h2>\n<p>Visualizing risk isn\u2019t about creating more diagrams \u2014 it\u2019s about making hidden risks visible through simple, consistent models.<\/p>\n<h3>1. Use Color-Coded Risk Heatmaps<\/h3>\n<p>Assign colors to dependency types:<\/p>\n<ul>\n<li><span style=\"color: red;\">Red<\/span> \u2013 High-delay risks (e.g., shared services, integration)<\/li>\n<li><span style=\"color: orange;\">Orange<\/span> \u2013 Medium-delay risks (e.g., API, data access)<\/li>\n<li><span style=\"color: green;\">Green<\/span> \u2013 Low-delay risks (e.g., UI updates)<\/li>\n<\/ul>\n<p>Apply the color to story cards or in your backlog tool. Instantly, the highest-risk dependencies stand out.<\/p>\n<h3>2. Tag Stories with Risk Indicators<\/h3>\n<p>Use lightweight tags such as:<\/p>\n<ul>\n<li><code>[RISK:HIGH]<\/code> \u2013 Delay cost &gt; 15 story points<\/li>\n<li><code>[RISK:MEDIUM]<\/code> \u2013 5\u201314 points<\/li>\n<li><code>[RISK:LOW]<\/code> \u2013 1\u20134 points<\/li>\n<\/ul>\n<p>These tags don\u2019t replace conversation \u2014 they prompt it. They turn risk from a hidden condition into a visible signal.<\/p>\n<h3>3. Build a Risk Radar Chart<\/h3>\n<p>At the end of each PI, visualize risk across teams using a radar chart:<\/p>\n<ul>\n<li>Dependency density<\/li>\n<li>Delay cost exposure<\/li>\n<li>Frequency of mitigation actions<\/li>\n<li>Refinement time spent on risk<\/li>\n<\/ul>\n<p>This isn\u2019t about blame \u2014 it\u2019s about identifying systemic risk patterns. If multiple teams report high delay costs on integration stories, it\u2019s a sign to invest in shared APIs and contracts.<\/p>\n<h2>When Teams Don\u2019t Own the Risk<\/h2>\n<p>One of the most common missteps is assigning risk to a single team. \u201cTeam A owns the dependency.\u201d But risk is not a task \u2014 it\u2019s a condition of the system.<\/p>\n<p>Instead, reframe ownership: \u201cThe story is blocked by a dependency\u201d \u2014 not \u201cTeam B is responsible.\u201d That shift removes blame and focuses on solution.<\/p>\n<p>At the backlog level, every dependency should have a designated owner \u2014 but not necessarily the team that wrote it. The owner is the one who can make the decision: \u201cCan we proceed without this story?\u201d or \u201cShould we spike the interface?\u201d<\/p>\n<p>That owner is typically a technical lead, architect, or product owner with cross-team visibility.<\/p>\n<h2>Case Study: Reducing Risk in a Financial Services Platform<\/h2>\n<p>A global bank was struggling with monthly release delays. Their backlog had over 3,000 stories \u2014 many with untracked dependencies.<\/p>\n<p>We introduced a dependency risk table at the feature level. Over six months, we tracked:<\/p>\n<ul>\n<li>Number of high-risk dependencies (delay cost \u2265 15)<\/li>\n<li>Stories with mitigation actions<\/li>\n<li>Reduction in sprint blockages<\/li>\n<\/ul>\n<p>Result: 42% fewer blocked sprints, 27% faster delivery cycles, and a 68% drop in last-minute dependency escalations.<\/p>\n<p>The key wasn\u2019t process \u2014 it was visibility.<\/p>\n<h2>Key Takeaways<\/h2>\n<ul>\n<li>Dependency risk agile is not about avoiding dependencies \u2014 it\u2019s about managing their impact.<\/li>\n<li>Story based risk visualization turns hidden delays into actionable data.<\/li>\n<li>Use simple models: risk tables, tags, heatmaps \u2014 not complex dashboards.<\/li>\n<li>Ownership of risk should be shared, not assigned. The goal is flow, not blame.<\/li>\n<li>Proactive risk modeling at the backlog level prevents crises downstream.<\/li>\n<\/ul>\n<p>Agile risk management stories aren\u2019t a phase \u2014 they\u2019re a mindset. When teams internalize this, they stop reacting to chaos and start designing for resilience.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What\u2019s the difference between dependency tracking and risk modeling?<\/h3>\n<p>Tracking shows <em>what<\/em> depends on <em>what<\/em>. Risk modeling shows <em>how much<\/em> that delay costs. One is descriptive. The other is predictive.<\/p>\n<h3>How do I estimate delay cost for a dependency?<\/h3>\n<p>Ask the teams involved: \u201cIf this story is delayed by one sprint, how many story points of work will be blocked?\u201d Use the highest estimate if consensus isn\u2019t possible. Then round up.<\/p>\n<h3>Can I use story based risk visualization in SAFe?<\/h3>\n<p>Absolutely. In fact, it\u2019s ideal for PI Planning. Use the risk table to flag high-impact dependencies before the PI starts.<\/p>\n<h3>What if the dependency is external (e.g., third-party API)?<\/h3>\n<p>Tag it as [RISK:HIGH] and add a spike story to validate availability, uptime, and contract stability. Treat it as a risk \u2014 not a certainty.<\/p>\n<h3>How often should we review dependency risk?<\/h3>\n<p>At every backlog refinement. Reassess once per sprint. And re-evaluate during PI Planning or sprint review if dependencies change significantly.<\/p>\n<h3>Does this slow down backlog refinement?<\/h3>\n<p>Not if you keep it simple. A few minutes per high-risk story adds up to faster, more reliable delivery. The time saved on rework and rework delays far outweighs the cost of risk review.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u201cWe\u2019ll figure it out when we get there\u201d \u2014 that\u2019s how most teams begin tackling complex dependencies. But in large-scale Agile, that mindset often leads to bottlenecks, missed releases, and frustrated stakeholders. Dependency risk agile isn\u2019t a problem that surfaces at sprint end. It\u2019s baked into how we write, link, and prioritize stories from day [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1801,"menu_order":4,"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-1806","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 Risk Management Stories<\/title>\n<meta name=\"description\" content=\"Proactively model dependency risk, delay cost, and mitigation strategies using story-based risk visualization to maintain flow and alignment in large-scale Agile environments.\" \/>\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\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/\" \/>\n<meta property=\"og:locale\" content=\"ru_RU\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Agile Risk Management Stories\" \/>\n<meta property=\"og:description\" content=\"Proactively model dependency risk, delay cost, and mitigation strategies using story-based risk visualization to maintain flow and alignment in large-scale Agile environments.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f\" \/>\n\t<meta name=\"twitter:data1\" content=\"6 \u043c\u0438\u043d\u0443\u0442\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/\",\"name\":\"Agile Risk Management Stories\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\"},\"datePublished\":\"2026-02-25T10:46:12+00:00\",\"description\":\"Proactively model dependency risk, delay cost, and mitigation strategies using story-based risk visualization to maintain flow and alignment in large-scale Agile environments.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/#breadcrumb\"},\"inLanguage\":\"ru-RU\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"User Story Techniques for Large-Scale Agile Projects\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Supporting Practices and Scaled Facilitation\",\"item\":\"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Risk Management Through Story Dependencies\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ru-RU\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#organization\",\"name\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ru-RU\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Agile Risk Management Stories","description":"Proactively model dependency risk, delay cost, and mitigation strategies using story-based risk visualization to maintain flow and alignment in large-scale Agile environments.","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\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/","og_locale":"ru_RU","og_type":"article","og_title":"Agile Risk Management Stories","og_description":"Proactively model dependency risk, delay cost, and mitigation strategies using story-based risk visualization to maintain flow and alignment in large-scale Agile environments.","og_url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/","og_site_name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","twitter_card":"summary_large_image","twitter_misc":{"\u041f\u0440\u0438\u043c\u0435\u0440\u043d\u043e\u0435 \u0432\u0440\u0435\u043c\u044f \u0434\u043b\u044f \u0447\u0442\u0435\u043d\u0438\u044f":"6 \u043c\u0438\u043d\u0443\u0442"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/","name":"Agile Risk Management Stories","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website"},"datePublished":"2026-02-25T10:46:12+00:00","description":"Proactively model dependency risk, delay cost, and mitigation strategies using story-based risk visualization to maintain flow and alignment in large-scale Agile environments.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/#breadcrumb"},"inLanguage":"ru-RU","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/agile-risk-management-stories\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/ru\/"},{"@type":"ListItem","position":2,"name":"User Story Techniques for Large-Scale Agile Projects","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/"},{"@type":"ListItem","position":3,"name":"Supporting Practices and Scaled Facilitation","item":"https:\/\/skills.visual-paradigm.com\/ru\/docs\/user-story-techniques-large-scale-agile\/scaled-agile-facilitation\/"},{"@type":"ListItem","position":4,"name":"Risk Management Through Story Dependencies"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#website","url":"https:\/\/skills.visual-paradigm.com\/ru\/","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/ru\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ru-RU"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#organization","name":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439","url":"https:\/\/skills.visual-paradigm.com\/ru\/","logo":{"@type":"ImageObject","inLanguage":"ru-RU","@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/ru\/wp-content\/uploads\/sites\/10\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills \u0420\u0443\u0441\u0441\u043a\u0438\u0439"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/ru\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1806","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1806\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/docs\/1801"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/media?parent=1806"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/ru\/wp-json\/wp\/v2\/doc_tag?post=1806"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}