EXIN Dynamic Project Management Method Foundation key terms

A concrete, agreed outcome that a project must deliver, describing the result, its scope and the conditions under which it counts as achieved. It steers decisions throughout the project.

The tangible or intangible product, service or change the project hands over. Results are what remain after the project ends and are distinct from the temporary effort that produced them.

The agreed boundary of what the project will and will not deliver, including the results, the work needed to produce them and the exclusions recorded at the start.

The explicit line drawn between what falls inside the project and what does not. Stating exclusions up front prevents expectation gaps and later disputes about deliverables.

The reasoning that justifies the project: the problem or opportunity, expected benefits, estimated costs and the risks accepted. It is revisited when major changes occur.

The formal starting signal that authorizes a project, names its sponsor and describes the intended result at a high level. It precedes detailed planning and organization design.

The environment surrounding a project: the organization, its stakeholders, culture, market, regulations and dependencies. Context shapes which approach and governance fit the work.

The person who owns the business case, secures resources and has authority to approve or stop the project. The sponsor shields the team and resolves issues beyond the project manager's mandate.

Any person or group with an interest in, influence over, or dependence on the project and its results. Stakeholders are identified, analyzed and engaged throughout the lifecycle.

The structured mapping of stakeholders by interest, influence and attitude toward the project, used to decide who to involve, how often and through which channel.

Adapting processes, documents and controls to the size, risk and context of a specific project instead of applying a fixed template uniformly. Tailoring decisions are recorded and justified.

A structured review of external and internal factors - market, regulation, technology, culture, dependencies - that could affect the project, used to choose approach and controls.

A durable guideline that shapes behavior and decisions across projects, independent of a specific procedure. Principles guide judgment when no rule prescribes the answer.

The underlying attitude and set of values with which people approach project work, such as openness to change and shared responsibility. Mindset determines how principles are lived in practice.

The ongoing habit of inspecting how work is done and adjusting it in small, regular steps. It applies to products, processes and team collaboration alike.

The practice of letting the people who do the work decide how to divide and sequence it, within agreed boundaries. It increases ownership and shortens decision paths.

Giving team members real authority and information to make decisions about their work, together with accountability for the outcome. It requires clear boundaries and trust.

The ability to respond quickly and effectively to change while still delivering value, by working in short cycles, keeping options open and seeking feedback early.

A fixed, repeating time box in which a defined slice of work is planned, executed and reviewed. Each iteration produces a usable increment or verifiable progress.

A completed, potentially usable addition to the project result produced within one iteration. Increments make progress visible and allow early validation by stakeholders.

A fixed maximum duration for an activity or meeting that is not extended; scope is adjusted instead. Timeboxes create rhythm and force prioritization.

A recurring cycle in which results are shown to stakeholders and their response is fed back into planning. Short loops reduce the cost of correcting a wrong direction.

Ranking work items by value, risk or urgency so that limited capacity is spent on what matters most first. It is revisited as insight and context change.

The agreed allocation of roles, responsibilities and decision rights for a project, including the sponsor, project manager, team and any steering or reference groups.

A defined set of tasks, authorities and expected behaviors assigned to a person or group in the project. One person may hold several roles if this is explicit.

The person responsible for planning, coordinating and reporting the project day to day, managing issues and risks, and keeping delivery aligned with the agreed goal.

A small decision-making body, typically chaired by the sponsor, that approves plans and major changes, resolves escalated issues and monitors progress against the business case.

A table that maps tasks or deliverables to roles and states who is responsible, who approves, who is consulted and who is informed, preventing gaps and duplication.

Transferring a defined task together with the authority and resources needed to complete it, while the delegating person keeps accountability for the outcome.

A documented forecast of what will be delivered, by whom, when and with which resources, plus how progress will be measured. It is updated as facts change.

The hierarchical decomposition of the project result and work into smaller, manageable and estimable pieces, ending at a level that can be planned and assigned.

A significant, dated point in the plan marking the completion of a result or a key decision. Milestones have zero duration and are used for steering and reporting.

Planning near-term work in detail while leaving later work at a coarse level until more information is available. Detail is added as each horizon approaches.

Judging the effort, duration or cost needed to produce a result, using techniques such as analogy, expert judgment or decomposition, and stating the uncertainty involved.

The degree to which the project result and the way it is produced meet agreed requirements and stakeholder expectations. Quality is planned, not inspected in at the end.

The specific, checkable conditions a result must satisfy to be accepted by the customer or sponsor. They are agreed before work starts and used to verify delivery.

A shared checklist stating what must be true for a piece of work to count as complete, covering content, quality checks and documentation. It prevents partial work being called finished.

A planned examination of a deliverable against its agreed criteria, performed by peers, experts or stakeholders, producing findings that are recorded and followed up.

A problem or question that has already occurred and needs a decision or action to keep the project moving. Issues differ from risks because their impact is present, not potential.

A register listing open issues with owner, date raised, agreed action, priority and status, reviewed regularly so nothing is silently dropped.

Referring a decision or problem to a higher authority when it exceeds the project manager's mandate or agreed tolerances, with a clear request and supporting facts.

An uncertain event or condition that, if it occurs, would affect the project's goals positively or negatively. Each risk is described by cause, event and effect.

A living record of identified risks with their cause, potential effect, likelihood, impact, owner and planned response, reviewed at fixed intervals.

The two dimensions used to rate a risk: how likely it is to occur and how severe its effect would be. Their combination sets priority for response.

The chosen way of dealing with a risk, such as avoiding, reducing, transferring or accepting it, together with an owner and any trigger that activates the action.

A defined, repeatable way of working within the method that describes which activities produce which results, with entry and exit conditions and assigned roles.

A distinct period of the project with its own focus and results, ending at a decision point. Phases give structure to longer projects while allowing iterative work inside them.

A planned decision point between phases where results are reviewed and the project board decides to continue, adjust or stop, based on the business case and current risk.

A short, regular team meeting that examines how collaboration and process worked in the last period and agrees concrete improvements for the next one.

An insight captured from experience about what worked or did not, recorded with context and shared so that later work benefits from it.

The agreed amount by which a plan may deviate - in time, cost or scope - before the project manager must escalate to the board for a decision.

An ordered list of work items still to be done, kept visible and reordered as priorities change. The most valuable items are pulled into the next iteration.

A prioritization scheme that sorts requirements into must-have, should-have, could-have and will-not-have for this delivery, making trade-offs explicit when time is fixed.

A session in which the team shows a working increment to stakeholders to gather feedback and confirm acceptance, rather than relying on written status alone.

An agreement on who needs which information, in what form and how often, covering status, decisions and escalations. It is adjusted as stakeholders and phases change.

A periodic summary comparing achieved results, milestones and resource use against the plan, highlighting deviations, issues and risks that need attention.