Are our retrospectives valuable? Are our teams improving? These are two questions that come to mind when I think about comments or articles I've seen about resistance to retrospectives or the time spent in them. I think we can learn a lot by conducting a retrospective… on our retrospectives. Through such a retrospective we seek learning by exploring the following questions:
What we have to say, what you want us to hear.
That’s how our blog works. It’s interactive. Let’s learn together.
This past week, Dennis Corpman and I gave a presentation at IEEE ProCon, a long-standing annual Professional Development conference held by the Cedar Rapids section of the IEEE. Our presentation focused on lessons learned along the agile path. As a way of framing our exploration, we used Patrick Lencioni's Five Dysfunctions of a Team to examine team interactions in a daily standup, and we used elements of an Agile Mindset to examine a sprint retrospective.
The week of November 14th, I spent 3 days with fellow developers, leaders, and Agilists at the Techwell-organized AgileDev / Better Software/ DevOps East Conference and the Agile Leadership Summit. The keynotes and sessions were well attended, as well as the "hallway breakouts." As a compulsive note taker, I came back with 53 pages of notes, everything from more books on my to-read list, to "Aha!" insights. Here, I would like to share a few of my key takeaways from the conference…