Information Technology Project Management: by Jack T. Marchewka
Information Technology Project Management: by Jack T. Marchewka
Technology Project
Management
by Jack T. Marchewka
Copyright 2006 John Wiley & Sons, Inc. all rights reserved. Reproduction or translation of this work beyond that permitted
in Section 117 of the 1976 United States Copyright Act without the express permission of the copyright owner is unlawful.
Request for further information information should be addressed to the Permissions Department, John Wiley & Sons, Inc.
The purchaser may make back-up copies for his/her own use only and not for distribution or resale. The Publisher
assumes no responsibility for errors, omissions, or damages caused by the use of these programs or from the use of the
information contained herein.
Chapter 6
The Work Breakdown
Structure & Estimation
Learning Objectives
Develop a work breakdown structure (WBS).
Describe the difference between a deliverable and a
milestone.
Describe and apply several project estimation methods.
These include the Delphi technique, time boxing, topdown estimation, and bottom-up estimation.
Describe and apply several software engineering
estimation approaches. These include lines of code
(LOC), function point analysis, COCOMO, and
heuristics.
Activity definition
Activity sequencing
Activity duration estimation
Schedule development
Schedule control
Work Package
Milestones
Significant events or achievements
Acceptance of deliverables or phase completion
Cruxes (proof of concepts)
Quality control
Keeps team focused
Estimation Techniques
- The Project Management Approach
Guesstimating
Delphi Technique
Time Boxing
Top-Down
Bottom Up
Analogous Estimates (Past experiences)
Parametric Modeling (Statistical)
Project Estimation
Guesstimating
Based on feeling and not facts
Not a good method for estimating but often used
by inexperienced project managers
Delphi Technique
Involves multiple, anonymous experts
Each expert makes an estimate
Estimates compared
If close, can be averaged
Another iteration until consensus is reached
Project Estimation
Time Boxing
A box of time is allocated for a specific
activity, task, or deliverable
Can focus a team if used effectively
Can demoralize a team if used too often or
ineffectively because of the increased stress
or pressure on the project team to get things
done
Project Estimation
Top-Down Estimating
Top and middle managers determine overall project
schedule and/or cost.
Lower level managers are expected to breakdown
schedule/budget estimates into specific activities
(WBS).
Often couched in terms of what a project should cost
and how long it should take as decreed by a member
of top management who thinks those parameters are
appropriate.
May be a response to the business environment.
May lead to a death march project.
Project Estimation
Bottom-Up Estimating
Most common form of project estimation
Schedules & budgets are constructed from
the WBS
Starts with people who will be doing the work
Schedules & budgets are the aggregate of
detailed activities & costs
Project Estimation
Analogous estimating
based on similarity between current projects
and others
Use information from previous, similar
projects as a basis for estimation
Project Estimation
Parametric Modeling
Use project characteristics (parameters) in a
mathematical model to estimate
Example: $50/ LOC based on:
Programming language
Level of expertise
Size & complexity
1 day
5 days
2 days
3 days
1 day
5 days
Count comments?
Declaring variables?
Efficient code vs. code bloat
Language differences
Easier to count afterwards than to estimate before
programming begins
Inputs
Outputs
Inquiries
Logical Files
Interfaces
Complexity
Low
Average
High
Total
_3x 7=21
_2x 10=20
_1x 15=15
56
__x 5=__
_2x 7=14
__x 10=__
14
ExternalInput
(EI)
_3x 3=9
_5x 4=20
_4x 6=24
53
External
Output(EO)
_4x 4=16
_2x 5=10
_1x 7=7
33
External
Inquiry(EQ)
_2x 3=6
_5x 4=20
_3x 6=18
44
Internal
LogicalFiles
(ILF)
External
InterfaceFiles
(EIF)
200
Degree of Influence
DataCommunications
DistributedDataProcessing
Performance
HeavilyUsedConfiguration
TransactionRate
On-lineDataEntry
EndUserEfficiency
OnlineUpdate
ComplexProcessing
Reusability
InstallationEase
OperationalEase
MultipleSites
FacilitateChange
2
Total Degrees of Influence
ValueAdjustmentFactorVAF=(TDI*0.01)+.65
40
VAF=(40*.01)+.65=1.05
FP=200*1.05=210
Language
Access
38
7,980
Basic
107
22,470
128
26,880
C++
53
11,130
COBOL
107
22,470
Delphi
29
6,090
Java
53
11,130
MachineLanguage
640
134,440
VisualBasic5
29
6,090
Source:http://www.theadvisors.com/langcomparison.htm
COCOMO
COnstructive COst MOdel
Parametric Model developed by Barry Boehm in
1981
Project types
Organic
Routine projects where the work is expected to go smoothly
with few problems
Embedded
Challenging projects that may be new ground for the
organization or project team
Semi-detached
In between organic and embedded. Projects that may not be
simple and straightforward, but there is a high degree of
confidence that the project team can meet the challenge
Embedded Challenging
Person Months = 3.6 * KDSI1.20
Semi-Detached Middle
Person Months = 3.0 * KDSI1.12
Semi-Detached
Duration = 2.5 * Effort0.35
Embedded
Duration = 2.5 * Effort0.32
COCOMO
COnstructive COst MOdel
COCOMO Model Types
Basic
Intermediate
Advanced
COCOMO II
Heuristics
(Rules of Thumb)
Whenforschedulingasoftwaretask:
1/3Planning
1/6Coding
1/4Componenttestandearlysystemtest
1/4Systemtest,allcomponentsinhand