New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

40
New Tools in an Old Company PMI Honolulu Chapter Meeting PMI Honolulu Chapter Meeting June 20, 2007 June 20, 2007

Transcript of New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Page 1: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

New Tools in an Old CompanyPMI Honolulu Chapter MeetingPMI Honolulu Chapter Meeting

June 20, 2007June 20, 2007

Page 2: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Pre-set Meeting Agendas Sets direction for meetingSets direction for meeting ““Manage” meeting participantsManage” meeting participants Assists new PMs (or employees)Assists new PMs (or employees)

Page 3: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Project Initiation Meeting Agenda

Page 4: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Project Initiation Meeting Agenda

Page 5: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Project Initiation Meeting Agenda

Page 6: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Project Initiation Meeting Agenda

Page 7: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Project Initiation Meeting Agenda

Page 8: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 9: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 10: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 11: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 12: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 13: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 14: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Statement Template

Page 15: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Other Meeting Agenda Templates Project Plan MeetingProject Plan Meeting Organizational Planning MeetingOrganizational Planning Meeting Preliminary Engineering MeetingPreliminary Engineering Meeting PUC Application Development MeetingPUC Application Development Meeting Engineering Design MeetingEngineering Design Meeting Construction Planning MeetingConstruction Planning Meeting Construction Review MeetingConstruction Review Meeting

Page 16: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Risk Assessment Checklist OperationsOperations CustomerCustomer Land Use/PermittingLand Use/Permitting RegulatoryRegulatory Community RelationsCommunity Relations Construction ImpactsConstruction Impacts Long-Term ImpactsLong-Term Impacts ScheduleSchedule Cost EstimateCost Estimate

PROJECT NAME:

Place an "X" as

applicable Add further comments as

warranted.RELIABILITY - SAIF FACTORS

Numerous outages have occurred over the past year, which the proposed project will address.

Numerous outages have occurred over the past 5 years, which the proposed project will address.

Recurring outages could occur if the project is not implemented.

A single outage could occur if the project is not implemented.

A single outage could occur if the project is not implemented AND another contingency occurs on the system. (Distribution Planning Criteria)A single outage could occur if the project is not implemented AND two or more contingencies occur on the system. (Transmission Planning Criteria)

This project would have no impact on SAIF.

RELIABILITY - CAID FACTORS

If an outage were to occur, then the outage duration would be longer than previous experiences (if project not implemented).

If an outage were to occur, then the outage duration would increase over time than previous experiences (if project not implemented).

This project would maintain the same outage duration as currently exists.

This project would reduce an outage duration from current experiences (i.e. improve CAID).

This project would have no impact on CAID.

NEW PROJECT RISK ASSESSMENTENERGY DELIVERY

Page 17: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

WBS Chart Pro™

Page 18: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

WBS Chart Pro™

Page 19: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Change Request Form

Page 20: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Change Request Form – Part 1

Page 21: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Change Request Form – Part 2

Page 22: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Change Request Form – Part 3

Page 23: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Change Request Form – Part 4

Page 24: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Scope Change Request Form – Part 5

Page 25: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Process Guidelines

Page 26: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Guideline #1

Lessons Learned meeting(s) should be Lessons Learned meeting(s) should be held within 6 weeks after a project or held within 6 weeks after a project or a major phase of a project is a major phase of a project is completed. completed.

Page 27: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Guideline #2

At least a week prior to the meeting(s), At least a week prior to the meeting(s), the Project Manager should prepare the Project Manager should prepare an agenda (or use the attached an agenda (or use the attached ‘Lessons Learned Matrix’) and ‘Lessons Learned Matrix’) and distribute to all stakeholders. distribute to all stakeholders.

Page 28: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Guideline #4

For a large or complex project it is For a large or complex project it is recommended that separate lessons recommended that separate lessons learned meetings be conducted for the learned meetings be conducted for the different areas or phases of the different areas or phases of the project. project.

Page 29: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 30: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 31: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 32: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 33: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 34: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 35: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 36: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 37: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Lessons Learned Matrix Template

Page 38: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

PM Checklist

Project Phase Deliverable Description Due Date Date Received CommentsProject Plan Phase PM Assignment LetterProject Team Org Chart

Research - Similar Projects/Lessons LearnedProject Initiation Meeting MinutesScope StatementWBSRisk Management AnalysisResource AssessmentProject SchedulePillar filesProject Plan Meeting MinutesPIF - Initiated (includes schedule, pillar file, WBS)

Preliminary Engineering PhaseOrganizational Planning Meeting Minutes-Responsibility MatrixPIF-Authorization for Engineering (includes schedule, pillar file, WBS)Preliminary Engineering Meeting MinutesChange Control Form (if required)Reauthorization (if required)

Project Management Check List

Page 39: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

PM ChecklistProject Phase Deliverable Description Due Date Date Received Comments

Final Engineering Design PhasePUC Application Development Meeting MinutesPUC Application Filed (includes schedule, pillar file, WBS)PUC Approval - D&OPIF-Material & Construction Authorization (includes schedule, pillar file, WBS)Engineering Design Meeting MinutesChange Control Form (if required)Reauthorization (if required)

Construction PhaseConstruction Planning Meeting MinutesConstruction Review Meeting MinutesChange Control Form (if required)Reauthorization (if required)

In Service Phase

Partial close project-notify Plant AccountingPUC Interim Accounting ReportLessons Learned Meeting MinutesFinal close contractsFinal close project - close out Ellipse subproject and workordersPUC Final Cost report

Page 40: New Tools in an Old Company PMI Honolulu Chapter Meeting June 20, 2007.

Conclusion

Work within FrameworkWork within Framework Keep efforts Low-KeyKeep efforts Low-Key Create In-house TrainingCreate In-house Training

Leverage Your PMI Membership!