Project Context: Positioning the Project in Its Environment
What this domain tests
Project Context examines whether you can place a project correctly against its surroundings: the parent organisation, the stakeholders, and the external factors that constrain it. Exam items ask you to classify a factor as internal or external, to judge a stakeholder analysis, or to decide what belongs to the project versus routine operations.
Core rules
- A project is temporary, unique, result-oriented and bounded by time, budget and capacity. Work that repeats indefinitely is line activity, not a project.
- A programme is a set of related projects managed together for a shared benefit; a project is a single temporary endeavour. Do not confuse the two in scenario questions.
- Stakeholders are analysed, not merely listed. A power/interest grid determines the strategy: high power–high interest is managed closely, high power–low interest is kept satisfied, low power–high interest is kept informed, low–low is monitored.
- Context splits into internal factors (strategy, culture, maturity, systems, available capacity, governance rules) and external factors (legislation, market, technology, suppliers, labour market).
- The project mandate from the project owner states why the project exists and what authority the project manager holds. Context changes during the project and must be re-scanned at decision points.
Worked example
A municipality runs a project to replace its permit-issuing system. New national privacy legislation takes effect three months before the planned go-live - an external factor. The power/interest analysis shows the data protection officer has high interest and high power over acceptance, while the IT operations department has high power and low interest until handover. Reasoning: the legislation is a compliance constraint that changes acceptance criteria, so the quality plan is updated; the DPO is managed closely and invited to review data flows early; IT operations is kept satisfied through scheduled handover briefings rather than daily involvement.
Traps that cost marks
- Producing a stakeholder list with no analysis, priority or engagement strategy.
- Ignoring the parent organisation’s planning cycles, budget rules or approval gates.
- Assuming the context is fixed - legislation, suppliers and sponsors change mid-project.
- Treating recurring service delivery as a project.