Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

[Product Name] Marketing Plan
By Guy Yariv Project Closure – Finally…
OPSM 639, C. Akkan Monitoring Progress How does a project get one year late? … One day at a time –Frederick P. Brooks MBWA: Management by Walking Around.
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Project Control Techniques
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
W5HH Principle As applied to Software Projects
Project Overview Project Name Company Name Presenter Name.
Chapter 3: The Project Management Process Groups
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Name Steering Committee Meeting Project Manager: Project Manager Name Program Manager: Program Manager Name Project Sponsor: Project Sponsor Name.
Advertising in Arab countries The Coca Cola Poster.
Project Lifecycle Section 6 - Closeout. Project Manager’s Role During Project Close-Out  Ensure that all project deliverables have been completed and.
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
© VESP International Pty Limited To Contents Slide CLICK to advance slides/ bullet points within slides Integrated Master Planner An Overview.
1 Project Failure Factors Well known Yet ignored..
Enterprise Product Implementation Process. Components of a Successful Implementation  A detailed Scope Document for customer review and signoff  Creation.
Chapter 4 The Project. 2 Learning Objectives Third phase starts after a contract is drawn up and ends when the project objective is accomplished; final.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Prof. Roy Levow Session 9.  Defining the APF  An Overview of the APF  The APF Core Values.
Prof. Roy Levow Session 8.  Steps in Closing a Project  Getting Client Acceptance  Installing Project Deliverables  Documenting the Project  Post-Implementation.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Marketing planning Key Terms Product Life Cycle Marketing Budget Test marketing Sales forecasting.
Basic of Project and Project Management Presentation.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Project Status Report Presenter Name Presentation Date.
Executive Session Director’s CD-3b Review of the MicroBooNE Project January 18, 2012 Dean Hoffer.
Project monitoring and Control
Managing Projects and People Summary Define the scope Plan the goals, milestones and deliverables Determine each person’s realm Assign work Monitor.
Project Life Cycle.
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.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project Overview From an AutoContent Wizard University of California Berkeley Extension Copyright © 2008 Patrick McDermott.
Introducing Project Management Update December 2011.
Chapter Fourteen Communicating the Research Results and Managing Marketing Research Chapter Fourteen.
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
Sage ERP X3 Standard Edition Methodology
Operational and Postimplementation
Project Management Update TAC Team Meeting
Project Status [Project Name] [Presenter Name] This presentation will probably involve audience discussion, which will create action items. Use PowerPoint.
Ch7: Project Monitoring and Control  To reduce differences between plan and actual in the 3D space of T/C/P.  Best utilization of organization’s primary.
Complete Design & Gate Review. Complete Design Detailed Design Review (DDR) 1.“High and medium technical risk” areas –Design Review (Prelim-DDR): standard.
PMI Evening Event - Preston / Dec 2007 Spotting & catching problem projects before it's too late Neil Johnson Project & Programme Management Capability.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Project Management PTM721S
Reactive Attachment Disorder
4.4 Monitor and Control Project Work
[Project Name] [Presenter Name]
[Project Name] Post-Mortem
PROJECT NAME POST-MORTEM
Reporting Progress or Status
[Project Name] [Presenter Name]
Downloaded from بسم الله الر حمن الر حيم Sayed Jalil 11/23/2018 Downloaded from
[Project Name] [Presenter Name]
[Project Name] [Presenter Name]
Project Execution Activities
[Project Name] Post-Mortem Presentation Template
Project Name Post-Mortem
Reporting Progress or Status
Presenting Project Status
[Project name] [Presenter name]
Presentation transcript:

Project Post-Mortem University of California Berkeley Extension Copyright © 2008 Patrick McDermott From an AutoContent Wizard 10/27/2007.

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

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 –How well did this work? Changes: how tracked, communicated –How well did this work? Other methods: , 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