Any project manager who hasn’t been hiding under a rock in
recent years knows about Agile Methodologies. One common way of delivering this
methodology is through Scrum, where one will discover prescribed activities called
“ceremonies”. One of these ceremonies is
a retrospective. This is where the delivery team meets to have a candid
discussion about what was done well and what wasn’t. The objective is to find
ways to improve how the team functions and produces. This ceremony helps the
team finish the project with a little respect. Simple.
If only life were like Scrum. Right?
Well, it is.
A project is often defined as a temporary effort to create a
unique result. Coincidently, this also accurately defines my life. I definitely
am unique. I’ve been reminded all too often that I’m only temporary. And to be
remembered as one who made a difference, who produced something positive, is the
end game.
So, there you have it; I’m a project. Now all I need is a
methodology to help me get to that glorious end. Enter Scrum.
On occasion I think back, and I think forward, and I wonder.
I wonder about how I’ll complete this project that I am with a little respect. To
help me out, it seems that adopting this Scrum retrospective ceremony would be worth
a try. Here we go.
Part one: what have I done well?
I want to believe I’m balanced. Sometimes I’m too critical of
myself. Sometimes I’m the most confident expert on my own opinion. But how
could I possibly have an unbiased opinion about any good I may have done? It
may be best to turn to others for their input. But don’t think you’ll get the
answer here in this article. This is more about how to arrive at the answer in
the title, not about me. Try not to be disappointed.
When working a project, look to the team to recognize what
the team has done well together. If you frame the question in that way, you
will more likely receive input that recognizes and builds upon teamwork. This
is the best kind of work, in my opinion. To kick off the discussion you may
offer a fill-in-the-blank statement: I think the team did well when we [did
what?] which resulted in [the positive output].
You might also ask the team to recognize other individual’s
good actions. But when you do this, focus on actual results, not feelings. You
won’t find a feeling listed as a Statement of Work deliverable. If Johnny did
something great, focus on how that great thing contributed to a positive, tangible
result. This will reinforce and encourage actual behavior that produces results.
The statement might be: When [person’s name] did [action] his actions resulted
in (or contributed greatly to) [this deliverable for the project].
Use the same approach in your self-project. No one is an
island; we’re all connected. Many, MANY people have contributed to who I am and
many more will contribute to who I will become. But don’t dismiss your own
contribution. Everyone contributes. Everyone counts. Be generous to yourself as
well as to those who helped you along the way.
Second part: what have I done that didn’t go well?
If you’re expecting me to answer this question here, you’re
aiming too high. But I will say this: a little introspection will go a long way
in this retrospective exercise.
The part of me that is too critical of myself shines bright
here. But let’s not get too carried away. Recognition without criticism is the
way to go. Recognize the problem, examine the reasons, then formulate a
corrective action for each reason. Fix the root cause and you’ve eliminated the
problem.
On the project, this is a good time to de-personalize things
by asking what the team did not do well. Stay focused on actual results.
Rarely is one person the sole cause of a problem within a team trying to
accomplish a goal. It takes a team to be successful. It takes a team to fail.
Another good piece of advice is about the approach. Identifying
a problem without a potential solution is just empty criticism. A former boss would
tell us not to come to him with a problem if we didn’t also suggest with a way
to fix it. Take that advice. Apply it here.
A retrospective ceremony is a good time to let the guard
down, be super honest, and set your purpose on finding ways to become better. Take
the person out of the equation. It’s not the best time to have harsh criticism
of others. Fix yourself on the behavior not the person.
It’s also a good time to do a little self-examination of your
own performance. Looking inward is the best way of finding ways to improve what
is outward. It’s been said, real change comes from within.
All this can be equally applied to our self-project. It’s
better to think about what I can control in myself, rather than finding fault
in others, of which we have little actual ability to control or change.
There you have it. A little retrospective ceremony is a
great way to continually improve your team and yourself.
What have I done with my life? It’s been a process. I’ve
done some good, and some not so good. But with some retrospective ceremonies it’s
bound to get better.
