Agile Retrospectives Keep Failing. Here’s Why
<p>Are your sprint retrospectives a nightmare of silence? Mine sure are, as nobody gives seems to have any enthusiasm for doing a good job and pushing features out to customers.</p>
<blockquote>
<p>I think the constant refrain at work is why bother!</p>
</blockquote>
<p>In this article, I’d like to explore what is going wrong, and how that might be solved in both my and your organizations.</p>
<h1>Trustworthiness</h1>
<p>I’ve noticed that many scrum masters have learned the term <strong><em>psychological safety</em></strong> but have failed to learn how to put any guardrails into their processes. Our “agile practitioners” say we have to build psychological safety in an organization where <a href="https://medium.com/@tsecretdeveloper/the-secret-developers-productivity-hack-the-infinite-power-of-tomorrow-5afbb7afea7f" rel="noopener">developers never seem to use their webcams</a>.</p>
<blockquote>
<p>Does the term webcams even still exist?</p>
</blockquote>
<p>Here are some methods that can be used to promote team spirit within retrospectives and perhaps tease out learning from what happened. Here are some ways of achieving that loft goal:</p>
<h2>Modeling</h2>
<p>If the “bosses” in a video call don’t bother to turn their cameras on why would they rank and file? If you want people to show vulnerability and capacity to learn you can model that from the top.</p>
<p><a href="https://medium.com/@tsecretdeveloper/agile-retrospectives-keep-failing-heres-why-e6edfb24550">Read More</a></p>