Lessons Learned About Lessons Learned

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog


View Posts By:

Cameron McGaughy
Marian Haus
Lynda Bourne
Lung-Hung Chou
Bernadine Douglas
Conrado Morlan
Kevin Korterud
Peter Tarhanidis
Vivek Prakash
Cyndee Miller
David Wakeman
Jen Skrabak
Mario Trentim
Shobhna Raghupathy
Roberto Toledo
Christian Bisson
Jess Tayel
Rex Holmlin
Taralyn Frasqueri-Molina
Wanda Curlee

Recent Posts

Move Beyond Herding Cats

Strategy In a VUCA World—Part 2

Strategy In a VUCA World—Part 1

Just Ignore the Trends—and Run to the Noise

The Brexit Effect—Deal With It

Categories: Agile

Many teams benefit from reflecting on their process after they complete their project. Any errors in the process, however, have already had their impact. Agile software development includes ways we can improve our lessons learned - not just for software, but for any project. These lessons from agile projects may help your projects too.

Lesson 1: Perform lessons learned sessions during the project.
This lets you benefit from your ideas in time to make a difference.

Lesson 2: Smaller, more frequent meetings flow better.
There aren't as many items to discuss and it becomes easier to focus on observations.

Lesson 3: Don't whine, refine.
Avoid spending a lot of time digging into why problems happened. There won't be enough time to plan for positive changes.

Lesson 4: Follow the cadence of change.
Sometimes we forget the team will be busy with work. Try limiting the changes to two actions. But nail those actions! And don't start new process improvements until the other ideas have been deployed.

Lesson 5: Changes should be by the team, for the team.
Lessons learned should not be viewed as a scorecard -- it will make all the metrics climb to suspiciously good levels. Management should have visibility into the process used and some lessons learned, and anonymous examples of triggers that led to their discovery. But the retrospective itself has to be a judgment-free zone where all problems can be discussed.

If you're using scrum or another agile method, this might sound familiar. Lessons learned or retrospectives are built into your iteration cycle.

How do these tips fit with your project's life cycle model? 
Posted by William Krebs on: July 01, 2010 12:39 PM | Permalink

Comments (4)

Please login or join to subscribe to this item
I disagree with the comment under Lesson #3. While they are correct in saying, "Don't whine, refine," I don't believe the explanation under that is always true. Without finding the cause of a problem, we aren't able to take appropriate and corrective actions.

Deepa Susan Koshy,PMP
With respect to comment under Lesson #3 - We can take a median approach. To understand the root cause, it is important to ask 'why?'

The '5 why?' is a known root cause analysis technique. But we need to keep in mind to stop the drill if and when the cause points directly to personal traits of people involved. Because nothing much can be achieved by pointing to people's inherent weaknesses. So a PM must exercise judicious judgment and must know when to stop asking 'why?' and take alternate decision/ path at this point.

Alexei Kim

Lessons 6. Don't forget to review all project documents and you will find a lot of lessons learned.

Best regards,

Ikechukwu Omeoga
The crux of having a lessons learned is finding out what went wrong and why it went wrong, every time spent on trying to figure out why problems happened is worthwhile.

Please Login/Register to leave a comment.


"An intellectual snob is someone who can listen to the William Tell Overture and not think of The Lone Ranger."

- Dan Rather