Description
various estimation techniques used in software projects with different scenarios along with estimation examples.
SW Project Management
?Estimation
Techniques
Why Estimation
? proper project planning and control ? under-estimating a project leads ? under-staffing it ? staff burnout ? under-scoping ? below quality ? cost overrun ? schedule overrun ? loss of credibility as deadlines are missed
? over-estimating a project can be just about as bad
What to estimate
? size of the project (LOC / FP) ? effort in person-months (hours / weeks) ? schedule in calendar months. ? project cost in dollars (or local currency)
How to Estimate
? size of the project (LOC / FP) ? Analogy ? Product features (FP) ? effort in person-months (hours / weeks) ? Company data ? Software life-cycle ? COCOMO ? WBS ? Function Point Analysis
How to Estimate
? Schedule in calendar months
?
? ? ? ?
WBS staff profile company data industry models thumb rule [Schedule = 3.0 * (effort-months) 1/3]
? project cost in dollars (or local currency) ? labor, hardware, software, travel, communications, training, office space
Estimation Process
Estimation - Scenarios
?Fixed Schedule Projects
? Work backwards to fit schedule into effort ? Prioritize functionality & deliver only those ? Generate “what-if” scenarios using Tools
? New Development Projects
? Estimate only after Architecting ? Estimate only through Function Points ? Do not use estimation models / past history
Estimation - Scenarios
? Small Projects
? Don’t spend time Architecting ? Do not use estimation models / past history ? Identify the Team before starting estimation ? Have the Project Manager or the specific Team
which is doing the Project to estimate ? SDLC is not the always best choice
Estimation - Scenarios
? New Domain Projects
? Classify project as “leading-edge” or “bleeding
edge” ? Use a Risk Checklist ? Take risks very clearly to Management / Customer ? Select Iterative Lifecycle (like RUP) ? Plan releases in Phases. ? Re-estimate after each release
Estimation Tips
? allow enough time to do a proper project estimate (gimme a
break) ? rushed estimates are inaccurate & high-risk ? for large development projects, the estimation step should really be regarded as a mini-project. ? where possible, use documented data from Wipro’s own similar past projects ? use developer-based estimates. Do not give estimation to Resource Managers ? use estimation tools often ? have different independent people estimate ? try to use a standard estimation template
Estimation examples
? Effort Estimation example ? Cost estimation example ? Risk estimation example
Estimation examples
? Effort Estimation example ? Cost estimation example ? Risk estimation example
Thank You…
? Thank You…
doc_518494826.pptx
various estimation techniques used in software projects with different scenarios along with estimation examples.
SW Project Management
?Estimation
Techniques
Why Estimation
? proper project planning and control ? under-estimating a project leads ? under-staffing it ? staff burnout ? under-scoping ? below quality ? cost overrun ? schedule overrun ? loss of credibility as deadlines are missed
? over-estimating a project can be just about as bad
What to estimate
? size of the project (LOC / FP) ? effort in person-months (hours / weeks) ? schedule in calendar months. ? project cost in dollars (or local currency)
How to Estimate
? size of the project (LOC / FP) ? Analogy ? Product features (FP) ? effort in person-months (hours / weeks) ? Company data ? Software life-cycle ? COCOMO ? WBS ? Function Point Analysis
How to Estimate
? Schedule in calendar months
?
? ? ? ?
WBS staff profile company data industry models thumb rule [Schedule = 3.0 * (effort-months) 1/3]
? project cost in dollars (or local currency) ? labor, hardware, software, travel, communications, training, office space
Estimation Process
Estimation - Scenarios
?Fixed Schedule Projects
? Work backwards to fit schedule into effort ? Prioritize functionality & deliver only those ? Generate “what-if” scenarios using Tools
? New Development Projects
? Estimate only after Architecting ? Estimate only through Function Points ? Do not use estimation models / past history
Estimation - Scenarios
? Small Projects
? Don’t spend time Architecting ? Do not use estimation models / past history ? Identify the Team before starting estimation ? Have the Project Manager or the specific Team
which is doing the Project to estimate ? SDLC is not the always best choice
Estimation - Scenarios
? New Domain Projects
? Classify project as “leading-edge” or “bleeding
edge” ? Use a Risk Checklist ? Take risks very clearly to Management / Customer ? Select Iterative Lifecycle (like RUP) ? Plan releases in Phases. ? Re-estimate after each release
Estimation Tips
? allow enough time to do a proper project estimate (gimme a
break) ? rushed estimates are inaccurate & high-risk ? for large development projects, the estimation step should really be regarded as a mini-project. ? where possible, use documented data from Wipro’s own similar past projects ? use developer-based estimates. Do not give estimation to Resource Managers ? use estimation tools often ? have different independent people estimate ? try to use a standard estimation template
Estimation examples
? Effort Estimation example ? Cost estimation example ? Risk estimation example
Estimation examples
? Effort Estimation example ? Cost estimation example ? Risk estimation example
Thank You…
? Thank You…
doc_518494826.pptx