{"id":54064,"date":"2021-12-13T09:00:48","date_gmt":"2021-12-13T03:30:48","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=54064"},"modified":"2022-01-13T11:51:25","modified_gmt":"2022-01-13T06:21:25","slug":"why-you-should-not-include-stakeholders-in-the-sprint-retrospective","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/why-you-should-not-include-stakeholders-in-the-sprint-retrospective\/","title":{"rendered":"Why you should not include Stakeholders in the Sprint Retrospective"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">Let&#8217;s first understand what is a Sprint Retrospective. Sprint Retrospective is one of the agile ceremonies that is conducted on the last day of the sprint and is focused on examining the performance and improvement areas more at a process level. <span style=\"font-weight: 400;\">If you are following sprints of longer duration say of a month, try to split the sprint retrospective into two and have a checkpoint after two weeks. This is recommended to not let any improvement area wait for a long time.<\/span><\/span><br \/>\n<span style=\"font-weight: 400;\">The process includes everything that has an effect on the working of the scrum team. This includes open discussions with touch points related to practices, team behavior, collaboration, availability, organization disruptions, external threats, tools, etc.<span class=\"Apple-converted-space\">\u00a0<\/span><\/span><br \/>\n<span style=\"font-weight: 400;\">To recap, a scrum team consists of a product owner (PO), a scrum master and the development team. Scrum teams are self-organizing and cross-functional teams who choose how best to accomplish their work. This team works towards setting the sprint goal and delivering it.<\/span><\/p>\n<h4><b>As a best and highly recommended practice, only the scrum team should be part of the sprint retrospective<\/b><\/h4>\n<p><span style=\"font-weight: 400;\">Any internal or external stakeholders should not be part of the sprint retrospective.<\/span><br \/>\n<span style=\"font-weight: 400;\">Why?<\/span><\/p>\n<p><img decoding=\"async\" loading=\"lazy\" class=\"alignnone size-full wp-image-54618\" src=\"\/blog\/wp-ttn-blog\/uploads\/2021\/12\/09.png\" alt=\"\" width=\"860\" height=\"339\" srcset=\"\/blog\/wp-ttn-blog\/uploads\/2021\/12\/09.png 860w, \/blog\/wp-ttn-blog\/uploads\/2021\/12\/09-300x118.png 300w, \/blog\/wp-ttn-blog\/uploads\/2021\/12\/09-768x303.png 768w, \/blog\/wp-ttn-blog\/uploads\/2021\/12\/09-624x246.png 624w\" sizes=\"(max-width: 860px) 100vw, 860px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Because the sprint retrospective is focused on people, relationships, tools and environment. With the involvement of the stakeholders, teams don\u2019t open up in front of them and hesitate to provide any actionable feedback concerning the scrum team. The most common outputs seen in the sprint retrospective with stakeholder involvement are very general like, \u2018the sprint was good\u2019, \u2018team was supportive\u2019, etc. which is good but does not add any constructive value to the purpose of this event. Teams find it more comfortable to share their honest opinions in the absence of the stakeholders simply because of the trust factor within the scrum team which is key to Agile. Also, remember that Scrum teams are self-organizing and cross-functional who choose how best to accomplish their work, rather than directed by others outside the team.<span class=\"Apple-converted-space\">\u00a0<\/span><\/span><br \/>\n<span style=\"font-weight: 400;\">Would you want to flag your team\u2019s shortcomings in front of the internal or external stakeholders? If no, follow the best practice of doing sprint retrospectives within a scrum team only.<\/span><\/p>\n<div class=\"ap-custom-wrapper\"><\/div><!--ap-custom-wrapper-->","protected":false},"excerpt":{"rendered":"<p>Let&#8217;s first understand what is a Sprint Retrospective. Sprint Retrospective is one of the agile ceremonies that is conducted on the last day of the sprint and is focused on examining the performance and improvement areas more at a process level. If you are following sprints of longer duration say of a month, try to [&hellip;]<\/p>\n","protected":false},"author":1420,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":35},"categories":[1993],"tags":[324,4617,936,3913,4918,4917],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/54064"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1420"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=54064"}],"version-history":[{"count":4,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/54064\/revisions"}],"predecessor-version":[{"id":54619,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/54064\/revisions\/54619"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=54064"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=54064"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=54064"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}