The Ant and The Elephant Boston SPIN蚂蚁和大象波士顿旋转.pptVIP

11/30/98 Through the Looking Glass - How to do a Post Project Review Barbara Purchia February 20, 2001 Rational Software bpurchia@ Agenda A Rose by Any Other Name Post Project Review (PPR) Project Retrospective Project Legacy Project Summary Post Mortem Post Partum What is a Post Project Review? A summary of project development, start to finish A brief description and analysis of Project activities Results Lessons learned Recommendations An improvement tool NOT a record of failures Why Should We Do a Post Project Review? Learn from project experiences Retain knowledge for future projects Understand how your project was done Identify areas to improve Understand successes Provide team closure When Do I Do One? For completed, terminated, or cancelled projects No more than 30 days after project end NOT before project release When all critical participants can attend During the project After a major project milestone At designated schedule points When things are not going well What’s Involved? Collect the information Technical Managerial Metrics Schedules Anything kept during the project Manager or project logs Emails ... What’s the Deliverable? Concise documented information summary Development activities Project metrics Estimates and actuals Technical and managerial lessons learned Recommendations for future projects Focused only on the project and the processes How Do I Start? Hold a meeting including ALL participating functions Project management team Affected functions AND/OR Request input via email Remote sites Managerial lessons learned Filtered to be unattributable What Is a PPR Meeting? A tool for reviewing and analyzing the project Promote discussion on improvements Involve a critical mass of those directly involved Promote discussion of all project areas Deliverables Team dynamics Processes Provide input for the PPR document Provide closure for the project team What Doesn’t the PPR Meeting Do? Assign blame to any individual or group Provide an