• Community of Practice Retrospective As agile matures and its adoption increases, we continue to see mixed results and mixed opinions about ATDD. We hosted a community retrospective to share the successes and reflect on the challenges teams have experienced with ATDD on their projects. By increasing overall community learning, we can effectively focus our energy on individual, team, tool, and AAFTT improvements (Iterations / Sticky Minds October 2010)
  • Once Upon A Retrospective Children can teach us some extremely profound things – often when we least expect it.  Jennitta Andrea shares sage advice about project retrospectives that she learned while perusing the well-known children’s stories on her daughter’s bookshelf.  These insights will help improve the way you plan, facilitate, and participate in project retrospectives (Better Software May/June 2010)
  • Reinvigorate Your Project Retrospectives The difference between a retrospective that is considered dull and worthless and a retrospective that produces team bonding and valuable insignts is in the planning and preparation. All effective retrospectives share a common structure: safety, review history, insight mining, prioritization, and concrete action planning. Explore the different ways that iteration and milestone retrospectives fill in this structure based on the type of learning that we need to draw out of the team at a particular point in the project. Variations on the activities that fill in the structure are described and experienced first hand. (APLN Presentation, Feb 2009; Software Quality Discussion Group Presentation, Oct 2009). Here’s the summary retrospectives cheat sheet as well.
  • The Case Of The Missing Fingerprint (Better Software, 2007)This article describes an approach to conducting an end-of-project retrospective that captures both outcome and context, and advises how new projects can use these retrospective outcomes (Better Software, February 2007)

internationally recognized thought leader in agile requirements