CH 2
CH 2
CH 2
Project Classification
Typical Project Cost and Staffing Level Across the Project Life Cycle
In the project life cycle:-
• The level of uncertainty is highest and, hence, risk of failing
to achieve the objectives is greatest at the start of the
project.
• The certainty of completion generally gets progressively
better as the project continues.
• Cost and staffing levels are low at the start, peak during the
intermediate phases, and drop rapidly as the project draws
to a conclusion.
CHAPTER TWO
PROJECT PLANNING
PROJECT PLANNING
• Used for managing the overall project activity.
• In the planning process the planning groups identify,
define, and mature the project scope, project cost, and
schedule the project activities that occur within the project.
• As new project information is discovered, additional
dependencies, requirements, risks, opportunities and
constraints will be identified or resolved.
• While planning the project, the project team should involve
all appropriate stakeholders, depending upon their influence
on the project and its outcomes.
Activities in the Project Planning
Introduction
• Objectives
• functions of the project
• Performance Issues
• Management and Technical Constraints
Project Estimates
• We may use Historical Data
• Estimation Techniques Used
• Effort, Time, and Cost Estimates
Schedule
• Work Breakdown Structure (WBS)
• Gantt Chart Representation
Activities in the Project Planning…
Project Resources
• People
• Hardware and Software
Staff Organization
• Team Structure
• Management Reporting
Risk Management Plan
• Risk Analysis, Identification, Risk Estimation
• Project Tracking and Control Plan
Miscellaneous Plans
• Quality Assurance Plan:-which is performed based on the
standard. Standards are the key to effective quality management.
Project Parameter Estimations
Project estimations
• To estimate various project parameters like project size, cost,
effort, and duration by using various estimation techniques.
Project Estimation Techniques
Empirical Estimation
• Expert Judgment
• Delphi cost estimation
Heuristic estimation Technique
• COCOMO
Analytical estimation technique
• Halstead software science
Empirical Estimation
Expert Judgment
• Here an expert guess about problem size after analyzing the problem
• Usually expert estimates the cost of modules of each subsystem to
get the overall estimation of system.
• Problem:-There may be personal bias and interference.
Delphi cost estimation:-
• Here estimation is carried out by an expert team with a coordinator.
• The coordinator gives SRS document and a cost recording form to
each expert.
• Each expert records cost in the form and submits to coordinator.
• Coordinator compiles several times and prepare the final cost
estimation report.
Heuristic estimation Technique
COCOMO(Constructive cost estimation model)
• Effort= a1.(Size)power of a2 Programmer Months
• Tdev= b1.(Effort)power of b2 Months
Where size of project= KLOC(Kilo line of codes) and a1,a2,
b1,b2 are the constants for each category of project.
Effort= total effort required to develop a project.
Estimation Steps:-
1. Determine size of the product(KLOC)
2. From the size estimated, determine the effort needed.
3. From the effort estimate, determine project duration, and cost
Heuristic estimation Technique
Estimation of development effort
For the three classes of projects, the formulas for estimating
the effort based on the code size are :-
• Organic: Effort=2.4(KLOC)1.05 PM
• Semidetached: Effort=3.0(KLOC)1.12 PM
• Embedded: Effort=3.6(KLOC)1.20 PM
Estimation of development Time
• Organic: Tdevt=2.5(Effort)0.38 months
• Semidetached: Tdev=2.5(Effort)0.35 months
• Embedded: Tdevt=2.5(Effort)0.32 months
Example:- Assume the size of a project= 32KLOC
• Basic COCOMO estimation formula for organic type of
project:
• Effort=2.4(32Kloc)power of 1.05=91PM
• development time = 2.5(434PM) power of 0.38 = 25 months
Analytical estimation technique
• Halstead software science:- a software metrics introduced
by Howard Halstead to estimate the project size based on
over all program length
• Used a few primitive program parameters to estimate a
given project
• Most of the time this technique is not applied
Project scheduling Steps
Project scheduling is an important project planning activity
used to decide which task should be taken first.
1. Identify all tasks needed to complete a project
2. Break down large tasks into smaller activities.
3. Determine dependencies among them
4. Establish time duration to complete activities.
5. Allocate resources to activities
6. Monitor the timely progress of the activities
Step-1 and 2 :- after identifying tasks the project manager
break down this large task into smaller activities by using a
work breakdown structure
Project scheduling Steps
Step-3 and 4:-The task dependencies define partial ordering of
tasks and the dependencies among the activities can be determined
by using an activity network.