# Software Project Management

> Computer Science · CIE A-Level 9618
> Source: https://www.owlsprep.com/study/cie-9618-u12-software-project-management/

This sub-topic covers core principles of software project management for CIE A-Level 9618, including methodologies, scheduling, risk management, and team roles. It is frequently tested in Paper 1 short answer and extended response questions.

**Prerequisites:** [Basic understanding of the software development lifecycle](https://www.owlsprep.com/study/cie-9618-u12-software-development-lifecycle/)

## Learning objectives

- Explain core principles and key terms of software project management
- Compare waterfall and agile methodologies for different development scenarios
- Identify common project risks and appropriate mitigation strategies
- Recall key roles and responsibilities in software project teams

## Core Principles and Key Terms

Software project management is the practice of planning, monitoring, and controlling software development to deliver a product that meets stakeholder requirements within agreed time, cost, and quality constraints. All projects are bound by the triple constraint of scope, time, and cost, which must be balanced to deliver a successful outcome.

**Software Project Management** — The process of initiating, planning, executing, monitoring, and closing software development work to meet specific goals and success criteria

*Example:* A team building a student attendance app manages developer hours, deadlines, and changing client feature requests to deliver a working product on budget.

- **Scope**: The set of features and requirements the project must deliver
- **Stakeholders**: All people or groups affected by the project outcome
- **Risk**: Any uncertain event that can positively or negatively impact the project
- **Deliverable**: A tangible or intangible output produced during the project

**Worked example:** Identify 4 key constraints for a project to develop a new e-commerce website for a small local business.

1. Step 1: Define what a project constraint is: any factor that limits project delivery.
2. Step 2: Identify the first two constraints: scope (required features: checkout, user accounts, inventory tracking) and time (deadline before the holiday shopping season).
3. Step 3: Identify the remaining two constraints: cost (limited small business budget for developer hours) and quality (must meet security standards for handling customer payment data).

## Project Management Methodologies

CIE 9618 frequently asks for comparisons of the two most common project management methodologies: waterfall and agile. A methodology is a structured approach to organizing and completing project work.

**Comparing methods**

Below is a comparison of the two core methodologies tested in the exam:

- **Waterfall** — Linear sequential approach where each phase of development is completed before moving to the next. Requirements are fixed and fully documented at the start of the project.
  - Pros: Easy to manage and schedule; Clear comprehensive documentation; Works well for small projects with stable requirements
  - Cons: Inflexible to changing requirements; Testing occurs late, leading to costly rework; Full product is only delivered at the end

- **Agile** — Iterative incremental approach where work is split into short fixed-length sprints. Requirements evolve over time, with regular stakeholder feedback after each sprint.
  - Pros: Adapts easily to changing requirements; Early working product is available for testing; Lower risk of costly major rework
  - Cons: Higher risk of unmanaged scope creep; Less comprehensive documentation; Final cost and timeline are harder to predict upfront

> **tip**
>
> When asked to recommend a methodology in an exam question, always link your choice to the specific details of the scenario. Never just state that agile is always better.

**Worked example:** Recommend a methodology for a project developing a new social media app where requirements are not fully defined, and the client wants regular updates to adjust features.

1. Step 1: Analyze the key characteristics of the scenario: unclear initial requirements, need for regular client input and changes.
2. Step 2: Eliminate waterfall: Waterfall requires all requirements to be fixed at the start, and cannot accommodate mid-project changes without major disruption and cost.
3. Step 3: Justify agile: Agile splits work into 2-4 week sprints, after each sprint the client can review the working product and adjust requirements. This matches the scenario needs perfectly.

## Scheduling and Risk Management

Project scheduling involves breaking work into tasks, identifying dependencies between tasks, and tracking progress against deadlines. Risk management is the process of identifying potential problems and putting mitigation strategies in place to reduce their impact.

**Critical Path** — The longest sequence of dependent tasks that determines the shortest possible time to complete the entire project. Any delay to a task on the critical path delays the overall project end date.

*Example:* If designing a database must be completed before coding the app backend, both tasks are part of the critical path.

Common software project risks include scope creep, staff turnover, unrealistic deadlines, and unproven technical complexity. Each risk has a corresponding mitigation strategy to reduce impact.

**Worked example:** A software project is at risk of scope creep from regular client requests for new features. Explain one effective mitigation strategy for this risk.

1. Step 1: Define scope creep to set context: uncontrolled, unapproved changes to project scope that lead to delays and increased cost.
2. Step 2: Describe a formal change control process: all new feature requests are written down, assessed for their impact on project time, cost, and scope, and only approved or rejected by the project steering group before any work begins.
3. Step 3: Explain why this works: it prevents unplanned work from being added to the project without adjusting deadlines and budget to accommodate the change, keeping the project on track.

## Team Roles and Stakeholder Management

CIE exam questions often ask about the responsibilities of key roles in a software project team. Below are the core roles you need to remember:

- **Project Manager**: Overall responsibility for planning, scheduling, budget, and on-time delivery
- **Business Analyst**: Elicits and documents requirements from stakeholders
- **Developer**: Writes, tests, and maintains code for the product
- **Tester**: Independently verifies that the product meets requirements and identifies bugs
- **Client/End User**: Defines requirements and accepts the final product

**Worked example:** A development team has no clear understanding of what the client needs from the product. Which role is responsible for resolving this, and why?

1. Step 1: Identify the correct role: Business Analyst.
2. Step 2: Explain the role's core responsibility: Business Analysts communicate directly with clients and stakeholders to elicit, clarify, and document requirements clearly for the development team.
3. Step 3: Justify: A clear requirements document produced by the Business Analyst removes ambiguity and ensures the team builds a product that matches the client's needs.

## Common pitfalls

- **Wrong:** Defaulting to agile as the correct answer regardless of scenario context
  - Why it fails: Many students learn agile is modern and automatically select it, even when the scenario describes fixed requirements.
  - Correct: Always match the methodology to the scenario: use waterfall for fixed, stable requirements and agile for changing, unclear requirements.
- **Wrong:** Claiming any delay to any task delays the whole project
  - Why it fails: Students forget that only critical path tasks affect the overall project end date.
  - Correct: Only tasks on the critical path have zero slack/float. Non-critical tasks can be delayed up to their slack time without changing the project end date.
- **Wrong:** Calling all scope changes scope creep
  - Why it fails: Controlled, approved scope changes are a normal part of any project. Scope creep refers specifically to uncontrolled changes.
  - Correct: Only label unapproved, unplanned changes to project scope that add work without adjusting time or cost as scope creep.
- **Wrong:** Stating agile projects have no documentation
  - Why it fails: Agile prioritizes working software over comprehensive documentation, which is often misinterpreted as no documentation at all.
  - Correct: Agile projects still include sufficient documentation for maintenance and future development, just less comprehensive than waterfall.
- **Wrong:** Assigning requirements gathering to the project manager
  - Why it fails: Students often mix up the responsibilities of project managers and business analysts.
  - Correct: Business analysts are responsible for eliciting and documenting requirements; project managers focus on planning, scheduling, and budget.

## Cheatsheet

| Concept | Waterfall | Agile |
| --- | --- | --- |
| Approach | Linear sequential | Iterative incremental |
| Requirements | Fixed at start | Evolve over time |
| Best for | Stable requirements, regulation-heavy projects | Changing requirements, innovative projects |
| Documentation | Comprehensive | Sufficient, just-in-time |
| Risk of scope creep | Low | High (if unmanaged) |
| Delivery | Full product at project end | Working increment each sprint |
| Flexibility to change | Low | High |

## What's next

Software project management is a core foundation for all further study of software engineering, and lays the groundwork for understanding system development, requirements gathering, and quality assurance for complex projects. This sub-topic is heavily weighted in CIE 9618 Paper 1, with frequent 6-8 mark extended response questions testing your ability to apply concepts to specific scenarios. Focus on practicing methodology comparisons and risk mitigation examples to score full marks. Explore the links below to build on your knowledge of connected concepts.

- [Computational thinking & problem solving (including declarative, OO and AI)](https://www.owlsprep.com/study/cie-9618-u13-overview/)
- [Problem Decomposition](https://www.owlsprep.com/study/cie-9618-u13-problem-decomposition/)
- [Abstraction](https://www.owlsprep.com/study/cie-9618-u13-abstraction/)

---

From [OwlsPrep](https://www.owlsprep.com) — free study guides for A-Level, IB, AP and IGCSE, written against the official syllabus. Canonical page: https://www.owlsprep.com/study/cie-9618-u12-software-project-management/