Professional Documents
Culture Documents
Project Planning and Estimation
Project Planning and Estimation
Chapters 23, 24
Software Engineering: A Practitioner’s Approach
Manasvi Mehta
BCA 16 UPTEC Allahabad
+917275142550
Project Planning
When: need for software has already been
established; stakeholders are on-board;
coding is ready to begin
What: project planning spans five major
activities- estimation, scheduling, risk
analysis, quality management planning, and
change management planning
Who: software project managers, with
information from stakeholders and engineers
Estimation
Planning requires estimation early-on, even
though it is likely this “commitment” will
be proven wrong
Some degree of uncertainty is unavoidable
when predicting into the future
Solid techniques and concrete procedures
help reduce the inaccuracy of estimates
Process-based estimation
Most commonly-used technique for project
estimation
Project is broken down into a relatively
small set of tasks and the effort required to
accomplish each task is estimated
Begins with a delineation of software
functions obtained from the project scope
Process-based estimation
A series of framework activities must be
performed for each function
Representative framework activities:
Customer communication
Planning / risk analysis
Engineering
Construction / release
Functions and activities may be shown
together as a table:
Process-based estimation table
Risk
Activity CC Planning Engineering Release CE Totals
analysis
Function Anal. Design Code Test
-- Manasvi Mehta
Relationship between people and
effort
For small software projects, one person can
analyze requirements, perform design,
generate code, and conduct tests
As the projects grow in size, more people
most become involved
As this happens, more and more time is
spent managing the interaction and
communication among the people involved
Relationship between people and
effort
Common myth still believed by many
software managers:
“If we fall behind schedule we can always
add more programmers to catch up.”