Project Management Integration

Size: px
Start display at page:

Download "Project Management Integration"

Transcription

1 Project Management Integration

2 Integration Management the processes required in ensuring that the various elements of a project are properly coordinated balancing, making trade-offs plan, execute and control 2

3 What needs to be integrated? Knowledge areas Activities of the project and the activities of the organisation Project and product scope Outputs from different functional areas of a project 3

4 Project Priority Matrix 4

5 Integration Processes Project plan development integrating the planning outputs of a project into a single document Project plan execution executing the project plan managing the overall project effectively Overall change control setting up procedures managing changes 5

6 Integration Steps Defining the project at the start Project kick-off meeting Project Definition Report (PDR) Project Plan Implementation & Change control Concluding a project and close-out 6

7 Project Definition Define scope, project organisation and constraints Deliverables required at each stage Gain acceptance of plans Mode of operation and communication channels Build and focus the project team 7

8 Kick-off meeting Gain commitment and build team spirit Ratify earlier project definition Plan the current stage Prepare preliminary plans for execution Prepare preliminary estimates Assess risk and develop risk reduction strategies Agree when to review the deliverables at each stage 8

9 Who will attend? Project sponsor or champion Manager(s) of current/future stages of the project Key functional managers who will provide resources Project support personnel Who will you invite? 9

10 PDR Provide sufficient definition for commitment Provide the basis for the next stage of the project Provide stakeholders with an overview of project priorities Communicate project s requirements 10

11 Contents of PDR Preface Executive summary Background Purpose, scope objectives WBS Project organisation PM system Risks and assumptions Budgets Justification 11

12 Project Plan Project description and objectives Master project plan Management plan Performance specifications Functional specifications Acceptance tests and criteria Project constraints Risks and assumptions 12

13 Revisit Scope Conceptual development Scope statement Work authorisation Scope reporting Control systems Project close-out 13

14 Implementation Planning Planning and scheduling activities Define activities required for each milestone Ratify the people involved Define roles and responsibilities Estimate work content and duration Schedule activities within the work package 14

15 How do we control? Set up a baseline plan Measure progress and performance Compare plan against actual on a regular basis Take action (when required) Continue to monitor to ensure that actions taken are effective 15

16 Baseline Gantt Chart

17 13-2 Control Chart 17

18 13-4 Work-Cost-Time Relationships 18

19 13-7 The S Curve 19

20 Change Evaluation Review all requested changes Identify all task impacts Translate this into performance, cost, schedule Evaluate cost/benefit Identify alternative ways to resolve Accept or reject the change 20

21 13-17 Changing the baseline When do you think it Justified to change baseline? 21

22 Change Implementation Once change is accepted Communicate the change to all parties Ensure that changes are implemented properly Summarise all changes to date and impact in monthly reports How will you incorporate a change order system in your project? Change Request Form creates a Change/Variation Log 22

23 Project Close-Out Plan for transition by setting up a hand over procedure Ensure that users accept the product/service Provide training to users to operate facility or use product or service Update any documentation Ensure provision of adequate post- project service 23

24 Group Project How will we kick off the project? Who will be invited to the kick-off meeting? Why? How will the work be coordinated during project implementation? How will we effectively control the project? How will the project be handed over and closed out? 24