project management organization scheduling 31 january

28
Project Management Organization Scheduling 31 January

Upload: alexandra-edwards

Post on 18-Jan-2016

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Project Management Organization Scheduling 31 January

Project Management

OrganizationScheduling31 January

Page 2: Project Management Organization Scheduling 31 January

ORGANIZATIONProject management

Page 3: Project Management Organization Scheduling 31 January

Organization Needed to control communications cost

Channel of communications costs about 2 hours per week

Optimal number 3-7 Organization structures

Hierarchical Peer

Requires leader of team or aspects Subteam

Requires gatekeeper Matrix

Page 4: Project Management Organization Scheduling 31 January

What can you tell from an organization?

The formal structure NOT the informal working mode

Page 5: Project Management Organization Scheduling 31 January

SCHEDULINGProject management

Page 6: Project Management Organization Scheduling 31 January

How to Build a Schedule

Identify the component parts Identify the dependencies Estimate

Really just another word for guess Prefer educated guess

Lay out assignments and time frames

Page 7: Project Management Organization Scheduling 31 January

Project Plan for this project Use simple Excel spreadsheet (or equivalent)

Deliverable/Milestone Responsible Due Revision 1 Delivered

project web site Sam 20-Jan 20-Janarchitecture Jane (all) 8-Feb 15-Feb 23-Febproject plan Harry 10-Feb 15-Feb 16-Febinitial user interface Sam 13-Feb 15-Feb 18-Febcontract Jane 20-Feb 15-Feb 18-Feb

Page 8: Project Management Organization Scheduling 31 January

What you should be able to tell from your project plan

What is Joe working on this week? Who can help me if I run into

trouble? If I have to choose an activity to be

late, which one will impact the project more?

Page 9: Project Management Organization Scheduling 31 January

Tools to Help

Product description Clear statement of what you are building

Work breakdown Product flow PERT charts

Program Evaluation and Review Technique

Gantt charts

Page 10: Project Management Organization Scheduling 31 January

Work Breakdown Structure

Need to break down the tasks into component parts and tasks

Level of detail important Lacks any time component

Page 11: Project Management Organization Scheduling 31 January

Work Breakdown

Page 12: Project Management Organization Scheduling 31 January

Graphical WBS

Page 13: Project Management Organization Scheduling 31 January

Product Flow

Identify sequences and dependencies

Distinguish new from existing components

Page 14: Project Management Organization Scheduling 31 January

Product Flow

Page 15: Project Management Organization Scheduling 31 January

PERT Charts Critical path analysis or method

Program Evaluation and Review Technique Also known as activity networks

Developed by Navy in 1958 Three stages:

Planning (tasks and sequence) Scheduling (start and finish times) Analysis (float and revisions)

Two different models Activities are nodes (most common) or arcs

Page 16: Project Management Organization Scheduling 31 January

Pert Chart Activity Box

Page 17: Project Management Organization Scheduling 31 January

Pert Charts

Page 18: Project Management Organization Scheduling 31 January

CPM: Critical Path Method

Alternative to PERT Dupont 1957 Graphical view of project Predicts time required to complete Shows which activities are critical

to maintaining the schedule

Page 19: Project Management Organization Scheduling 31 January

Planning: PERT and CPM1. Identify the specific

activities and milestones. 2. Determine the proper

sequence of the activities.

3. Construct a network diagram.

4. Estimate the time required for each activity.

5. Determine the critical path.

6. Update the PERT chart as the project progresses.

1. Specify the individual activities.

2. Determine the sequence of those activities.

3. Draw a network diagram. 4. Estimate the completion

time for each activity. 5. Identify the critical path

(longest path through the network)

6. Update the CPM diagram as the project progresses.

Page 20: Project Management Organization Scheduling 31 January

Gantt Charts

Milestone charts Invented by Harvey Gantt in 1916 Advantages

Less detailed Amenable to management overlays

Page 21: Project Management Organization Scheduling 31 January

Gantt Chart

Page 22: Project Management Organization Scheduling 31 January

Gantt Chart with Overlays

Page 23: Project Management Organization Scheduling 31 January

Scheduling Steps and Tools Put together minimal solution

Primary requirements Start with external commitments

Product descriptions Milestones (contract)

Introduce internal milestones Work breakdown structure Product Flow PERT Chart, Gantt chart

Focus on the risks Risks (contract)

Add next level of features where possible Secondary requirements

Page 24: Project Management Organization Scheduling 31 January

Software Sources Open source tools:

dmoz.org/Computers/Software/Project_Management/Open_Source/

Page 25: Project Management Organization Scheduling 31 January

Reviews and Inspections

Page 26: Project Management Organization Scheduling 31 January

Reviews and Inspections Why?

Developer can’t correct unseen errors More eyes to catch problems Earlier is cheaper

Integration fix typically 3-10 times the cost at design

Difference in terms Review implies completed work, often

reviewed by someone at a different level Inspection implies peer review of work in

progress

Page 27: Project Management Organization Scheduling 31 January

Inspections

Introduced by Michael Fagin in 76 (IBM Systems Journal)

Formalized process Specific roles and steps Heavy preparation and follow-up

Used for documents and code

Page 28: Project Management Organization Scheduling 31 January

Will you review or inspect?What will you review or inspect?How will you review or inspect?