This document provides a template for a project kick-off meeting presentation. It includes an introduction outlining the purpose and objectives, an agenda with sections on the project overview including description and goals, scope, team organization, major deliverables, estimated effort including budget, infrastructure, manpower allocation and timeline, assumptions risks and issues, project acceptance including customer acceptance conditions, and concludes with an end of presentation slide. The template provides placeholders for specific project details.

1. Project Kick-off Meeting guidelineThe following is a suggested format/template for preparing and presenting a project1/5/20111Prepared by: Sid CalayagDate: December 13, 2009

2. 1/5/2011Confidential2<Project Name> Kick-Off MeetingPrepared by: <Name> Date: <mm/dd/yyyy>

3. 1/5/2011Confidential3IntroductionPurpose of this presentationObjective: <Replace this text with a statement of this goal.>

4. 1/5/2011Confidential4AgendaProject OverviewScope and Team organizationMajor deliverablesEstimated EffortAssumptions, Risks and IssuesProject Acceptance

5. 1/5/2011Confidential5Project OverviewProject description<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.>

6. January 5, 2011Confidential6Scope<Replace this text with a list of scope. This section is where you clearly define the logical boundaries of your project.Explanation:Scope statements are used to define what is within the boundaries of the project and what is outside those boundaries.

7. January 5, 2011Confidential7Team Organization<Replace this text with a list of responsible team or organization. This section is where you clearly specify team members and their responsibilities (as well as expectations).

8. January 5, 2011Confidential8Major DeliverablesDeliverables<Deliverable 1: Description and importance to project.><Deliverable 2: Description and importance to project.><Deliverable 3: Description and importance to project.>Explanation of this section: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.

9. January 5, 2011Confidential9Estimated EffortBudgetInfrastructure neededInclude here office required, communication, warehouse, transportation and equipmentManpower allocation<List of subcon: Description and importance to project.><Timetable :Usually included in the project master schedule .>Timelinea 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.

10. 1/5/2011Confidential10Assumptions, Risks and IssuesProject AssumptionsUnverified information used in the design and estimateUnknown situations/installation requirement that are due to our own inability to visit/survey the site before the design and estimation processRisk and IssuesThese 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. Change Orders that are not yet considered in the plan and estimate (and budget as well).

11. 1/5/2011Confidential11Project AcceptanceCustomer AcceptanceConditions by costumers prior to acceptance.customer concerns,changes,requirement, testing and commissioningdocuments

12. 12Managers & Engineers should:Prepare Project Quality PlanPrepare work methodology and follow them accordinglyHave standard processes in place to deal with all contingencies.Conduct End Of Project assessmentReview Issues LogPromote continual improvement thru effective use of CAR & PAR

13. 1/5/2011Confidential13End of Presentation