← Portal CONCEPT 01 SPM Foundations & ICCF
01 / 05 • 00:00
1.1 Definitions & Project Properties

What is a Software Project?

DEFINITIONCORE
Project
Temporary & Unique Effort
  • 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.
Exam Trap: Running weekly university payroll is routine operations—building a new payroll system by Dec 2026 is a project.
DISCIPLINESPM
SPM
Art & Science of Delivery
  • 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.
Hughes & Cotterell: Planning and Control form a closed-loop feedback cycle until formal handover.
OTHER TYPESDCAP UNIT 1
5 Types
Project Taxonomies
  • 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.
Each project type answers "When to start, stop, and evaluate?" differently.
1.2 Fred Brooks & Hughes & Cotterell (#1 Exam Favorite)

Software vs. Ordinary Projects: ICCF

I
Invisibility
Unlike walls rising on a building site, code progress is intangible ("90% done" looks like "50% done").

PM Fix: Artificial visibility via WBS milestones, prototypes & burn-down charts.
C
Complexity
Per dollar spent, software holds vastly more discrete states, branches, and interactions than bridges.

PM Fix: Modular design, formal specs, code reviews & automated testing.
C
Conformity
Physics is consistent; software must conform to arbitrary human rules, legacy DBs, and tax laws.

PM Fix: Intensive requirements engineering & domain validation.
F
Flexibility
Because text files seem easy to edit, clients constantly demand late changes (nobody moves concrete bridges!).

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.

MEMORIZE: ICCF
1.3 Iron Triangle & Laws of Software Management

The Triple Constraint & Key Laws

THE IRON TRIANGLE

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
Squeezing all three simultaneously destroys Software Quality at the center via rushed, untested code and technical debt.
3 CLASSIC LAWS IN SPM

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.

1.4 Roles, Lifecycle & Stakeholders

What PMs Do & Stakeholder Matrix

5 PM AREAS & 5 PROCESS GROUPS

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 STAKEHOLDER MATRIX
PowerInterestStrategy & Examples
HighHighManage Closely: Project Sponsor, Client
HighLowKeep Satisfied: Senior Executives
LowHighKeep Informed: End Users, Dev Team
LowLowMonitor: Other Departments
Note from Mr Bhuru: A Project Charter formally authorizes the project and names the PM & Sponsor during Initiation.
1.5 NUST Exam Drill & Summary

Lecture 1 Marking Guides

HIGH-FREQUENCY QUESTIONS9–12 MARKS
  • 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.
6 KEY CHALLENGES IN SPMINTRO SLIDES
  • 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.
Ready for economic evaluation? Continue to Concept 2 for Cost-Benefit Analysis & Project Failure!

Completed Concept 1: SPM Foundations

Next up: Standish CHAOS failure modes, Costs/Benefits taxonomy, Payback, ROI, and NPV.

Next: Concept 2 (CBA) →