{"id":3387,"date":"2022-05-10T15:58:21","date_gmt":"2022-05-10T14:58:21","guid":{"rendered":"https:\/\/agilebeyondboundary.com\/?p=3387"},"modified":"2023-10-30T11:23:35","modified_gmt":"2023-10-30T11:23:35","slug":"sprint-report","status":"publish","type":"post","link":"https:\/\/agilebeyondboundary.com\/index.php\/2022\/05\/10\/sprint-report\/","title":{"rendered":"Sprint Report"},"content":{"rendered":"\n<p>Transparency and Visualization is an important aspect of Agile way of working.  The Sprint report (team wise) is powerful a tool to enhance transparency and create a collaborative relationship between team and key stakeholder (sponsors, management, leadership and immediate customer).  Such a report is specially more useful in a client-vendor (buyer-seller) setup. <\/p>\n\n\n\n<p>Its important to understand that the aim of this report is not to create control, rather its to enhance transparency and trigger two way dialogue at right time. <\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"571\" src=\"https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Picture1-1024x571.png\" alt=\"\" class=\"wp-image-3389\" srcset=\"https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Picture1-1024x571.png 1024w, https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Picture1-300x167.png 300w, https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Picture1-768x428.png 768w, https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Picture1-1536x857.png 1536w, https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Picture1.png 1872w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p>Key Elements of this report <\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>3&nbsp;Sprint views <\/strong>&nbsp;&#8211; this report creates a quick summary of three sprints (last one, current, and next one). The last sprint \u2013 achievement\/misses; Current Sprint \u2013 commitment, stories, and the Next sprint \u2013 potential stories &amp; direction&nbsp;<\/li>\n\n\n\n<li><strong>Burndown <\/strong>(Sprint or Release or feature\/epic) &#8211; a snapshot&nbsp;of relevant burn down \u2013 how much % of story \/ SP deviled; how much pending;<\/li>\n\n\n\n<li>Open <strong>impediments and impact<\/strong>&nbsp;[to expedite resolutions]&nbsp;<\/li>\n\n\n\n<li><strong>Indicative Trend <\/strong>(red, amber, green) of overall health and progress<\/li>\n\n\n\n<li>All data on this report is directly copied from ALM tool (e.g. Jira or AzureDevOps or clickup)&nbsp;<\/li>\n\n\n\n<li>For multiple Squad, the Sprint report will have one slide for each Squad in a consolidated file<\/li>\n<\/ul>\n\n\n\n<p>You may download the template (blank sample report) from here <\/p>\n\n\n\n<div class=\"wp-block-file\"><a id=\"wp-block-file--media-ce1874dc-ccfb-4d1e-aa57-1f7c293f73c6\" href=\"https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Sprint-Report.pptx\">Sprint-Report<\/a><a href=\"https:\/\/agilebeyondboundary.com\/wp-content\/uploads\/2022\/05\/Sprint-Report.pptx\" class=\"wp-block-file__button wp-element-button\" download aria-describedby=\"wp-block-file--media-ce1874dc-ccfb-4d1e-aa57-1f7c293f73c6\">Download<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Transparency and Visualization is an important aspect of Agile way of working. The Sprint report (team wise) is powerful a tool to enhance transparency and create a collaborative relationship between team and key stakeholder (sponsors, management, leadership and immediate customer). Such a report is specially more useful in a client-vendor (buyer-seller) setup. Its important to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3389,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_oct_exclude_from_cache":false,"footnotes":""},"categories":[45],"tags":[],"class_list":["post-3387","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tool"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":6}},"_links":{"self":[{"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/posts\/3387","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/comments?post=3387"}],"version-history":[{"count":2,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/posts\/3387\/revisions"}],"predecessor-version":[{"id":3406,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/posts\/3387\/revisions\/3406"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/media\/3389"}],"wp:attachment":[{"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/media?parent=3387"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/categories?post=3387"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilebeyondboundary.com\/index.php\/wp-json\/wp\/v2\/tags?post=3387"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}