Retrospectives - I get the feeling people either love them or hate them.
Maybe this is just because we like to have binary "this vs. that" arguments on this platform...or maybe there's something to be learned from the emerging patterns of sentiment towards the concept.
What is a retrospective?
Well, straight away we run into one of those "ask 100 people, get 143 answers" problems.
A retrospective is a retrospective, whatever that means to you and your organization.
Yes, I know that is a frustratingly non-committal and non-prescriptive take, but if we bring it from an über-abstract philosophical level down to ground level, what I mean is there is no right or wrong answer to the question...a retrospective is whatever you think it is.
Now here's where I'd like to propose the injection of a little framing - what if you discovered a way to give people a sense of ownership in their work, the confidence of being able to speak up safely and be heard, and the feelings of joy and connectedness that come with winning together as a team?
This is what a retrospective is to me.
Strip out any rigid definitions, and I see the concept of the retrospective as an invaluable opportunity to reflect and grow, both as individuals and as teams.
I see retrospectives as a natural way to close out cycles and prepare for what comes next.
"Oh, retrospectives are just another dumb Agile ceremony."
Maybe. What's wrong with a little ceremony? Is it more comfortable to frame it as a "ritual" instead?
A ritual that promotes reflection and the capturing of new knowledge to establish feedback loops that reinforce positive behaviors?
A ritual for celebrating wins and connecting the dots from individual contributions to the customer value created by the team (and ultimately the organization)?
What's not to like about that?
Next Page | Previous Page | Page Name | Published Date |
|---|---|---|---|
April 26, 2024 |
