PROJECT TIME MANAGEMENT. IMPORTANCE Average time overrun on unsuccessful IT projects was 222 % of the original estimation. 1995 CHAOS Report It was reduced.

Slides:



Advertisements
Similar presentations
CP Chapter 4 Schedule Planning.
Advertisements

Advanced Project Management - CPH
Chapter 10: Project Schedule Planning
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
Eleanor Roosevelt High School
Management & Development of Complex Projects Course Code - 706
Project Time Management
Copyright 2008 Introduction to Project Management, Second Edition 1  Project time management involves the processes required to ensure timely completion.
Chapter 5: Project Time Management
Project Management. What is a Project? One Time Effort Identifiable Start/End Points Specific Objectives Multiple Tasks Resources from Across the Organization.
Project Time Management
Importance of Project Schedules
Chapter 6: Project Time Management
1 Project Time Management. 2 Learning Objectives Understand the importance of project schedules and good project time management Define activities as.
Chapter 6: Project Time Management
Project Time Management
Chapter 6: Project Time Management
Software Project Management
Project Time Management J. S. Chou, P.E., Ph.D.. 2 Activity Sequencing  Involves reviewing activities and determining dependencies.  A dependency or.
Project Planning Instructor: Dr. Jerry Gao. Project Planning Jerry Gao, Ph.D. Jan Software Scope - Obtaining Information Necessary for Scope -
Software Engineering: A Practitioner’s Approach
HIT241 - TIME MANAGEMENT Introduction
Software Project Management Task Sequencing Activity Sequencing Concepts PERT charts Critical Path Analysis.
Time Management Week 7 - Learning Objectives You should be able to: n List and describe the processes, activities, inputs, and outputs in time management.
Chapter 6: Project Time Management Information Technology Project Management, Fifth Edition Note: some slides have been removed from the author’s original.
Project Time Management J. S. Chou, P.E., Ph.D.. 2 Activity Sequencing  Involves reviewing activities and determining dependencies.  A dependency or.
Software Project Management Task Estimating and Scheduling
Cmpe 589 Spring Software Quality Metrics Product  product attributes –Size, complexity, design features, performance, quality level Process  Used.
Project Time Management, Mohammad A. UHCL 1 Project Time Management Mohammad A. Rob.
MODULE PLANNING &ESTIMATION.
Real-World Project Management Chapter 13. Characteristics of Project Management Unique one-time focus –Difficulties arise from originality Subject to.
Scheduling Sequence & Time.
Chapter 6: Project Time Management
POST GRADUATE PROGRAM OF INFORMATION TECHNOLOGY
Chapter 6 : Software Metrics
Project Management Project Planning Estimating Scheduling.
~ pertemuan 6 ~ Oleh: Ir. Abdul Hayat, MTI 03-Apr-2009 [Abdul Hayat, Project Time Management, Semester Genap 2008/2009] 1 PROJECT TIME MANAGEMENT.
Quick Recap. Work Breakdown Structure (WBS): Set of activities to do (“use cases”) Formats of WBS Risk associated WBS Approaches for WBS Dependency Graph:
Successful IT Projects slides © 2007 Darren Dalcher & Lindsey Brodie Successful IT Projects By Darren Dalcher & Lindsey Brodie
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
Chapter 6: Project Time Management Information Technology Project Management,
1IT Project Management, Third Edition Chapter 6 Chapter 6: Project Time Management.
Copyright Course Technology Chapter 5: Project Time Management.
Advanced Project Management Project Time Management Ghazala Amin.
1 Chapter 5 Software Project Planning. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling,
Collecting requirements – Different methods Defining scope – Estimates for all resources Creating the WBS – Different approaches Verifying scope – Formal.
Project Time Management
Intro to Estimating Part Art, Part Science. Importance of Good Estimates Time (Realistic Deadlines) most software projects are late because the time was.
Reference: Figure 6.2. PMBOK® Guide, 5 h Ed Reference: Figure 6.2. PMBOK® Guide, 5 h Ed.
Chapter 4 Note: See the text itself for full citations.
1 Chapter 6: Project Time Management. 2 Learning Objectives Understand the importance of project schedules and good project time management Define activities.
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
1IT Project Management, Third Edition Chapter 6 Chapter 6: Project Time Management.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Project Scope, Time and Cost IT Project Management PM Knowledge Areas:
1 Chapter 6 Project Time Management BLBSC Programmes Prepared by: Eng Kok Siong Quality checked by: Olympia College Johor Bahru Copyright 2010 University.
Eleanor Roosevelt High School
Chapter 6: Project Time Management
CHAPTER 6 PROJECT TIME MANAGEMENT
Project Time Management
Project Time Management
Project Time Management
Project Time Management
Project Time Management
Importance of Project Schedules
Project Time Management
CHAPTER 6 PROJECT TIME MANAGEMENT
Presentation transcript:

