- Temporary: Defined start and end date; team disbands upon completion.
- Unique Output: Creates a novel product/service, unlike routine operations.
- Goal-Driven: Judged against agreed objectives & acceptance criteria.
- Constrained: Bounded by Time, Budget, People, and Technology.
What is a Software Project?
- Planning, organizing, staffing, directing, monitoring, and controlling software projects.
- 3 Control Cycle Stages: (1) Feasibility & Planning, (2) Execution & Monitoring, (3) Control & Closure.
- Categorizing Projects: Information Systems vs. Embedded; Product-Driven vs. Objective-Driven; In-House vs. Outsourced.
- Construction: Tangible physical artifact (bridge, building).
- Research: Generates knowledge, models, or patents.
- Reengineering: Changes existing process/system (e.g., PRINCE2 adoption).
- Procurement & Business Impl.: Supplier tenders or new business processes.
Software vs. Ordinary Projects: ICCF
PM Fix: Artificial visibility via WBS milestones, prototypes & burn-down charts.
PM Fix: Modular design, formal specs, code reviews & automated testing.
PM Fix: Intensive requirements engineering & domain validation.
PM Fix: Strict Change Control to prevent scope creep.
Critical Exam Trap: Flexibility is NOT an Advantage!
Never write that flexibility makes software easier to manage. In Hughes & Cotterell / Brooks, perceived flexibility invites relentless late changes, schedule slippage, and architectural decay.
The Triple Constraint & Key Laws
Scope, Time & Cost Coupled Around Quality
| If Client Asks To... | Required Trade-Off |
|---|---|
| Add features (+Scope) | Extend schedule (Time) or increase budget (Cost) |
| Deliver sooner (-Time) | Cut features (Scope) or add resources (+Cost) |
| Spend less (-Cost) | Reduce Scope or accept a longer Time schedule |
1. Brooks' Law
"Adding manpower to a late software project makes it later" — due to onboarding overhead and combinatorial communication channels $n(n-1)/2$.
2. Parkinson's Law
"Work expands to fill the time available for its completion" — over-estimating schedules wastes budget without finishing early.
3. Weinberg's Zeroth Law of Reliability
"If a system doesn't have to be reliable, it can meet any other objective" — severe under-estimation forces teams to ship broken code.
What PMs Do & Stakeholder Matrix
5 Core PM Activities (Lecture Notes)
1) Scope & Requirements • 2) Schedule & Estimation • 3) People & Resources • 4) Risk & Quality • 5) Communication. ("Maintenance has money!")
Lifecycle Deliverables (5 Groups)
Initiation: Business Case, Project Charter.
Planning: SRS, WBS, Schedule, Budget, Risk Plan.
Execution: Designs, Code, Tested Builds.
Monitoring & Control: Status Reports, Change Logs.
Closure: Final Product, Sign-off, Lessons Learned.
| Power | Interest | Strategy & Examples |
|---|---|---|
| High | High | Manage Closely: Project Sponsor, Client |
| High | Low | Keep Satisfied: Senior Executives |
| Low | High | Keep Informed: End Users, Dev Team |
| Low | Low | Monitor: Other Departments |
Lecture 1 Marking Guides
- Q1 (10m): Define Project & SPM + 4 characteristics separating projects from routine work (unique, temporary, interdependent, constrained).
- Q2 (12m): Discuss 4 ways software projects differ from physical projects + management challenges (ICCF).
- Q3 (9m): Describe Feasibility, Planning, and Execution/Control stages & how they form a closed feedback loop.
- Q4 (9m): 5 core responsibilities of a Software PM (don't write "writing all C++ code solo"!).
- Q5 (10m): Triple Constraint trade-offs + Brooks' Law impact when adding staff late.
- Changing Requirements: Needs evolve once users see prototypes.
- Estimation: Effort is hard to predict for novel one-off systems.
- Intangibility: Code progress cannot be seen physically.
- Technical Risk: Unproven tools, integrations, latent defects.
- Communication: Coordinating large/distributed teams.
- Quality Pressure: Tight deadlines tempt teams to skip testing.
Completed Concept 1: SPM Foundations
Next up: Standish CHAOS failure modes, Costs/Benefits taxonomy, Payback, ROI, and NPV.