The retrospective can be the most challenging of the Scrum activities, because, well, people are involved. A former student, Vijay, asked me:
The scrum master is facilitating the retrospective meeting by hearing the positive and negative from the team members. Should the scrum master or team members validate each other’s feedback during the retrospective? I hope the answer is….
Dear Vijay, I think the purpose of the first phase of a retrospective is to seek understanding. Different people in the team will have different truths. The objective is to understand all the truths, rather than to find the truth. So I prefer to ask the question, “what happened?” Just the facts, no judgements or accusations. Oh, by the way the left side (top half) of the flipchart, this is for things that made you happy. The other half is for things that made you sad. It is helpful to understand the mood, but don’t ask the question too soon, lest people focus too much on the thumbs up or down aspect of the question.
As a Scrum Master, it’s my job is to prevent debate and other downward spirals. That’s right, there is no such thing as a constructive debate! It drives people into their corners and makes agreement and consensus much more difficult. So people can ask clarifying questions of each other, but not rebut or challenge what was said, justify their own behavior or criticize others. “We understand and truly believe, everyone is doing the best job they can….” So we look for that 80% that everyone can agree on. This is the better basis for achieving a consensus for action.
As for recording, At each step of the retrospective, I would get cards up on a flip chart or pin board, then take a picture. As Scrum Master, I would only record individually those points that the team wants to act on in this sprint.
For a more complete discussion, check out “How we do a retrospective.”
|cookielawinfo-checkbox-advertisement||1 year||Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .|
|cookielawinfo-checkbox-analytics||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".|
|cookielawinfo-checkbox-functional||11 months||The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".|
|cookielawinfo-checkbox-necessary||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".|
|cookielawinfo-checkbox-others||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.|
|cookielawinfo-checkbox-performance||11 months||This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".|
|mailchimp_landing_site||1 month||The cookie is set by MailChimp to record which page the user first visited.|
|CONSENT||2 years||YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.|
|_ga||2 years||The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.|
|_gat_gtag_UA_42152348_1||1 minute||Set by Google to distinguish users.|
|_gcl_au||3 months||Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services.|
|_gid||1 day||Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.|
|NID||6 months||NID cookie, set by Google, is used for advertising purposes; to limit the number of times the user sees an ad, to mute unwanted ads, and to measure the effectiveness of ads.|
|test_cookie||15 minutes||The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.|
|VISITOR_INFO1_LIVE||5 months 27 days||A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.|
|YSC||session||YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.|
|yt-remote-connected-devices||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|yt-remote-device-id||never||YouTube sets this cookie to store the video preferences of the user using embedded YouTube video.|
|COMPASS||1 hour||No description|
|cookies.js||session||No description available.|
|S||1 hour||No description available.|