Hey everyone, In agile software development, we have the concept of a “retro,” which is short for retrospective. At the end of every two-week sprint, the team talks about what went well, what didn’t go well, and what we can improve next time. Since last November, I’ve been running a retro on my personal life at the end of the week (typically on Sunday, either right before or after I write this newsletter). I ask myself what I wanted to get done, what I got done, why stuff didn’t get done, and what I want to do next week. (I’ve realized while writing this that I should probably expand to overall feelings about the week as opposed to only a task-oriented view of how things are going.) I’ve also created a
The Weekly Retro
The Weekly Retro
The Weekly Retro
Hey everyone, In agile software development, we have the concept of a “retro,” which is short for retrospective. At the end of every two-week sprint, the team talks about what went well, what didn’t go well, and what we can improve next time. Since last November, I’ve been running a retro on my personal life at the end of the week (typically on Sunday, either right before or after I write this newsletter). I ask myself what I wanted to get done, what I got done, why stuff didn’t get done, and what I want to do next week. (I’ve realized while writing this that I should probably expand to overall feelings about the week as opposed to only a task-oriented view of how things are going.) I’ve also created a