Project Management

Please login or join to subscribe to this thread

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

linkedin twitter facebook   Agile   Communications Management   Stakeholder Management  
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
The project retrospective meeting helps the team to analyze both successes and the failures, so the team and organization can improve how they work going forward. I think the main purpose of a project "postmortem" is to help the team to shed the tension, crisis and chaos from the project, so they can approach the next one with a good attitude and open mind. What is your opinion?
Sort By:
< 1 2 3 4 >
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Mar 14, 2018 5:02 PM
Replying to Diwakar Killamsetty
...
Both Respect and Courage is required from all the stakeholders to be part of retrospective meetings. Having said, they can be motivated by proper training - Agile Methodologies, Project know how, Project background and last but not the least - Technology insights.
Thanks, Diwakar for your response.
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Mar 15, 2018 6:01 AM
Replying to Keshava Subramanyam Pirati
...
Retrospective is a challenging part of the meeting to discuss what worked well and what didn’t in the past which can be useful to predict/plan in furture. Before meeting, share high level agenda to the team to make it easy for them to come prepared.
I agree, Kashava. Based on my experience it is very challenging.
avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Mar 15, 2018 1:13 PM
Replying to Paul Hollings
...
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
That's a good suggestion, Paul and thanks for your feedback on this.
< 1 2 3 4 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

We are ready for any unforeseen event that may or may not occur.

- Dan Quayle

ADVERTISEMENT

Sponsors