Differences between revisions 14 and 15
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
 * Jim Shore's [http://jamesshore.com/Agile-Book/retrospectives.html brief recap] from ''The Art of Agile Development'' (ISBN:0596527675)

Feedback is very important in tuning software development, but it's also needed in tuning the software development process. It comes in two major forms, introspection and retrospectives. Both involve looking back at what you've done, what went right, what could be improved, but introspection is solo and retrospectives involve the team.

In the "old days," a retrospective was called a project "post mortem," done after the project was finished and the team was about to disperse. A bit late to use the lessons learned in it, don't you think?

From experience and the literature I've read, post mortems are frequently skipped, especially on failed projects. And failed projects may have the most to teach us.

iDIAcomputing: IntrospectionAndRetrospectives (last edited 2012-02-02 16:56:32 by GeorgeDinwiddie)