{"id":1451,"date":"2026-02-25T10:41:42","date_gmt":"2026-02-25T10:41:42","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/"},"modified":"2026-02-25T10:41:42","modified_gmt":"2026-02-25T10:41:42","slug":"scrum-sprint-review-guide-beginners","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/","title":{"rendered":"Conducting Sprint Reviews: Feedback Loops for Improvement"},"content":{"rendered":"<p>Too many teams treat the sprint review as a formality\u2014just a slide deck to present completed work. But that\u2019s where the real learning begins.<\/p>\n<p>I\u2019ve seen teams deliver fully functional features only to have stakeholders say, \u201cThis isn\u2019t what we wanted.\u201d Not because the work was poor\u2014but because the feedback loop was closed too late.<\/p>\n<p>The Scrum sprint review isn\u2019t a presentation. It\u2019s a conversation. A chance to inspect what was built and adapt based on real user needs.<\/p>\n<p>As a Scrum Master, I\u2019ve watched teams transform their sprint reviews from status updates into powerful feedback engines. And it starts with one shift: stop preparing to \u201cshow\u201d work. Start preparing to \u201clearn\u201d from it.<\/p>\n<p>In this guide, you\u2019ll get a clear, no-fluff path to leading effective sprint reviews. You\u2019ll learn how to demo in sprint review with purpose, structure stakeholder engagement, and use diagrams to make outcomes visible\u2014without overcomplicating things.<\/p>\n<p>You\u2019ll also discover how a simple checklist can prevent common pitfalls, and why the best sprint reviews are not about perfection\u2014but about progress and people.<\/p>\n<h2>Preparing for a Meaningful Sprint Review<\/h2>\n<p>Preparation is not about polishing slides. It\u2019s about ensuring the right people, the right data, and the right mindset come together to make the review valuable.<\/p>\n<p>Start with the sprint goal. Ask: Did the team deliver on the goal they committed to? If not, why? That should be the first point of discussion.<\/p>\n<p>Next, ensure the Product Owner has curated the Increment. Only items that meet the Definition of Done should be included. Don\u2019t let \u201calmost done\u201d work derail the conversation.<\/p>\n<p>Invite the right stakeholders. This isn\u2019t just the project sponsor. Include users, support teams, and anyone impacted by the delivered features.<\/p>\n<p>Use a simple checklist to stay focused:<\/p>\n<ul>\n<li>Confirm the sprint goal is visible and discussed<\/li>\n<li>Verify all selected Product Backlog items are Done<\/li>\n<li>Prepare a demo environment that reflects production behavior<\/li>\n<li>Share access to the working increment in advance (e.g., demo link)<\/li>\n<li>Identify 2\u20133 key questions to guide the discussion<\/li>\n<\/ul>\n<p>When I coach new teams, I often remind them: the goal of the sprint review isn\u2019t to win approval. It\u2019s to learn what works\u2014and what doesn\u2019t\u2014before the next sprint begins.<\/p>\n<h3>How to Demo in Sprint Review: A Practical Approach<\/h3>\n<p>Many beginners think a demo means showing every task or every line of code. That\u2019s a mistake.<\/p>\n<p>Focus on user value. Show what the user can do with the feature. Use real-world scenarios. Instead of \u201cthe login button is implemented,\u201d say, \u201ca customer can now reset their password in under 30 seconds.\u201d<\/p>\n<p>Keep it under 30 minutes. If you\u2019re talking longer, you\u2019re likely including too much detail or not focusing on outcomes.<\/p>\n<p>Use a structured demo format:<\/p>\n<ol>\n<li><strong>Start with the sprint goal<\/strong> \u2013 \u201cThis sprint, we aimed to reduce checkout time by 40%.\u201d<\/li>\n<li><strong>Show the working product<\/strong> \u2013 Walk through the user journey with a live or recorded demo.<\/li>\n<li><strong>Highlight key outcomes<\/strong> \u2013 \u201cWe reduced average checkout time from 90 to 52 seconds.\u201d<\/li>\n<li><strong>Invite feedback<\/strong> \u2013 \u201cWhat would make this even better for your team?\u201d<\/li>\n<\/ol>\n<p>This format keeps the demo focused and the conversation action-oriented.<\/p>\n<p>For beginners, here\u2019s a tip: rehearse the demo with a colleague who isn\u2019t involved in the sprint. If they can\u2019t understand the value in 15 seconds, you\u2019re not telling the right story.<\/p>\n<h2>Engaging Stakeholders and Capturing Feedback<\/h2>\n<p>Stakeholder engagement is not about making everyone happy. It\u2019s about making the right decisions based on real user needs.<\/p>\n<p>Beginner teams often make the mistake of inviting stakeholders only to let them passively watch. That\u2019s a missed opportunity.<\/p>\n<p>Instead, use techniques like \u201cdot voting\u201d or \u201cimpact effort\u201d grids to help stakeholders prioritize the next steps. Ask: \u201cWhich of these features would deliver the most value if we built it next?\u201d<\/p>\n<p>Keep feedback organized. Use a simple shared document or whiteboard to capture insights in real time. Categorize feedback into:<\/p>\n<ul>\n<li><strong>Changes to the product<\/strong> \u2013 \u201cAdd dark mode\u201d<\/li>\n<li><strong>Improvements to the process<\/strong> \u2013 \u201cWe need to start sprint reviews earlier\u201d<\/li>\n<li><strong>New ideas for future sprints<\/strong> \u2013 \u201cCould we add a mobile app next?\u201d<\/li>\n<\/ul>\n<p>At the end of the session, the Product Owner should commit to reviewing these inputs and updating the backlog accordingly.<\/p>\n<p>One team I worked with used a \u201cFeedback Wall\u201d during their sprint review. They posted sticky notes on a board\u2014each labeled with the source (e.g., \u201cCustomer Support\u201d)\u2014and grouped them by theme. The result? They identified a recurring pain point in onboarding that led to a major backlog refinement session.<\/p>\n<h3>Using Diagrams to Make Feedback Clear<\/h3>\n<p>Diagrams aren\u2019t about impressing. They\u2019re about clarity.<\/p>\n<p>When you show a feature, back it up with a simple flowchart, user journey map, or before\/after comparison. These visuals help stakeholders understand context.<\/p>\n<p>For example, a flowchart showing the old checkout path versus the new one makes the improvement visible. A user journey map highlights where friction was removed.<\/p>\n<p>Don\u2019t overdesign. Use tools or even paper and markers. The goal is communication\u2014not aesthetics.<\/p>\n<p>Here\u2019s a simple template to use during your sprint review:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Element<\/th>\n<th>What to Show<\/th>\n<th>Why It Matters<\/th>\n<\/tr>\n<tr>\n<td>Sprint Goal<\/td>\n<td>One sentence<\/td>\n<td>Aligns everyone on purpose<\/td>\n<\/tr>\n<tr>\n<td>Working Demo<\/td>\n<td>Live or recorded user flow<\/td>\n<td>Shows real value<\/td>\n<\/tr>\n<tr>\n<td>Before\/After Comparison<\/td>\n<td>Simple diagram<\/td>\n<td>Highlights improvement<\/td>\n<\/tr>\n<tr>\n<td>Feedback Summary<\/td>\n<td>Grouped sticky notes or bullet points<\/td>\n<td>Ensures no insight is lost<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This structure keeps the review focused and productive.<\/p>\n<h2>Common Challenges and How to Overcome Them<\/h2>\n<p>The sprint review is where many teams hit their first real roadblock.<\/p>\n<p>One of the most common issues? The team shows work that no one asked for.<\/p>\n<p>Why does this happen? Often because the Product Owner didn\u2019t validate the backlog with stakeholders before sprint planning. Or the team misunderstood the user need.<\/p>\n<p>Solution: The Product Owner must ensure that backlog items are grounded in real user problems. Use techniques like \u201cjob stories\u201d or \u201cuser role mapping\u201d to clarify intent.<\/p>\n<p>Another frequent issue: feedback comes too late. A stakeholder says, \u201cWe need this changed,\u201d but the sprint is already over.<\/p>\n<p>This is why the sprint review exists. To catch that early. If a change is needed, it should be added to the backlog and prioritized\u2014never forced into the current sprint.<\/p>\n<p>Finally, some teams struggle with time management. A 2-hour review lasting 4 hours isn\u2019t uncommon.<\/p>\n<p>Prevention: Set a strict timebox. Use a timer. If you\u2019re over time, pause and revisit the agenda. Respect the rhythm of the event.<\/p>\n<h2>Key Takeaways<\/h2>\n<p>The Scrum sprint review is not a status report. It\u2019s a feedback loop where value, transparency, and adaptation meet.<\/p>\n<p>Preparation isn\u2019t about perfect slides\u2014it\u2019s about clarity, relevance, and user focus.<\/p>\n<p>How to demo in sprint review? Stay focused on user value, use real examples, and keep the demo under 30 minutes.<\/p>\n<p>Stakeholder engagement is about inviting insight, not approval. Capture feedback, organize it, and act on it.<\/p>\n<p>Use diagrams\u2014not to impress, but to explain. Flowcharts, journey maps, and before\/after visuals make improvement visible.<\/p>\n<p>Remember: the sprint review is where Scrum becomes real. Not because work was completed\u2014but because learning began.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What happens if the sprint review doesn\u2019t go well?<\/h3>\n<p>It\u2019s okay. Not every review will be perfect. The goal isn\u2019t perfection\u2014it\u2019s improvement. Reflect on what went wrong, adjust your approach for next time, and keep the conversation going.<\/p>\n<p>If stakeholders were disengaged, ask why. If the demo took too long, simplify your flow. The retro will help you refine the process.<\/p>\n<h3>How do I handle conflicting feedback during the sprint review?<\/h3>\n<p>Don\u2019t resolve it in the moment. Capture all feedback, categorize it, and let the Product Owner assess priority. Use a weighted scoring model (effort vs. value) or stakeholder impact to guide decisions.<\/p>\n<p>Communicate that not every feedback can be immediate. But it will be reviewed and prioritized.<\/p>\n<h3>Can I include work that\u2019s not fully Done in the sprint review?<\/h3>\n<p>No. The Sprint Review is for the Increment\u2014only items that meet the Definition of Done. Including incomplete work undermines transparency and trust.<\/p>\n<p>If a feature isn\u2019t Done, it belongs in the backlog. The team can work on it in the next sprint.<\/p>\n<h3>How long should a sprint review be?<\/h3>\n<p>For a 2-week sprint, 1.5 to 2 hours is ideal. For longer sprints, increase time proportionally. The key is to stay focused and respect the timebox.<\/p>\n<p>Time should be split between demo (30\u201340%), discussion (40\u201350%), and backlog update (10\u201320%).<\/p>\n<h3>Who should attend the sprint review?<\/h3>\n<p>Everyone on the Scrum Team\u2014Product Owner, Scrum Master, Development Team\u2014plus stakeholders who were involved in the sprint goal or impacted by the deliverables.<\/p>\n<p>Invite users, support teams, or business analysts if they have a stake. Avoid inviting everyone just for show.<\/p>\n<h3>Is it okay to skip the sprint review if we\u2019re behind schedule?<\/h3>\n<p>No. Skipping the sprint review breaks the inspect-and-adapt cycle. Even if the team is behind, the review is still valuable.<\/p>\n<p>Use it to discuss what\u2019s not done, why, and what adjustments are needed. The sprint review is not a celebration\u2014it\u2019s a checkpoint.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Too many teams treat the sprint review as a formality\u2014just a slide deck to present completed work. But that\u2019s where the real learning begins. I\u2019ve seen teams deliver fully functional features only to have stakeholders say, \u201cThis isn\u2019t what we wanted.\u201d Not because the work was poor\u2014but because the feedback loop was closed too late. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1448,"menu_order":2,"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-1451","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>Scrum Sprint Review Guide for Beginners<\/title>\n<meta name=\"description\" content=\"Master the Scrum sprint review with this actionable guide for beginners. Learn how to demo in sprint review, engage stakeholders, and capture feedback effectively to drive continuous improvement.\" \/>\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\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Scrum Sprint Review Guide for Beginners\" \/>\n<meta property=\"og:description\" content=\"Master the Scrum sprint review with this actionable guide for beginners. Learn how to demo in sprint review, engage stakeholders, and capture feedback effectively to drive continuous improvement.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Polski\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data1\" content=\"8 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/\",\"name\":\"Scrum Sprint Review Guide for Beginners\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\"},\"datePublished\":\"2026-02-25T10:41:42+00:00\",\"description\":\"Master the Scrum sprint review with this actionable guide for beginners. Learn how to demo in sprint review, engage stakeholders, and capture feedback effectively to drive continuous improvement.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Scrum Essentials: Beginner\u2019s Guide to Agile\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Scrum Events in Detail\",\"item\":\"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Conducting Sprint Reviews: Feedback Loops for Improvement\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"name\":\"Visual Paradigm Skills Polski\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#organization\",\"name\":\"Visual Paradigm Skills Polski\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Polski\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Scrum Sprint Review Guide for Beginners","description":"Master the Scrum sprint review with this actionable guide for beginners. Learn how to demo in sprint review, engage stakeholders, and capture feedback effectively to drive continuous improvement.","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\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/","og_locale":"pl_PL","og_type":"article","og_title":"Scrum Sprint Review Guide for Beginners","og_description":"Master the Scrum sprint review with this actionable guide for beginners. Learn how to demo in sprint review, engage stakeholders, and capture feedback effectively to drive continuous improvement.","og_url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/","og_site_name":"Visual Paradigm Skills Polski","twitter_card":"summary_large_image","twitter_misc":{"Szacowany czas czytania":"8 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/","name":"Scrum Sprint Review Guide for Beginners","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website"},"datePublished":"2026-02-25T10:41:42+00:00","description":"Master the Scrum sprint review with this actionable guide for beginners. Learn how to demo in sprint review, engage stakeholders, and capture feedback effectively to drive continuous improvement.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/scrum-sprint-review-guide-beginners\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/pl\/"},{"@type":"ListItem","position":2,"name":"Scrum Essentials: Beginner\u2019s Guide to Agile","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/"},{"@type":"ListItem","position":3,"name":"Scrum Events in Detail","item":"https:\/\/skills.visual-paradigm.com\/pl\/docs\/scrum-essentials-beginners-guide-to-agile\/scrum-events-in-detail\/"},{"@type":"ListItem","position":4,"name":"Conducting Sprint Reviews: Feedback Loops for Improvement"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#website","url":"https:\/\/skills.visual-paradigm.com\/pl\/","name":"Visual Paradigm Skills Polski","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/pl\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#organization","name":"Visual Paradigm Skills Polski","url":"https:\/\/skills.visual-paradigm.com\/pl\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/pl\/wp-content\/uploads\/sites\/8\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Polski"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/pl\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1451","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1451\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/docs\/1448"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/media?parent=1451"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/pl\/wp-json\/wp\/v2\/doc_tag?post=1451"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}