The following is a suggested format/template for

preparing and presenting a project

Prepared by: Sid Calayag

Date: December 13, 2009

12/13/2009 1
 <Project Name>
Kick-Off Meeting

Prepared by: <Name>

Date: <mm/dd/yyyy>
12/13/2009 2
 Introduction
• Purpose of this presentation
– Objective:
• <Replace this text with a statement of this goal.>

12/13/2009 Confidential 3
 Agenda
• Project Overview
• Scope and Team organization
• Major deliverables
• Estimated Effort
• Assumptions, Risks and Issues
• Project Acceptance

12/13/2009 Confidential 4
 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.>

12/13/2009 Confidential 5
 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.

December 13, 2009 Confidential 6

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

December 13, 2009 Confidential 7

 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.
December 13, 2009 Confidential 8
 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.
December 13, 2009 Confidential 9
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).

12/13/2009 Confidential 10
 Project Acceptance
• Customer Acceptance
– Conditions by costumers prior to
acceptance.
• customer concerns,
• changes,
• requirement,
• testing and commissioning
• documents

12/13/2009 Confidential 11
12/13/2009 Confidential 12