PROJECT NAME POST-MORTEM

Slides:



Advertisements
Similar presentations
[Product Name] Marketing Plan
Advertisements

By Guy Yariv Project Closure – Finally…
Project Control Techniques
Problem Management SDG teamIT Problem Management Process 2009 Client Services Authors: M. Begley & R. Crompton, Client Services.
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.
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.
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.
The Budgeting Process 7. OBJECTIVE 1: Define budgeting, and explain budget basics.
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
MGT 437 OUTLET Become Exceptional/mgt437outlet.com FOR MORE CLASSES VISIT
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
BUSINESS DRIVEN TECHNOLOGY
[Product Name] Marketing Plan
[Product Name] Marketing Plan
4.4 Monitor and Control Project Work
6/11/2018 Marketing Plan Your Name.
Project Management Managing Project Execution
Project Name Company Name Presenter Name
Project Name Company Name Presenter Name
[Product Name] Marketing Plan
[Project Name] [Presenter Name]
[Project Name] Post-Mortem
Project Management PTM721S
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
12/7/2018 Marketing Plan Your Name.
Project Name Company Name Presenter Name
[Project Name] [Presenter Name]
[Product Name] Marketing Plan
Project - Execution stage
Project Execution Activities
[Product Name] Marketing Plan
[Project Name] Post-Mortem Presentation Template
Project Name Company Name Presenter Name
Project Name Post-Mortem
Project Name | Company Name | Presenter Name
Issue Logs I want to implement a project
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
Presentation transcript:

PROJECT NAME POST-MORTEM

Performance Against Goals ACTUAL State original goal or goals of project Summarize what really happened in relationship to goals List key metrics (items for measuring success) List differences in terms of original dates (x weeks late, x months early, etc.)

Performance Against Schedule PLAN ACTUAL Summarize original schedule of project Summarize what really happened in relationship to the plan List key milestones List differences in terms of original dates (x weeks late, x months early, etc.)

Performance Against Quality QUALITY GOAL ACTUAL State original quality goal or goals for the project Summarize what really happened in relationship to quality goals List key metrics (items for measuring success) List progress against metrics

Performance Against Budget ACTUAL COST/EXPENDITURES state original quality goal or goals for the project Summarize what really happened in relationship to budget List key cost goals, expenditure limits List progress against goals & limits

Post-Mortem By Department

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

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

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

Research & Development How Effective & Efficient Was R&D? IDENTIFYING & SOLVING TECHNICAL PROBLEMS ESTIMATES & EXECUTION Were estimates on track with actuals? What helped people estimate well? What caused people to estimate poorly? Were issues identified early enough? Were problems solved well? What worked? Didn’t work? Could be better?

Project Management How Was the Project Managed? MEETINGS COMMUNICATION Who/when/how often Who/when/how often How well did this work? How well did this work? CHANGES OTHER METHODS How tracked, communicated E-mail, schedules, databases, reports, etc. How well did this work?

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

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

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

Sales Was channel & sales force appropriately informed about product? Was timing appropriate? Cost? How do initial sales compare to goals? Did product and message meet customer need? 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” rather than “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 How did team respond to problems? Try to isolate specific attitudes, procedures, methods, timing issues, etc. which caused 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