Seven project and programme managers contributed to a recent online discussion that covered good practice, processes, metrics, and handling the results of post project reviews.

• A common issue is that feedback is captured on a project-by-project basis with no central repository. This results in a lack of consistency in the way feedback is captured and often prevents subsequent projects benefiting from the feedback.
• Have processes in place to capture post-project feedback. Two main mechanisms for feedback are Post- Implementation Review (PIR) and Lessons Learned. Aim for this to be part of the embedded culture.
• There is no set time after project closure for gathering feedback. Decide at project closure when the feedback will be gathered.
• A key to success is keeping the relationship open. Project size influences the size of the project review. The degree of formality is the same regardless of project size
• A key message is ‘Create documentation during the project life cycle for PIR and Lessons Learned.’

Reports are free to organisations subscribing to the Corporate IT Forum - Want to know more?