PROJECT TIME MANAGEMENT

IMPORTANCE Average time overrun on unsuccessful IT projects was 222 % of the original estimation CHAOS Report It was reduced to 63% in CHAOS Report One may massage the overrun of cost and scope Time passes no matter what happens on a project Time can be measured easily and simply

Conflict intensity over the life of a project Project Formation Early Phase Middle Phase End Phase SchedulePriority ManpowerTech. option Procedure costPersonality Conflict Intensity Average Total Conflict

MAIN PROCESS OF PTM Activity definition involves identifying the specific activities to produce the deliverables. Activity duration estimating involves estimating the work periods that are needed to complete individual activities. Activity sequencing involves identifying and documenting the relationships between activities. Schedule development involves activity estimating, sequencing and resources Schedule control involves controlling and managing changes to the project schedule

ACTIVITY (TIME) ESTIMATION Define project type and Understand scope Reusable software resources Skill set needed Software project estimation Estimation of resource, schedule, and cost based on conditions defined by Program Plan and Engineering Plan. Project Type: Product: requirements from market Customized: RFP and proposal System Integration: RFP and proposal People Reusable Tools Project Resources

ACTIVITY (TIME) ESTIMATION Problem-Based Estimation Line-Of-Code-Based (LOC) Function-Point-Based (FP) Process-Based Estimation History Record-Based

ESTIMATION FAILURE Estimation of resource (human resource, reusable, skill set, domain expertise), schedule, and cost based on conditions defined by Program Plan and Engineering Plan. FAILED PROJECT IRADIUM Low Orbit, 66 satellites, 11 ground stations International: US, Russian, China, … Postmortem : Marketing Time to market Targeting (small customer group) Technology Management (estimation) Scope Size Payload Cross link In orbit link handset Ground stations

WORK BREAKDOWN WORK BREAKDOWN STRUCTURE (WBS) Define product scope Identify function by decomposing scope Do while functions remain select a function assign all functions to sub functions list do while sub functions remain select a function if similar to historical function then use its estimation + change else if the function can be estimated then estimate else further decompose end if end do End do

EXAMPLES OF ESTIMATION The CAD software will accept two- and three-dimensional geometric data from an engineer. The engineer will interact and control the CAD system through a user interface that will exhibit characteristics of good human/machine interface design. All geometric data and other supporting information will be maintained in a CAD database. Design analysis modules will be developed to produce the required output, which will be displayed on a variety of graphics devices. The software will be designed to control and interact with peripheral devices that include a mouse, digitizer, laser printer and plotter. User interface and control facilities (UICF) Two-dimensional geometric analysis (2DGA) Three-dimensional geometric analysis (3DGA) Database management (DBM) Computer graphics display facilities (GCDF) Peripheral control function (PFC) Design analysis modules (DAM) Computer-aided Design Application For Mechanical Component:

LOC-BASED ESTIMATION FUNCTIONEST. LOC User interface and control facilities (UICF) Two-dimensional geometric analysis (2DGA) Three-dimensional geometric analysis (3DGA) Database management (DBM) Computer graphics display facilities (GCDF) Peripheral control function (PFC) Design analysis modules (DAM) 2,300 5,300 6,800 3,350 4,950 2,100 8,400 TOTAL33,200 ESTIMATED LOC = ( S optimistic + 4* S moderate + S pessimistic ) / 6 TOTAL PROJECT COST = $431,000 (54 person-month) Productivity=620 LOC/pm Salary=$8,000 Cost/LOC=$13

