[Project Name] Post-Mortem Presentation Template

Slides:



Advertisements
Similar presentations
[Product Name] Marketing Plan
Advertisements

By Guy Yariv Project Closure – Finally…
Project Control Techniques
Project Lifecycle Section 6 - Closeout. Project Manager’s Role During Project Close-Out  Ensure that all project deliverables have been completed and.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Prof. Roy Levow Session 8.  Steps in Closing a Project  Getting Client Acceptance  Installing Project Deliverables  Documenting the Project  Post-Implementation.
Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.
Executive Session Director’s CD-3b Review of the MicroBooNE Project January 18, 2012 Dean Hoffer.
Project monitoring and Control
Week 3 Outline Post-Mortem By: Jamaral Johnson. 2 After Actions Review In this presentation I will do my best to highlight what went wrong. This is just.
Sage ERP X3 Standard Edition Methodology
Project Status [Project Name] [Presenter Name] This presentation will probably involve audience discussion, which will create action items. Use PowerPoint.
Complete Design & Gate Review. Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Project Execution Methodology
Project Management PTM721S
[Product Name] Marketing Plan
Project Management Jukka A. Miettinen September 4, 2006
SCT Project Management Issues
[Product Name] Marketing Plan
Reactive Attachment Disorder
Using Games to Effect Organizational Change
[Product Name] Marketing Plan
[Product Name] Marketing Plan
4.4 Monitor and Control Project Work
Project Management Managing Project Execution
Project Name Company Name Presenter Name
Project Name Company Name Presenter Name
Project Name Progress Report 1
[Product Name] Marketing Plan
[Project Name] [Presenter Name]
[Project Name] Post-Mortem
Project Management PTM721S
PROJECT NAME POST-MORTEM
Project Name | Company Name | Presenter Name
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Project Name Steering Committee Meeting Project Manager: Project Manager Name Program Manager: Program Manager Name Project Sponsor: Project Sponsor Name.
[Product Name] Marketing Plan
Mastering Change Control
Reporting Progress or Status
Conducting Self-Inspections
[Project Name] [Presenter Name]
[Product Name] Marketing Plan
Downloaded from بسم الله الر حمن الر حيم Sayed Jalil 11/23/2018 Downloaded from
[Project Name] [Presenter Name]
IS&T Project Reviews September 9, 2004.
[Product Name] Marketing Plan
Project Name Company Name Presenter Name
[Project Name] [Presenter Name]
[Product Name] Marketing Plan
Project - Execution stage
Employee engagement Close out presentation
Project Execution Activities
[Product Name] Marketing Plan
Project Name Company Name Presenter Name
Project Name Post-Mortem
Project Name | Company Name | Presenter Name
Issue Logs I want to implement a project
Effective Project Management: Traditional, Agile, Extreme
Reporting Progress or Status
Project Name Company Name Presenter Name
Project Overview.
Presenting Project Status
Software Reviews.
Native American Webquest
[Project name] [Presenter name]
Chapter 3 Managing the Information Systems Project
Executive Governance Template
Presentation transcript:

[Project Name] Post-Mortem Presentation Template

Performance Against Goals Actual: summarize what really happened in relationship to goals List progress against metrics Goal: state original goal or goals of project List key metrics (items for measuring success)

Performance Against Schedule Plan: summarize original schedule of project List key milestones Actual: summarize what really happened in relationship to plan List differences in terms of original dates (x weeks late, x months early, etc.)

Performance Against Quality Quality goal: state original quality goal or goals for the project List key metrics (items for measuring success) Actual: summarize what really happened in relationship to quality goals List progress against metrics

Performance Against Budget Budget: state original quality goal or goals for the project List key cost goals, expenditure limits Actual cost/expenditures: summarize what really happened in relationship to budget List progress against goals & limits

Post-Mortem By Department

Project Planning How Was the Project Planned? Who was responsible for original plans? How did that work? Right set of people? Was project well defined from beginning? Was there an actual written plan? How was project plan communicated? How well did that work?

Project Planning Was the Plan the Right One? Was the plan a good one? What was good? What was missing? Was the plan realistic? How did the plan evolve over time? Was the change good or bad? How did the changes affect the project? Key areas for improvement: Make very specific recommendations.

Research & Development How Was R&D Managed? How was the project managed through R&D? How many teams, number of people, reporting structure, etc. How well did that work? Improvements? How did the R&D teams communicate What methods, timing, etc. How well did that work?

Research & Development How Effective & Efficient Was R&D? Identifying & solving technical problems Were issues identified early enough? Were problems solved well? What worked? Didn’t work? Could be better? Estimates & execution Were estimates on track with actuals? What helped people estimate well? What caused people to estimate poorly?

Project Management How Was the Project Managed? Meetings: who/when/how often How well did this work? Communication: who/when/how often Changes: how tracked, communicated Other methods: email, schedules, databases, reports, etc.

Manufacturing Was team properly prepared to receive product? BOM & paperwork complete & accurate? Materials ordered & ready? Did product meet manufacturability goals? Were there unexpected delays or problems?

Quality Assurance & Support How was product quality measured? Was this effective? Efficient? How did final product compare against quality goals? How were quality issues resolved? Were support teams properly prepared? Is product quality consistent with support resources?

Marketing Did positioning match final product? Was positioning successful? Appropriate? Effective? Was product launch effective? Were marketing programs effectively implemented? Did product & launch meet marketing goals?

Sales Was channel & sales force appropriately informed about product? Did product and message meet customer need? Was timing appropriate? Cost? How do initial sales compare to goals? How has product been received?

Key Lessons

What Went Right Summarize in quick bullet points specific things that worked well Use specific examples: “daily 15-minute morning status meetings worked well” instead of “team communicated well”. Distribute or list network location of forms, procedures, reports, etc. that were found to be particularly useful.

What Went Wrong Summarize in quick bullet points specific things that caused problems Try to isolate specific attitudes, procedures, methods, timing issues, etc. that caused problems How did team respond to problems?

Recommendations By department or management level, record critical recommendations for future products of this type Distribute document or network location of more detailed summary of this presentation

Questions & Comments