Unit 2: Managing software projects
Managing Software Projects notes · PTU syllabus (MBA 943-18)
On this page
Unit summary
Managing a software project means measuring, estimating, scheduling and controlling risk. This unit covers process, product and project metrics, software project estimation, planning, scheduling and tracking, risk identification, projection, refinement and mitigation, feasibility analysis in process planning, and cost and effort estimation models.
After this unit you can
- Explain process, product and project metrics
- Estimate size, effort and cost
- Plan, schedule and track software projects
- Manage software project risks and assess feasibility
PTU syllabus topics
- Process/product/project metrics
- software project estimation
- planning
- scheduling and tracking
- risk identification/projection/refinement/mitigation
- process planning feasibility analysis
- cost and effort estimation models
- 1
Identify risks
- 2
Project them
Probability × impact
- 3
Prioritise
- 4
Plan mitigation
- 5
Monitor
- 6
Manage when they occur
Topic 1
Software metrics
Process metrics
Defect removal efficiency, cycle time, productivity over projects
Product metrics
Size (LOC, function points), complexity (cyclomatic), defects per KLOC
Project metrics
Effort, schedule variance, cost variance, earned value
Productivity
Size ÷ person-months
Defect density
Defects ÷ KLOC
Defect removal efficiency
Errors found before release ÷ (errors before + defects after release)
Cyclomatic complexity
Edges − nodes + 2
Topic 2
Software project estimation
- Size estimation: lines of code (LOC), function points (inputs, outputs, inquiries, internal files, external interfaces weighted by complexity and adjusted by 14 general system characteristics), story points in agile.
- Approaches: decomposition (by function or by activity), expert judgement and Delphi, analogy with past projects, empirical models, planning poker in agile.
Topic 3
Cost and effort estimation models
Effort (person-months)
a × (KLOC)^b
Development time (months)
c × (Effort)^d
Organic mode
a = 2.4, b = 1.05, c = 2.5, d = 0.38
Semi-detached
a = 3.0, b = 1.12, c = 2.5, d = 0.35
Embedded
a = 3.6, b = 1.20, c = 2.5, d = 0.32
Example
An organic project of 32 KLOC: effort = 2.4 × 32^1.05 ≈ 91 person-months; time = 2.5 × 91^0.38 ≈ 14 months; average team ≈ 91 ÷ 14 ≈ 6.5 people.
- COCOMO II: application composition, early design and post-architecture models using cost drivers and scale factors.
- Putnam (SLIM) model relates effort, time and size through the Rayleigh curve.
Topic 4
Project planning, scheduling and tracking
- 1
Define scope and objectives
- 2
Feasibility
- 3
Estimate size, effort, cost
- 4
Identify tasks (work breakdown structure)
- 5
Schedule
Network, Gantt chart, critical path
- 6
Allocate resources
- 7
Plan risk, quality, configuration
- 8
Track and control
- Tracking: status meetings, milestones, earned value analysis — planned value (PV), earned value (EV), actual cost (AC); SPI = EV ÷ PV; CPI = EV ÷ AC.
Example
PV ₹40 lakh, EV ₹32 lakh, AC ₹36 lakh: SPI = 0.8 (behind schedule), CPI = 0.89 (over budget).
Topic 5
Risk management
- 1Identification
Checklists — project, technical, business risks
- 2Projection (estimation)
Probability and impact; risk exposure = P × cost
- 3Refinement
Break risks into specific conditions
- 4Mitigation, monitoring and management (RMMM)
Avoid, reduce, transfer, accept; contingency plans
- Common risks: unclear or changing requirements, staff turnover, unrealistic schedules, new technology, third-party dependencies, gold plating.
- Proactive vs reactive risk strategies; the RMMM plan documents them.
Topic 6
Feasibility analysis in process planning
Technical
Is the technology available and mature?
Economic
Do benefits exceed costs (NPV, payback)?
Operational
Will users accept and use it?
Schedule
Can it be done in time?
Legal
Licensing, data protection, contracts
Key terms
- Function point
- Size measure based on functionality delivered
- COCOMO
- Constructive cost model for effort estimation
- Earned value
- Value of work actually completed
- Risk exposure
- Probability multiplied by cost of a risk
- RMMM
- Risk mitigation, monitoring and management
Quick revision
- Process, product, project metrics; DRE, defect density.
- LOC, function points, story points; estimation approaches.
- COCOMO modes and formulas; COCOMO II; Putnam.
- Planning steps; WBS, Gantt, CPM; earned value (SPI, CPI).
- Risk identification, projection, refinement, RMMM; feasibility types.
Important exam questions
Practice questions written to the PTU exam pattern for this unit's syllabus: short answers (Section A style) and long answers (Sections B and C style).
Short-answer questions
- Q1.Distinguish process and product metrics.
- Q2.What is a function point?
- Q3.State the basic COCOMO effort equation.
- Q4.What do SPI and CPI measure?
- Q5.What is risk exposure?
- Q6.Name four types of feasibility.
Long-answer questions
- Q1.Explain software metrics used in project management.
- Q2.Explain software estimation using function points and COCOMO (numerical).
- Q3.Discuss planning, scheduling and tracking of software projects.
- Q4.Explain software risk management and feasibility analysis.
Stuck on this unit?
Message SBS on WhatsApp for help with Managing Software Projects, or to ask about studying MBA at Synetic.