Kick-Off Meeting Presentation
-
Upload
sidcalayag -
Category
Documents
-
view
2.654 -
download
4
description
Transcript of Kick-Off Meeting Presentation
![Page 1: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/1.jpg)
The following is a suggested format/template for
preparing and presenting a project
12/13/2009 1
Prepared by: Sid Calayag
Date: December 13, 2009
![Page 2: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/2.jpg)
12/13/2009 2
<Project Name>
Kick-Off Meeting
Prepared by: <Name>
Date: <mm/dd/yyyy>
![Page 3: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/3.jpg)
12/13/2009 Confidential 3
Introduction
• Purpose of this presentation
– Objective: • <Replace this text with a statement of this goal.>
![Page 4: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/4.jpg)
12/13/2009 Confidential 4
Agenda
• Project Overview
• Scope and Team organization
• Major deliverables
• Estimated Effort
• Assumptions, Risks and Issues
• Project Acceptance
![Page 5: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/5.jpg)
12/13/2009 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.>
![Page 6: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/6.jpg)
December 13, 2009 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.
![Page 7: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/7.jpg)
December 13, 2009 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).
![Page 8: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/8.jpg)
December 13, 2009 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.
![Page 9: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/9.jpg)
December 13, 2009 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.
![Page 10: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/10.jpg)
12/13/2009 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).
![Page 11: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/11.jpg)
12/13/2009 Confidential 11
Project Acceptance
• Customer Acceptance
– Conditions by costumers prior to acceptance.
• customer concerns,
• changes,
• requirement,
• testing and commissioning
• documents
![Page 12: Kick-Off Meeting Presentation](https://reader034.fdocuments.us/reader034/viewer/2022050808/546abbc6af795971298b4886/html5/thumbnails/12.jpg)
12/13/2009 Confidential 12