Looking back to move forward

Retrospectives are a common reflection practice on most software development teams. A few of my favorite formats:

Start / Stop / Continue

• What should we start doing?
• What should we stop doing?
• What should we continue doing?

Retro+

• What went well? Who helped you out this sprint?
• What did you learn?
• What could have gone better? What was your most frustrating moment?
• Does anything still puzzle you? What feels unresolved?

Retro’ing an artifact or resource

• What should we keep? (What’s working well?)
• What should we add or change? (What’s missing?)
• What should we remove? (What’s not helpful or distracting?)