Making Retrospectives Useful, Part I: Capturing Lessons Learned

Posted February 28, 2019 in Business Agility & Software Engineering Excellence

One of the techniques people in the Agile community argue for is retrospectives. A retrospective refers to a meeting held at the end of an iteration where teammates reflect on what they experienced and recommend improvements. It is an important tool because it allows the team to take advantage of their lessons learned. The bottom line is that organizations need to put processes in place to facilitate sharing. Besides being easy to use, developers need to be motivated to use these processes, or else the databases that are provided will remain unused.

About The Author
Donald Reifer
Donald J. Reifer is recognized as one of the leading figures in the fields of software engineering and management, with more than 40 years of progressive management experience in both industry and government. He has built businesses, managed key programs, and led major R&D initiatives. Mr. Reifer is often called upon by clients to review troubled programs, examine red team proposals, and perform competitive assessments with an emphasis on… Read More
Not a member? Gain Access to the Cutter Experts today — register now to read select open-access articles.