How can I motivate team members to participate in project retrospective analysis?

Anish,

Like previous comments should be done on a regular basis, so project could benefit before the end.

Waiting at the end in large project is loosing lot of information, people are already move to other projects and can't contribute.

Glad to know about your experience, Sante.
I have mixed response, so need to try something different. May be this works fine in a projectized organizational structure.

Something I also have done before Anish, and this goes for my meetings with virtual team members to make them feel inclusive, is to have a mug created with their name on it, placed around the table with a small gift perhaps then and they drink a beverage from that mug, like hot chocolate or coffee etc. It's a simply gesture but psychologically is creates a sense of "home" with a warm mug in their hands with their name on it, which creates inclusion and recognition. When these factors are in play, people are more likely to open up and cooperate. I usually put the name of the project and the year also, and sometimes a "Thank You" placed there too.

I think it is vital to explain to everyone on the team why this is such an important step and how it will actually help each project member in a similar situation or in similar projects.
In my experience explaining why things are done and why one considers them important can really help increase awareness and motivation to participate.

Agree with much of what has been said in this thread and Walter has made a very important point!

But as PM you can operate an open-door, stripes-at-the-door policy to encourage all project resources to communicate.

I also use regular retrospectives when milestones are reached, it keeps it recent and fresh in people's minds. It can also be shorter and less intense than an end-of-project saga.

In addition, use a feedback form, The Good, The Bad and the Ugly, it is less formal and can be anonymous so removes the fear of speaking out. If distributed before a retrospective, as PM, you can table the items received, allowing the originator to participate in discussion rather than being seen to have raise the topic.

Paul

This retrospective analysis can only happen if:

a) One or two meetings are held to review all project obstacles, unexpected events and workarounds. Identifying resources and skills involved.
b) Team members are given time to ellaborate and propose procedures, recipes, checklists, etc for the next project. No time to ellaborate = a waste of time. People will not dedicate to writing the retrospectie analysis if they are being pushed to work right now on the next project
c) Team members receive an incentive (company recognition, a bonus, etc) if their proposed idea results in improvements in the next projects.