Home > Agile, Development > Technical Retrospective (Part 1)

Technical Retrospective (Part 1)

October 3rd, 2007 Scott Lilly

We recently ran a technical retrospective on the project that I’ve been working on. The idea was to focus on just the development issues. This is the e-mail that I sent out to the developers on the team:

==========================================

We made the best decisions we could with the information (both facts and opinions) at the time. Now, we have more experience and are smarter. So, let’s see what changes we want to make for the future versions of PE.


This is a retrospective/brainstorming session for development practices only. There will be another retrospective for the whole project process.


Purposes of the meeting

  • Identify what we want to do more
  • Identify what we want to do less


Rules

  • This is not the place to criticize ideas
  • All ideas are encouraged (even ‘crazy’ ones)
  • Try to build and combine on the ideas of others
  • Let everyone complete their comments


Focus on these results

  • Improve maintainability
  • Improve reliability
  • Improve usability
  • Improve testability
  • ???
Categories: Agile, Development Tags:
Comments are closed.