A reader asked what he could do to inject some life into his sprint retrospectives. He’d been using two questions “What did we do well?” and “What could we do better?” for several sprint retrospectives with the general goal of improving performance. Nothing really...
A while I go I pointed out the reasons *not* to have a retrospective. There are plenty of reasons *in favor* of having retrospectives (after every iteration): A well run retrospective enables the team to:step back and take a “whole system” view of their methods and...
Retrospectives are a great way for teams to inspect and adapt their methods and teamwork after each iteration and release. And they’re a great way for teams to build on success, learn from hard times, or bring closure when a project ends. But they’re not for good for...
[rant]Last week I heard someone espousing a new form of project review called a Retrospective. Here’s what she advised:Anonymous feedback via survey or questionnaireRanking of questionnaire resultsFunctional groups discussing questionnaire results in...
