Planning and retrospective are not about completing tasks. From the difficulty of setting goals, to methods for retrospective, and on to orienting around your own growth — a complete list of topics.
Part of the column “One-on-One Conversations” · Chapter 11
From daily and weekly reports to problem retrospectives: how to maintain baselines, record changes, judge impact, and turn data conclusions into verifiable action items.
Part of the column “Data Metrics Guide” · Chapter 5
The value of an engineering retrospective is not in retelling what happened or blaming individuals, but in turning an experience into improvements that can be verified, maintained, and reused.