FP-BASED ESTIMATION I Information domainOpt.LikelyPess.Est. Count WeightFP Count Number of inputs Number of outputs Number of inquiries Number of files Number of external interfaces Count Total320 FP Count = Weight * ( FP optimistic + Weight* FP likely + FP pessimistic) / (Weight +2) FP estimated = Count Total * [ * Σ(Fi)] = 375 TOTAL PROJECT COST = $461,000 (58 person-month) Productivity=6.5 FP/pm Salary=$8,000 Cost/FP=$1,230

FP-BASED ESTIMATION II FactorValue (Fi) Backup and recovery4 Data communication2 Distributed processing0 Performance critical4 Existing operating environment3 On-line data entry4 Input transaction over multiple screen5 Master files updated on-line3 Information domain values complexity5 Internal processing complexity5 Code design for reuse4 Conversion/installation in design3 Multiple installation5 Application designed for change5 Complexity adjustment factor1.17

HISTORICAL PROJECT METRICS Project Type: Product: requirements from market Customized: RFP and proposal System Integration: RFP and proposal Previous methods only estimate coding, not requirement, design, documentation, etc. Use historical project data (similar projects, metrics) 20 LOC/day (…), simple but efficient, hourly price of engineer (head count cost) including management cost + travel cost + per dine Requirement collection + analysis = implementation Product size estimation: brainstorm and bi-weekly estimation Type of projects: Cost + profit, Fixed price Difficult to estimate scope during bid process, to get the project, cut price and under estimate Application domain knowledge expertise

ACTIVITY SEQUENCING PROJECT NETWORK DIAGRAM: a schematic display of the logical relationships among, or sequencing of, activities. Arrow diagramming method (ADM) Precedence diagramming method (PDM)

ADM Activity-On-Arrow (AOA) A=1 B=2 C=3 D=4 E=5 G=6 F=4 H=6 I=2 J=3 Critical Path (B-E-H-J) Is the series of activities that determine the earliest time by which the project can be completed. It is the longest path through the network diagram and has the least amount of slack (not the shortest path in the domain of transportation) Burst Merge

Activity-On-Arrow (AOA) A=1 B=2 C=3 D=4 E=5 G=6 F=4 H=6 I=2 J= TASKSLACK A2 B0 C2 D2 E0 F7 G2 H0 I2 JO 5: A-D=5; B-E=7 6: A-D-H=11; B-E-H=13; B-F=6; C-G-I=11

DUMMY ACTIVITY A=1 B=2 C=3 D=4 E=5 G=6 F=4 H=6 I=2 J=3 8 K=11 9 L=1 Critical Path Method (CPM) Dummy activity

PDM A B A B A B A B Finish-to-start (FS) Task B cannot start until task A finishes Start-to-start (SS) Task B cannot start until task A starts Finish-to-finish (FF) Task B cannot finish until task A finishes Start-to-finish (SF) Task B cannot finish until task A starts

A Start: Finish: ID: 1 C Start: Finish: ID: 3 D Start: Finish: ID: 4 E Start: Finish: ID: 5 B Start: Finish: ID: 2

A B C D E F G H I J SMTWTFSSMTWTFSSMTWTFSSM Gantt Chart

Techniques for shortening schedule Crashing: making cost and schedule trade-offs to obtain the greatest amount of schedule compression for the least incremental cost a 43b 3c 2 A=5B=9 A=5 B1=4 B2=3 B3=2 B1’=1 B3’=2 In preparing critical path diagram for a project, usually resource is not considered. You may have to consider resources when shortening schedule.

Techniques for shortening schedule Fast tracking: doing activities in parallel that you would normally do in sequence A=5B=9 A’=0 B=9 C=6 4 A=5

CRITICAL CHAIN SCHEDULING Avoid multitasking Multitasking: when a resource works on more than one task/project at a time. TASK 1TASK 3 10 days Task 2 completed Task 3 completed Task 1Task 2Task 3Task 1Task 2Task 3 10 days 5 days Task 1 completed Task 2 completed Task 3 completed +△+△ +△+△ +△+△ TASK 2 Task 1 completed

CRITICAL CHAIN SCHEDULING Avoid individual buffer Individual buffers: when activity duration estimations are done by individuals, safety (buffer) is usually included for each estimation. FB Proj. buffer Add project buffer and feeding buffer (FB)

CRITICAL CHAIN SCHEDULING Probabilistic time estimates Optimistic time + 4xmost likely time + pessimistic time = 6 Weighted average