Professional Documents
Culture Documents
Post Implementation Review - Project Debriefing
Post Implementation Review - Project Debriefing
doc
1
/var/www/apps/collegelist/repos/collegelist/trunk/collegelist/tmp/scratch4/3170098.doc
Tips - Keep the conversation light and be sure that everyone understands the purpose of
the meeting: to improve the process, not to complain. The meeting should last no longer
than 1 hour to prevent conversations from running on.
Follow-up - The comments should be taken very seriously and followed up on, another
reason for developer participation, to show that we are serious. A summary of the
discussion will be sent to the participants. The recipients should focus on suggestions of
what to avoid in the future and what changes can improve the process. The information
to share with peers will be sent to other project teams and the HR and Financial
Computing Committee.