Project Management Lecture Resource Analysis. Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network.

Slides:



Advertisements
Similar presentations
Lecture Network Analysis
Advertisements

CP Chapter 4 Schedule Planning.
Project Management Information Systems and Management.
Project Management Information Systems and Management.
Network Analysis and Duration Estimating Kathy S. Schwaig.
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
Critical Path and Gantt
5.8 Project Management Chapter 37 HL - Only.
Chapters 8, 9, and 10 Design Stage 1 Preconstruction Stage 2: Procurement Conceptual Planning Stage3: Construction Stage 4: Project Close-out.
Project Management Lecture Developing the Project Plan.
Importance of Project Schedules
SWE Introduction to Software Engineering
COMP2001 HNC Project. Project Characteristics A project must have: clear objectives planning & control resources assurance of quality.
Lecture Network Analysis
CS 501: Software Engineering Fall 2000 Lecture 4 Management I: Project Management.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Chapter 3 Managing the Information Systems Project
Project Time Management
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Project Management Software Tools Cheryl A. Wilhelmsen Lee Ostrom.
PLANNING ENGINEERING AND PROJECT MANAGEMENT By Lec. Junaid Arshad 1 Lecture#10 DEPARTMENT OF ENGINEERING MANAGEMENT.
Dr. Godfried Williams1 Project Management – Topic 6 Lecture Content Planning Tools/Techniques Optimization Techniques Resource Planning & Allocation Linear.
Allocating Resources to the Project
Lecture 5 – Gantt Chart GANTT Charts Constructing GANTT Charts
1 Project Control Kathy S. Schwaig. 2 What is Project Control? Project control is the continuous monitoring of the project for deviations from plan (time,
Resource Management. Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall12-2 Types of Constraints  Time  Resource  Mixed Copyright.
Project Management Project Planning Estimating Scheduling.
COMP 208/214/215/216 Lecture 3 Planning. Planning is the key to a successful project It is doubly important when multiple people are involved Plans are.
Quick Recap.
Software Project Management
Software Engineering Lecture 7: Scheduling & Tracking.
© The McGraw-Hill Companies, Software Project Management 4th Edition Resource allocation Chapter 8.
Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.
1 Project Management Software Engineering
© Pearson Education Limited 2004 OHT 8.1 Cadle and Yeates: Project Management for Information Systems, 4th edition Critical Path Method(CPM)
Objectives 4 Understand the basic concepts of project planning and control 4 Explain PERT and Timeline (Gantt) charts.
Managing Resources Program Evaluation and Review Technique (PERT) Production Process.
CS 501: Software Engineering Fall 1999 Lecture 6 Management I: Project Management.
Resource analysis Project management (lecture + seminar)
Project Schedules Chapter 4 Applied Software Project Management, Stellman & Greene See also:
Chapter 6: Project Time Management Information Technology Project Management, Fourth Edition Using Critical Chain Scheduling, PERT, and MS Project 2003.
MEM 612 Project Management Chapter 6 Allocating Resources to the Project.
Lecture 61 Project planning tool Lecture 62 Objectives Understand the reasons why projects sometimes fail Describe the different scheduling tools, including.
Chapter 7 – PERT, CPM and Critical Chain Operations Management by R. Dan Reid & Nada R. Sanders 4th Edition © Wiley 2010.
Project Time Management Ashima Wadhwa. Schedule Development – Determining start and finish dates for project activities – Without realistic dates, project.
CPM – Critical Path Method Can normal task times be reduced? Is there an increase in direct costs? Additional manpower Additional machines Overtime, etc…
Project Time Management
1 Allocating Resources to the Project Expediting a Project Fast-Tracking a Project Resource Loading Allocating Scare Resources.
Microsoft Project 2010 ® Tutorial 4: Assigning Resources and Costs.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Resource analysis 1 Project management (seminar).
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Chapter 5: Software effort estimation
The Network Diagram. When to Do What?  Carrying out one activity after the other may result in project completion, but it will take the longest possible.
HNDIT23082 Lecture 10:Software Project Management
Critical Path Analysis (CPA)
Critical Path Method(CPM)
Software Project Management
ACTIVITY PLANNING AND RISK MANAGEMENT
Project planning Unit 3 Employability and Professional Development
Critical Path Analysis (CPA)
COMP 208/214/215/216 Lecture 3 Planning.
Chapter 5: Software effort estimation
Software Project Management Fifth Edition
Project management Lecture 9
Project management (seminar)
Exercise – A small building.
University of Debrecen Mongolian University of Life Sciences
IEEE Aerospace Conference 2019 Rob Richards, Ph.D.
Pacific International Maritime Conference 2019
Presentation transcript:

Project Management Lecture Resource Analysis

Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network analysis II Project planning Network analysis II Plan Project planning Resource analysis Risk management Quality Budgets and cost control Project teams Project planning Resource analysis Risk management Quality Budgets and cost control Project teams

Why Network Diagrams? Splits up the decision making process into Method/logic - the order in which tasks have to be completed Time – estimates for the time to completion can be added to each task Resources – these can be added and then analysis carried out

Resources Resources may be: Storable Remains available if not used and is only depleted by usage Examples? Non-Storable Availability has to be renewed for each time period Examples?

Loading The assignment of work to an operator, machine or department When too much work is required of a resource it is overloaded If too little work is assigned to a resource it is underloaded What are the implications if a resource is underloaded?

Limits Time limited projects – Projects where time is the overriding factor They must be completed by a certain date Resource limited projects – Limited resources are available to complete the project Think about the relationship between time and resources in a project?

Units of resource It is desirable when possible to state the work required in units of time. (i.e. person/machine hours) Example To dig a hole 4m x 4m x 6m = 96m 3 will take one person 12 hours. So 96m 3 = 12 person hours of digging Or 1 person hour of digging = 8m 3 How long would it take 12 persons to dig the hole?

Units of resource Most tasks will NOT have a linear relationship between the units of resource employed and the activity duration IS Team working factors? Communication overhead? Increased likelihood of sickness?

Linear vs. non-linear relationship

Exercise 1 – Resource Analysis

Exercise 1 Draw a Gantt chart using earliest Start/Finish Times

Resource analysis Earliest Start Time

Resource analysis Earliest Start Time Now add the resource usage histogram

Resource analysis Earliest Start Time

Exercise 1 Draw a Gantt chart using latest Start/Finish Times

Resource analysis Latest Start Time Now add the resource usage histogram

Resource analysis Latest Start Time

Resource analysis Latest Start Time Earliest Start Time

Different types of resource It is likely that more than on type of resource is being consumed by a project For three types of resource we need three histograms (See example in Lockyer and Gordon)

Resource Analysis The same approach can be used to calculate the: Cumulative Resource Requirements Average Resource Requirements (using earliest start and latest start) See (Lockyer and Gordon, 1996)

Levelling Resources Resources can be levelled by: Moving activities with float Splitting up activities Only really effective for those with float Mooving activities with no float Trade-off between extending project duration and reducing resource costs Sometimes there is no choice

Levelling Resources After resource levelling the Activity Network must be reviewed Some tasks will now have no usable float (due to resource constraints) This can be indicated by using “dummy” activities such as “Waiting for programmer availability” It is likely that more than on type of resource is being consumed by a task

Project Effort Estimation Need to know: Usual efficiency of working Sickness/absenteeism rate Other existing commitments (e.g. other projects) Additional tasks (e.g. routine maintenance) Holidays Constraints on Facilities (e.g. availability of labs) Cost of and availability of overtime etc.

Software Effort Estimation Needs Historical Data KLOC is not a good measure on its own Complexity of the software can effect time taken for development E.g. more efficient algorithms will take longer to design

Laws of Estimation Parkinson’s Law “Work expands to fill the time available” Brookes’ Law “putting more people on a late job makes it later”

Why Network Diagrams? Splits up the decision making process into Method/logic - the order in which tasks have to be completed Time – estimates for the time to completion can be added to each task Resources – these can be added and then analysis carried out

Introduction Project planning Gantt chart and WBS Project planning Network analysis I Project planning Network analysis II Plan Project planning Resource analysis Budgets and cost control Quality Risk management Project teams