Retrospective meetings have been commonplace in software development teams for many years. Teams hold a meeting at the end of a project or milestone to discuss successes and failures. They use the data from that meeting to look for ways to create more success and less failure in future projects or milestones.
Agile teams in particular have embraced retrospectives as a way to drive continuous improvement into both teams and processes. As stated in one of the twelve principles behind the Agile Manifesto, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." In this month's column, I dissect this principle and examine a few key elements of effective retrospectives. Read the full article at Visual Studio Magazine.