Kick Off Meeting Presentation

39,904 views
39,351 views

Published on

0 Comments
41 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
39,904
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
41
Embeds 0
No embeds

No notes for slide
  • The estimated effort hours and project costs may be depicted in many ways, including costs by team member, cost by deliverable, cost by milestone, or cost by category (internal labor, external labor, travel, training, supplies, etc.). Also include 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.
  • Project RisksProject risks 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. (In other words, whereas an issue is a current problem that must be dealt with, a risk is a potential future problem that has not yet occurred.) All projects contain some risks. Risks may not be able to be eliminated entirely, but can be anticipated and managed, thereby reducing the probability that they will occur.Risks that have a high probability of occurring and have a high negative impact should be listed below. Also consider those risks that have a medium probability of occurring. For each risk listed, identify activities to perform to eliminate or mitigate the risk.
  • 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 />

    ×