Retrospectives in Retrospect

You don’t sell products.
You sell the products of your process.
Your process is your product!
  1. List some good and bad things that happened. The list doesn’t have to be exhaustive.
  2. Drill down. Repeatedly answer the question “why?” until you get to the root cause of each. Typically, this takes five whys. In the case of good things, the root cause is a strength. It needs to be protected and amplified. In the case of a bad thing, the root cause is a blocker and needs to either be removed, or treated as a bottleneck, the center of gravity around which your process flows. Sound mysterious? Read The Goal.
  3. Finally, come up with a short list of changes to your process from the insights you just gathered.
  4. Actually do the changes.
  5. Repeat next week. (If you didn’t do the changes, list that as one of the bad things.)

--

--

--

Software Crafter at 8th Light Consultancy, Organizer for Fullstack LA meetup, Eagle Scout, Theatre Person, Taoist Philosopher among other passions.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Some extra tips that would have helped me before taking the AWS certification exam

Three Starter Repositories For Your Next GraphQL API

Logos for the business and 3 repositories.

Hunting down a Google’s Bug in Android

Flutter TODO APP With GetX and Sqflite

The fastest way to get a Jupyter-based local development environment for Apache Spark 3 in Scala

Kubernetes Prometheus Stack

Stop using Dockerfile!

Fluentd vs. LogStash: A Feature Comparison

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ian Carroll

Ian Carroll

Software Crafter at 8th Light Consultancy, Organizer for Fullstack LA meetup, Eagle Scout, Theatre Person, Taoist Philosopher among other passions.

More from Medium

Agile Quickie: Working Software & Responding to Change

An excellent agile project manager ~ A typical housewife (Homemaker)

A methodology for everyone: how I learned to stop worrying and love Agile — Part II

Reasons NOT to Use Velocity for Sprint Planning