Top 100 Vocabulary for Adults | Project & Programme Management
Project language is the language of finite delivery: a defined outcome, bounded scope, constrained resources and a point at which the work should be complete. Programme language adds coordination across multiple projects, benefits, dependencies and strategic change that cannot be managed as one isolated delivery plan.
This profession-specific flagship belongs to the eduKate Adult Vocabulary for Professionals system. It connects to Management, Organisational Change and Decision-Making & Judgement.
The Four Banks
Definition & Planning: project, programme, objective, outcome, scope, requirement, deliverable, workstream, milestone, schedule, timeline, budget, resource, capacity, dependency, assumption, constraint, baseline, critical path, sequencing, estimate, contingency, plan, roadmap, charter.
Governance & Stakeholders: sponsor, owner, project manager, programme manager, steering committee, governance, authority, mandate, decision, approval, escalation, stakeholder, stakeholder map, communication, reporting, cadence, status, issue, risk, change control, dependency owner, accountability, responsibility, assurance, review.
Delivery & Control: execution, implementation, task, action, progress, variance, delay, slippage, blocker, bottleneck, critical, priority, quality, acceptance, testing, handover, transition, deployment, procurement, vendor, contract, change request, mitigation, corrective action, completion.
Programme & Benefits: benefit, benefits realisation, business case, strategic alignment, interdependency, portfolio, transformation, capability, adoption, target state, transition state, outcome measure, KPI, baseline, value, impact, sustainment, operating model, readiness, change fatigue, sequencing, prioritisation, resource conflict, lessons learned, closure.
Top 100 Project & Programme Management Vocabulary: Working Meanings
| # | Word | Professional meaning |
|---|---|---|
| 1 | Project | A temporary effort undertaken to deliver a defined outcome. |
| 2 | Programme | A coordinated group of related projects and activities managed to achieve broader outcomes or benefits. |
| 3 | Objective | A defined result the project or programme aims to achieve. |
| 4 | Outcome | The resulting change produced by delivery. |
| 5 | Scope | The boundaries of work included. |
| 6 | Requirement | A condition the deliverable must satisfy. |
| 7 | Deliverable | A defined output to be produced. |
| 8 | Workstream | A distinct strand of work within a project or programme. |
| 9 | Milestone | A significant checkpoint in delivery. |
| 10 | Schedule | The planned timing of work. |
| 11 | Timeline | The sequence of dates and periods over which delivery occurs. |
| 12 | Budget | The planned financial allocation for delivery. |
| 13 | Resource | People, money, time or tools available to the project. |
| 14 | Capacity | The amount of work a team can absorb. |
| 15 | Dependency | A condition or task on which another part of the plan relies. |
| 16 | Assumption | A proposition accepted for planning without complete proof. |
| 17 | Constraint | A limit restricting the project or programme. |
| 18 | Baseline | The approved reference plan used to measure change or variance. |
| 19 | Critical path | The sequence of dependent activities determining the earliest possible completion date. |
| 20 | Sequencing | The deliberate ordering of work. |
| 21 | Estimate | An approximate judgement of effort, duration or cost. |
| 22 | Contingency | Reserved time, money or action for uncertainty. |
| 23 | Plan | A structured arrangement of actions for delivery. |
| 24 | Roadmap | A high-level sequence of intended development or change. |
| 25 | Charter | A document defining purpose, scope, authority and key governance of a project or programme. |
| 26 | Sponsor | The senior person accountable for organisational support and key decisions. |
| 27 | Owner | The person clearly charged with an outcome or decision. |
| 28 | Project manager | The person responsible for coordinating delivery of a project. |
| 29 | Programme manager | The person coordinating related projects and broader programme outcomes. |
| 30 | Steering committee | A senior governance group providing direction and decisions. |
| 31 | Governance | The structure of authority, oversight and accountability. |
| 32 | Authority | Legitimate power to decide or approve. |
| 33 | Mandate | The formal scope within which a project or leader may act. |
| 34 | Decision | A settled choice requiring action. |
| 35 | Approval | Formal acceptance by an authorised person or body. |
| 36 | Escalation | Raising an issue to a higher authority or urgency. |
| 37 | Stakeholder | A party affected by or influencing the project. |
| 38 | Stakeholder map | A structured view of stakeholder influence, interest and role. |
| 39 | Communication | Structured exchange of information needed for alignment and delivery. |
| 40 | Reporting | Provision of structured status, risk and decision information. |
| 41 | Cadence | The recurring rhythm of governance, reporting or review. |
| 42 | Status | The current condition of delivery against plan. |
| 43 | Issue | A current problem requiring action. |
| 44 | Risk | An uncertain event that may affect objectives. |
| 45 | Change control | A process for assessing and approving changes to scope, cost or schedule. |
| 46 | Dependency owner | The person accountable for managing a specified dependency. |
| 47 | Accountability | Obligation to answer for outcomes. |
| 48 | Responsibility | A duty to perform or coordinate work. |
| 49 | Assurance | Evidence-based confidence that governance and delivery are operating appropriately. |
| 50 | Review | Structured re-examination of progress, risks or decisions. |
| 51 | Execution | The carrying out of planned work. |
| 52 | Implementation | Putting a solution or change into operation. |
| 53 | Task | A defined unit of work. |
| 54 | Action | A specific next step assigned to an owner. |
| 55 | Progress | Movement toward completion or outcome. |
| 56 | Variance | A difference between actual and baseline performance. |
| 57 | Delay | A later-than-planned start or finish. |
| 58 | Slippage | Movement of planned delivery dates later over time. |
| 59 | Blocker | A condition preventing progress. |
| 60 | Bottleneck | A limiting point restricting overall flow. |
| 61 | Critical | Important enough that failure or delay materially affects objectives. |
| 62 | Priority | A task or outcome given precedence. |
| 63 | Quality | The degree to which deliverables meet requirements. |
| 64 | Acceptance | Formal agreement that deliverables meet agreed criteria. |
| 65 | Testing | Structured checking of deliverable behaviour or quality. |
| 66 | Handover | Transfer of deliverables, information and responsibility. |
| 67 | Transition | Movement from project delivery into new operational state. |
| 68 | Deployment | Release or placement of a solution into use. |
| 69 | Procurement | The structured acquisition of goods or services. |
| 70 | Vendor | An external provider of goods or services. |
| 71 | Contract | A formal agreement defining commercial obligations. |
| 72 | Change request | A formal proposal to alter scope, cost, schedule or requirements. |
| 73 | Mitigation | Action reducing likelihood or consequence of risk. |
| 74 | Corrective action | Action intended to repair an existing delivery problem. |
| 75 | Completion | The point at which defined project work is finished. |
| 76 | Benefit | A favourable outcome created by the programme or project. |
| 77 | Benefits realisation | The process of achieving and measuring intended benefits after delivery. |
| 78 | Business case | A structured justification for investment or action. |
| 79 | Strategic alignment | Consistency between the programme and organisational priorities. |
| 80 | Interdependency | A relationship in which multiple projects or outcomes rely on one another. |
| 81 | Portfolio | A collection of projects or programmes managed together for strategic value. |
| 82 | Transformation | A substantial change in organisation, capability or operating model. |
| 83 | Capability | The ability to perform a required function. |
| 84 | Adoption | Actual use of the new process, system or behaviour. |
| 85 | Target state | The desired future operating condition. |
| 86 | Transition state | An intermediate operating condition between current and target state. |
| 87 | Outcome measure | A metric showing whether intended change occurred. |
| 88 | KPI | A key performance indicator linked to an important objective. |
| 89 | Value | The benefit created relative to cost and alternatives. |
| 90 | Impact | The significance of the resulting change. |
| 91 | Sustainment | Maintenance of new capability or benefit after implementation. |
| 92 | Operating model | The structure of roles, processes, governance and systems through which work is done. |
| 93 | Readiness | The degree to which the organisation is prepared for transition. |
| 94 | Change fatigue | Reduced capacity or engagement caused by repeated or overlapping change. |
| 95 | Prioritisation | Ordering projects or actions by strategic importance. |
| 96 | Resource conflict | Competition among projects for the same scarce capability or capacity. |
| 97 | Lessons learned | Knowledge captured for future delivery. |
| 98 | Closure | The formal end of a project or programme phase. |
| 99 | Realisation owner | The person responsible for ensuring an intended benefit is achieved. |
| 100 | Programme coherence | The degree to which related projects collectively support the intended strategic outcome. |
Project Completion Is Not Benefit Realisation
A system can be delivered on time and still fail to create the intended business outcome. Projects produce deliverables; programmes often exist because benefits require coordinated adoption and operational change after the deliverable is complete.
Scenario: Green Status, Late Reality
If every workstream reports green until the deadline slips, the governance system is not surfacing uncertainty early enough. Examine milestone evidence, dependency ownership, estimate confidence and whether status culture punishes bad news.
Seven-Day Project & Programme Plan
| Day | Practice |
|---|---|
| 1 | Separate objective, outcome, deliverable and benefit. |
| 2 | Map milestones, dependencies and critical path. |
| 3 | Audit governance, ownership and escalation routes. |
| 4 | Practise risk, issue and change-request distinctions. |
| 5 | Map adoption and benefits beyond project completion. |
| 6 | Recall 75+ terms by delivery function. |
| 7 | Write a one-page programme review connecting delivery to strategic benefit. |
Continue the Profession Wing
- Operations & Supply Chain
- Sales & Business Development
- Public Service & Policy Professionals
- Organisational Change
Conclusion
Project and programme vocabulary helps adults distinguish delivery from benefit, risk from issue, ownership from activity and completion from adoption. The language becomes most valuable when it reveals what must happen after the project team declares success.