I was asked to write about “Making Agile Retrospectives Productive” for SitePoint. Here’s an excerpt:
One of the greatest advantages of an agile workflow is that it makes time for intentional reflection to encourage constant improvement. The retrospective ritual, traditionally held at the end of a sprint, gives the team a chance to discuss everything that stood out in the previous sprint. This includes looking at what went well and what didn’t, and making course corrections.
But carving out time from a busy production schedule for a retrospective meeting that doesn’t produce features for the product can be a tough sell in a fast-paced and competitive industry. Here are a few possible objections that are worth listening out for, and ways to address them.
Read the rest of my article about Making Agile Retrospectives Productive on SitePoint.