This subtopic examines the structured phases through which a digital project progresses, from initiation and planning to execution, monitoring, and closure
Topic Synopsis
This subtopic examines the structured phases through which a digital project progresses, from initiation and planning to execution, monitoring, and closure. Understanding the project lifecycle is fundamental to selecting appropriate management methodologies such as Waterfall for linear projects or Agile for iterative development, and to utilising planning tools like Gantt charts and critical path analysis to ensure timely delivery.
Key Concepts & Core Principles
- Project Life Cycle: Understand the phases—initiation, planning, execution, monitoring & control, and closure. Each phase has specific deliverables and activities.
- Project Methodologies: Compare Waterfall (linear, sequential) and Agile (iterative, flexible). Know when to use each, e.g., Waterfall for well-defined projects, Agile for dynamic requirements.
- Critical Path Analysis (CPA): Identify the longest sequence of dependent tasks to determine the minimum project duration. Calculate float/slack to manage delays.
- Risk Management: Identify, assess, and mitigate risks using a risk register. Prioritise risks by probability and impact, and plan responses (avoid, transfer, mitigate, accept).
- Stakeholder Management: Identify stakeholders (internal/external), analyse their influence and interest, and develop communication strategies to keep them engaged.
Exam Tips & Revision Strategies
- When discussing methodologies, always justify your choice by linking it to the project’s characteristics (e.g., requirement stability, client involvement).
- Practise hand-drawing Gantt charts with clear milestones and dependencies, as these may be required in written examinations.
- For critical path analysis, double-check that you have considered all task predecessors and that the forward and backward pass calculations are consistent.
Common Misconceptions & Mistakes to Avoid
- Confusing the Waterfall and Agile methodologies, e.g., stating Agile is suitable for well-defined requirements with minimal change.
- Omitting or misordering lifecycle stages, such as placing monitoring/control after closure.
- Incorrectly linking tasks in Gantt charts, leading to unrealistic schedules or missed dependencies.
- Misidentifying the critical path by ignoring parallel task durations or assuming it is the path with the most tasks.
Examiner Marking Points
- Award credit for accurately identifying and sequencing all lifecycle stages (e.g., initiation, planning, execution, monitoring/control, closure) in a given scenario.
- Award credit for clearly differentiating between Waterfall (sequential, plan-driven) and Agile (iterative, adaptive) methodologies with reference to project suitability.
- Award credit for constructing a Gantt chart with correctly ordered tasks, accurate durations, and clear dependency markers.
- Award credit for performing critical path analysis, identifying the longest sequence of dependent tasks and calculating total float where required.