If the project was fairly straightforward and there weren't too many (or any) lessons to learn, this could be done to gather stakeholder feedback including satisfaction levels, but this would be the exception, not the rule.
I've done this more for fairly routine short term service engagements where the stakes are fairly low.
An electronic survey is a more ordenated way to keep and computate results, rather than an informal conversation with stakeholders. This method could be adopted formally to apply in all projects. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
To what end? Doing a 'debrief' at the end of a project can be done to understand what went well and not so well in the project or it can be done to understand if the implementation was successful.
I am yet to see any evidence that a 'debrief' to understand what went well and what did not add any value. These are the so-called lessons learned and if you wait until the end to understand lessons learned you have learned nothing.
If it is to understand if the implementation was successful i.e. the adoption rate is good then an electronic survey is a good approach. Saving Changes...
