{"id":422,"date":"2019-07-22T23:30:14","date_gmt":"2019-07-22T21:30:14","guid":{"rendered":"http:\/\/p4dev.hardscrum.com\/?p=422"},"modified":"2021-05-13T16:54:37","modified_gmt":"2021-05-13T14:54:37","slug":"retrospective","status":"publish","type":"post","link":"https:\/\/p4dev.hardscrum.com\/en\/retrospective\/","title":{"rendered":"Team Retrospective"},"content":{"rendered":"<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Team Retrospective gives the team the opportunity to review themselves and <\/span><span style=\"vertical-align: inherit;\">to identify and plan <\/span><span style=\"vertical-align: inherit;\">improvements in the way they work for the upcoming <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/iteration\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">iteration<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> . <\/span><span style=\"vertical-align: inherit;\">It takes place between the <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/review\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Review<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> and the next <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/planning\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Team Planning<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">. <\/span><span style=\"vertical-align: inherit;\">For a four-week iteration, an upper limit of three hours is set. <\/span><span style=\"vertical-align: inherit;\">The meeting is usually shorter for shorter iterations. <\/span><span style=\"vertical-align: inherit;\">The <\/span><\/span><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Scrum Master <\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">ensures that the meeting takes place and that all participants understand its purpose. <\/span><span style=\"vertical-align: inherit;\">The Scrum Master ensures that the meeting is constructive and productive. <\/span><span style=\"vertical-align: inherit;\">The Scrum Master teaches everyone how to adhere to the time frame (time box). <\/span><span style=\"vertical-align: inherit;\">Due to its responsibility for the P4 process, the Scrum Master takes part in the Team Retrospective as an equal member. <\/span><span style=\"vertical-align: inherit;\">The Team Retrospective is being held to &#8230;<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">to review how the past iteration was in terms of people, relationships, processes, infrastructure and tools involved;<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">identify the most important and possible improvements and put them in order; <\/span><span style=\"vertical-align: inherit;\">and<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">create a plan for implementing improvements to the way the team works.<\/span><\/span><\/li>\n<\/ul>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">The Scrum Master encourages the team to improve their development processes and practices within the P4 framework to work more effectively and satisfactorily in the upcoming iteration. <\/span><span style=\"vertical-align: inherit;\">In each Team Retrospective, the team works out ways to improve result quality by adapting the processes accordingly or by defining-of-done, provided these changes are appropriate and do not conflict with product or company standards. <\/span><span style=\"vertical-align: inherit;\">At the end of the Team Retrospective, the team should have identified improvements for the upcoming iteration. <\/span><span style=\"vertical-align: inherit;\">The implementation of these improvements in the next iteration is the adaptation effort for self-examination of the team.<\/span><\/span><\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">In the meantime, there are many methodological approaches and questions for the course of the Team Retrospective, e.g.<\/span><\/span><\/p>\n<ul>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Glad, Sad, Mad<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Keep, change, puzzled<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Good, problems, questions<\/span><\/span><\/li>\n<li><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Start, stop, keep, more, less<\/span><\/span><\/li>\n<\/ul>\n<p>The <a href=\"http:\/\/p4dev.hardscrum.com\/delegation-poker\/\">Delegation Poker game<\/a> is particularly suitable for negotiating the delegation of responsibility to the team.<\/p>\n<p><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">There <\/span><span style=\"vertical-align: inherit;\">are many more ideas and suggestions <\/span><span style=\"vertical-align: inherit;\">under <\/span><\/span><a href=\"https:\/\/www.funretrospectives.com\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Fun Retrospectives<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> or <\/span><\/span><a href=\"https:\/\/retromat.org\/en\/\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">Retromat<\/span><\/span><\/a><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\"> .<\/span><\/span><\/p>\n<p><span style=\"color: #ffffff;\"><span style=\"vertical-align: inherit;\"><span style=\"vertical-align: inherit;\">.<\/span><\/span><\/span><\/p>\n<hr \/>\n<p>Further suitable links:<\/p>\n<table  class=\" table table-hover\" >\n<tbody>\n<tr>\n<td>Events<\/td>\n<td>Roles<\/td>\n<td>Groups<\/td>\n<td>Artifacts<\/td>\n<\/tr>\n<tr>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/planning\/\">Team Planning<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/sync\/\">Team Sync<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/refinement\/\">Team Backlog Refinement<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/review\/\">Team Review<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cycleretro\/\">Cluster Retrospective<\/a><\/p>\n<p><span style=\"color: #ffffff;\">.<\/span><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/organisations-retrospektive\/\">Organisation Retrospective<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/productowner\/\">Team Product Owner<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/systemengineer\/\">Team System Engineer<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/scrummaster\/\">Team Scrum Master<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/rteamlevel\/\">Working Team<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/cop\/\">Community of Practice<\/a><\/td>\n<td><a href=\"http:\/\/p4dev.hardscrum.com\/teambl\/\">Team Backlog<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/ateamlevel\/\">Inspectable Results<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/dod\/\">Team DoD<\/a><\/p>\n<p><a href=\"http:\/\/p4dev.hardscrum.com\/improvementbacklog\/\">Team Improvement Backlog<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"The Team Retrospective gives the team the opportunity to review themselves and to identify and plan improvements in the way they work for the upcoming iteration . It takes place between the Team Review and the next Team Planning. For a four-week iteration, an upper limit of three hours is set. The meeting is usually&hellip;","protected":false},"author":3,"featured_media":1891,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,34,21],"tags":[501,363],"translation":{"provider":"WPGlobus","version":"2.10.10","language":"en","enabled_languages":["de","en"],"languages":{"de":{"title":true,"content":true,"excerpt":false},"en":{"title":true,"content":true,"excerpt":false}}},"_links":{"self":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/422"}],"collection":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/comments?post=422"}],"version-history":[{"count":19,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/422\/revisions"}],"predecessor-version":[{"id":1524,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/posts\/422\/revisions\/1524"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media\/1891"}],"wp:attachment":[{"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/media?parent=422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/categories?post=422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/p4dev.hardscrum.com\/en\/wp-json\/wp\/v2\/tags?post=422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}