19-Soft-B6 Software Project Management · May 2015
Nivaar worked solution (AI-drafted; not reviewed by a licensed engineer)
Question text not reproduced: the examination questions are © Engineers and Geoscientists BC. Open the official past paper (linked at the top of this page) to read the question, then follow the worked solution below.
PMBOK's nine knowledge areas partition everything a project manager must actively manage into named disciplines that together cover the whole of a project, from the highest-level coordination down to the individual contract:
| Knowledge area | Purpose |
|---|---|
| Integration | Coordinating all the other knowledge areas and processes into one coherent whole — developing the project charter and management plan, directing and managing the work, and controlling changes so the pieces don't drift out of alignment with each other. |
| Scope | Ensuring the project includes all, and only, the required work (Question 1c) — defining, decomposing (WBS), validating and controlling what "done" means. |
| Time (Schedule) | Sequencing activities, estimating their durations, and developing and controlling the schedule so the project finishes when it needs to. |
| Cost | Estimating, budgeting, and controlling costs so the project finishes within its approved budget. |
| Quality | Planning quality requirements/standards and the activities (assurance and control) that confirm the project's deliverables actually meet them (see Question 3c's QA activities). |
| Human Resource | Identifying, acquiring, developing, and managing the project team — roles, responsibilities, and the interpersonal skills needed to keep the team effective (Pressman's "People" P, Question 4a). |
| Communication | Ensuring project information (status, decisions, risks) is generated, collected, and distributed to the right stakeholders in a timely and appropriate way. |
| Risk | Identifying, analysing, planning responses to, and monitoring risks throughout the project so uncertainty is managed proactively rather than only reacted to. |
| Procurement | Managing the purchase or acquisition of products, services, or results needed from outside the performing team — the project-manager-side counterpart to the Acquisition/Supply processes of Question 5. |
The nine areas are not independent silos: Integration exists specifically because the other eight interact constantly (a schedule slip is usually also a cost and a risk event; a scope change usually also changes cost, time, and often procurement), and a project manager's real job is managing those interactions, not any one area in isolation.
