mgmt 483 week 5. we now move into consideration of the details of the project – planning what...

15
MGMT 483 Week 5

Upload: barbara-kinn

Post on 31-Mar-2015

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

MGMT 483 Week 5

Page 2: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when

We look at:

The project action plan – hierarchical planning

The Work Breakdown Structure The Linear Responsibility Chart

Then you will practice these techniques with an in-class planning exercise

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 3: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Overview Objectives or scope General approach Contractual aspects Schedules Resources Personnel Risk management plans Evaluation methods

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 4: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Action plan: the set of project activities, their schedules, and the resources needed to complete the project

What is to be doneWhen it is to be started and finishedWho is going to do it

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 5: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Activities on a project face unique complexities Task dependencies

▪ Some activities cannot start until others are finished▪ Some activities must be done at-the-same-time

Some activities are very time critical Others have a great deal of flexibility

This requires a great deal of planning

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 6: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Hierarchical planning: a planning approach that breaks the planning task down into the activities that must be done at each level. Typically, the upper level sets the objectives for the next lower level

Major tasks are listed Each major task is then broken down

into more detail This continues until all the activities to

be completed are listed Need to know which activities “depend

on” other activitiesMeredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 7: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

From: http://office.microsoft.com/en-us/project Copyright Microsoft Corporation 2009

Finish-to-start (FS) Task (B) cannot start until task (A) finishes. For example, if you have two tasks, "Construct fence" and "Paint fence," "Paint fence" can't start until "Construct fence" finishes. This is the most common type of dependency.

Start-to-start (SS) Task (B) cannot start until task (A) starts. For example, if you have two tasks, "Pour foundation" and "Level concrete," "Level concrete" can't begin until "Pour foundation" begins.

Finish-to-finish (FF) Task (B) cannot finish until task (A) finishes. For example, if you have two tasks, "Add wiring" and "Inspect electrical," "Inspect electrical" can't finish until "Add wiring" finishes.

Start-to-finish (SF)Task (B) cannot finish until task (A) starts. Used to control scheduling – not used very often in practice

Page 8: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Figure 6-2Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 9: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Figure 6-3Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 10: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

The WBS is a tool for activity planning using the hierarchical method – it is usually a more detailed form of the action plan

Steps to create a WBS:1. Create a list of the major activities for the project2. Decompose (break down) each major activity into more detailed

tasks for the next level in the hierarchy. ▪ The tasks identified for each level must be at approximately the same

level of detail. It’s easy to come up with detail for activities we are familiar with and gloss over those that are unfamiliar. This process forces comparable detail for all the levels.

▪ Break the tasks down into sufficient detail so they can be individually planned, budgeted, scheduled monitored and controlled. The tasks at the bottom of the structure are typically called work packages.

3. When the activities are sufficiently decomposed, then individual tasks are scheduled and assigned to personnel (a Linear Responsibility Chart is often created to help understand task assignments and responsibilities)

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 11: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Can be columnar, with sub-tasks indented under the main task elements - like the earlier example of the action plan, or visual

Either is correct – or you can create both, depending on the purpose

In MS Project you enter the WBS in a spreadsheet-like format, which is visually displayed as a Gantt chart

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 12: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Figure 6-6Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 13: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Once tasks are broken down into work packages on the WBS, we need to assign resources

▪ The assignment of people to work packages can be displayed on an LRC, which can also identify requirements for support, approval and notification.

▪ With this, the PM can keep track of who must approve what and who must report to whom

▪ The work packages must be reviewed with the people involved to ensure their accuracy and adequacy in describing the tasks to be accomplished.

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 14: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Figure 6-7Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.

Page 15: MGMT 483 Week 5. We now move into consideration of the details of the project – planning what exactly is going to be done, by whom, and when We look at:

Meredith & Mantel (2009) Project management: a managerial approach. 7th ed. Wiley.Simplified Linear Responsibility Chart (Fig 6-8)