Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kick Off Meeting Presentation

71,012 views

Published on

Kick Off Meeting Presentation

  1. 1. Project Kick-off Meeting guideline<br />The following is a suggested format/template for preparing and presenting a project<br />1/5/2011<br />1<br />Prepared by: Sid Calayag<br />Date: December 13, 2009<br />
  2. 2. 1/5/2011<br />Confidential<br />2<br /><Project Name> Kick-Off Meeting<br />Prepared by: <Name><br /> Date: <mm/dd/yyyy><br />
  3. 3. 1/5/2011<br />Confidential<br />3<br />Introduction<br />Purpose of this presentation<br />Objective: <br /><Replace this text with a statement of this goal.><br />
  4. 4. 1/5/2011<br />Confidential<br />4<br />Agenda<br />Project Overview<br />Scope and Team organization<br />Major deliverables<br />Estimated Effort<br />Assumptions, Risks and Issues<br />Project Acceptance<br />
  5. 5. 1/5/2011<br />Confidential<br />5<br />Project Overview<br />Project description<br /><Replace this text with a short description of the project, organizations affected or impacted (e.g. customer and their product, supplier and sub-cons, government agencies where compliance to regulations are required, etc.), contract amount, timeline and goals.><br />
  6. 6. January 5, 2011<br />Confidential<br />6<br />Scope<br /><Replace this text with a list of scope. <br />This section is where you clearly define the logical boundaries of your project.<br />Explanation:<br />Scope statements are used to define what is within the boundaries of the project and what is outside those boundaries. <br />
  7. 7. January 5, 2011<br />Confidential<br />7<br />Team Organization<br /><Replace this text with a list of responsible team or organization. <br />This section is where you clearly specify team members and their responsibilities (as well as expectations).<br />
  8. 8. January 5, 2011<br />Confidential<br />8<br />Major Deliverables<br />Deliverables<br /><Deliverable 1: Description and importance to project.><br /><Deliverable 2: Description and importance to project.><br /><Deliverable 3: Description and importance to project.><br />Explanation of this section:<br />All projects have deliverables. In this section, describe the deliverables of the project. Provide enough explanation and detail that all members will be able to understand what is being produced. <br />
  9. 9. January 5, 2011<br />Confidential<br />9<br />Estimated Effort<br />Budget<br />Infrastructure needed<br />Include here office required, communication, warehouse, transportation and equipment<br />Manpower allocation<br /><List of subcon: Description and importance to project.><br /><Timetable :Usually included in the project master schedule .><br />Timeline<br />a chart showing the project start date, major milestones, and end date. The deliverables included in this milestone chart should all have been described in the scope section.<br />
  10. 10. 1/5/2011<br />Confidential<br />10<br />Assumptions, Risks and Issues<br />Project Assumptions<br />Unverified information used in the design and estimate<br />Unknown situations/installation requirement that are due to our own inability to visit/survey the site before the design and estimation process<br />Risk and Issues<br />These are circumstances or events that exist outside of the control of the project team that will have an adverse impact on the project if they occur. <br />Change Orders that are not yet considered in the plan and estimate (and budget as well).<br />
  11. 11. 1/5/2011<br />Confidential<br />11<br />Project Acceptance<br />Customer Acceptance<br />Conditions by costumers prior to acceptance.<br />customer concerns,<br />changes,<br />requirement, <br />testing and commissioning<br />documents<br />
  12. 12. 12<br />Managers & Engineers should:<br />Prepare Project Quality Plan<br />Prepare work methodology and follow them accordingly<br />Have standard processes in place to deal with all contingencies.<br />Conduct End Of Project assessment<br />Review Issues Log<br />Promote continual improvement thru effective use of CAR & PAR<br />
  13. 13. 1/5/2011<br />Confidential<br />13<br />End of Presentation<br />

×