The following is a suggested format/template for preparing and presenting a project

7/10/2011 1

Prepared by: Sid Calayag Date: December 13, 2009

7/10/2011 2

<Project Name> Kick-Off Meeting

Prepared by: <Name>

Date:

<mm/dd/yyyy>

7/10/2011 Confidential 3

Introduction

• Purpose of this presentation – Objective:

• <Replace this text with a statement of this goal.>

7/10/2011 Confidential 4

Agenda

• Project Overview • Scope and Team organization • Major deliverables • Estimated Effort • Assumptions, Risks and Issues • Project Acceptance

7/10/2011 Confidential 5

Project Overview

• Project 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.>

July 10, 2011 Confidential 6

Scope • <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.

July 10, 2011 Confidential 7

Team 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).

July 10, 2011 Confidential 8

Major Deliverables • Deliverables

– <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.

July 10, 2011 Confidential 9

Estimated Effort • Budget • Infrastructure needed

– Include here office required, communication, warehouse, transportation and equipment

• Manpower allocation – <List of subcon: Description and importance to

project.> – <Timetable :Usually included in the project master

schedule .>

• Timeline – 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.

7/10/2011 Confidential 10

Assumptions, Risks and Issues • Project Assumptions

– Unverified information used in the design and estimate

– Unknown situations/installation requirement that are due to our own inability to visit/survey the site before the design and estimation process

• Risk and Issues – 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.

– Change Orders that are not yet considered in the plan and estimate (and budget as well).

7/10/2011 Confidential 11

Project Acceptance

• Customer Acceptance – Conditions by costumers prior to

acceptance. • customer concerns,

• changes,

• requirement,

• testing and commissioning

• documents

12

Managers & Engineers should:

Prepare Project Quality Plan Prepare work methodology and follow them accordingly Have standard processes in place to deal with all contingencies. Conduct End Of Project assessment Review Issues Log Promote continual improvement thru effective use of CAR & PAR

7/10/2011 Confidential 13