Logo

DECISION LOG

Project: National Stadium & Digital Ticketing Platform
Prepared by: Alex – Project Manager
Version: 1.0
Date: September 2028

Purpose

The Decision Log ensures that important project decisions are documented, traceable, and transparent to stakeholders.

It supports governance oversight and allows future teams to understand the context behind critical project actions.

Decision Log Entries

Decision ID

Date

Decision Description

Decision Authority

Rationale

Impact

DL-01

10 Sept 2025

Initiate Business Case development for national stadium project

Ministry Steering Committee

Tournament hosting opportunity created strategic need

Triggered project evaluation

DL-02

25 Nov 2025

Approve Project Charter and formally authorize project

Ministry Steering Committee

Business case demonstrated economic and strategic value

Project officially initiated

DL-03

05 Jan 2026

Adopt hybrid project delivery approach

Project Manager with Sponsor approval

Construction predictable; ticketing platform requires agile development

Established hybrid governance structure

DL-04

18 Mar 2026

Approve scope baseline and WBS structure

Steering Committee

Scope definition and decomposition completed

Enabled cost and schedule estimation

DL-05

22 May 2026

Approve stadium construction vendor contract

Procurement Authority

Competitive bid evaluation completed

Construction execution authorized

DL-06

30 Jun 2026

Approve ticketing platform vendor contract

Procurement Authority

Vendor demonstrated strongest technical capability

Agile development began

DL-07

14 Aug 2028

Escalate design change request regarding VIP seating

Project Manager to Steering Committee

Design authority rests with engineering contractor

Triggered formal change request review

DL-08

02 Sept 2028

Integrate gate testing sprint with construction milestone

Project Manager

Integration between digital platform and stadium infrastructure required

Adjusted sprint planning

DL-09

10 Apr 2029

Approve contingency reserve usage for steel price increase

Steering Committee

Commodity price volatility risk materialized

Maintained construction progress

DL-10

15 Mar 2030

Approve operational handover plan

Steering Committee

Construction and platform integration testing completed

Enabled transition to operations

Decision Governance

The following authorities may make decisions recorded in the log:

Decision Type

Authority

Strategic decisions

Ministry Steering Committee

Budget and scope changes

Change Control Board

Operational project decisions

Project Manager

Procurement contract decisions

Procurement Authority

Usage

The Decision Log is updated when:

  • major governance decisions occur
  • baseline approvals are granted
  • significant project trade-offs are made
  • escalation outcomes are determined

The log is reviewed during governance meetings to ensure alignment and transparency.

Scroll to Top

Cost Forecast

A prediction of the future cost performance of the project based on current cost performance and trends.

Monitor and Control Costs

The process of tracking, reviewing, and regulating project expenditures to ensure the project stays within the approved budget.

External Event

A factor outside the project team’s control that can influence project performance.

Schedule Forecast

A prediction of the future status or completion date of the project schedule based on current performance and trends.

Corrective Action

An action taken to bring project performance back in line with the project management plan.

Variance

The difference between the planned value and the actual performance of a project element such as cost or schedule.

Change Log

A project document used to record and track all change requests, including their status, decisions, and implementation details throughout the project. Click to see exemple.

Schedule Model

A representation of the project schedule that includes activities, durations, dependencies, and constraints used to calculate the project timeline.

Scope Creep

The uncontrolled expansion of project scope without formal approval or corresponding adjustments to schedule, cost, and resources.

Decision Log

A project document used to record important decisions made during the project, including the rationale, date, and responsible parties. Click to see exemple.

Risk Appetite

The level of risk an organization is willing to accept in pursuit of objectives.

Fast-Tracking

A schedule compression technique in which activities that were originally planned to be performed sequentially are performed in parallel to shorten the project duration.

Crashing

A schedule compression technique that shortens the project schedule by adding additional resources to critical path activities.

Product Backlog

A prioritized list of features, enhancements, fixes, and requirements that defines the work needed to develop and improve a product. Click to see exemple.

Stakeholder Transparency

The practice of openly sharing project information, progress, decisions, and issues with stakeholders to maintain trust and informed engagement.

Velocity Chart

A visual chart used in agile projects to track the amount of work completed by the team in each sprint, helping forecast future sprint capacity.

Sprint Cancellation

Formal termination of a sprint when its goal becomes invalid.

Technical Debt

The implied cost of additional rework caused by choosing an easy solution now instead of a correct one.

Definition of Done

A shared agreement within the team that defines the criteria a product increment must meet to be considered complete and ready for delivery.

Make-or-Buy Analysis

A decision-making technique used to determine whether project work should be performed internally or purchased from external suppliers.

Control Procurements

The process of managing procurement relationships, monitoring contract performance, and making changes and corrections as appropriate.

Claim

A formal request by a party to a contract seeking compensation, time extension, or other relief due to changes, disputes, or unmet contractual obligations.

Scope Management

The processes required to ensure that the project includes all the work necessary—and only the work necessary—to complete the project successfully.

Impact Assessment

The evaluation of the potential effects of a proposed change or risk on project objectives such as scope, schedule, cost, quality, and resources.

Change

A modification to any project element such as scope, schedule, cost, quality, resources, or project plans.

Team Working Agreement

Mutually agreed guidelines that define how team members collaborate, communicate, and make decisions while working on the project.

Manage Team

The process of tracking team member performance, providing feedback, resolving issues, and managing changes to optimize performance.

Develop Team

The process of improving competencies, interaction, and the overall team environment to enhance project performance.

Issue Log

A project document used to record and track issues that arise during the project, including their status, owners, and resolution actions click to see exemple.

Live Increment

A usable product version made available to real users under controlled conditions.

Dependency Log

A project document used to record, monitor, and track dependencies that may affect project activities or deliverables.

Sprint Goal

A short statement that describes the objective the team aims to achieve during a sprint.

Sprint Backlog

A list of product backlog items selected for a sprint, along with the tasks needed to deliver the sprint goal click to see exemple.

Dependency Mapping

Identifying and documenting relationships between activities.

External Dependency

A relationship in which a project activity relies on work, resources, or deliverables provided by an entity outside the project team.

Sprint Planning

A meeting in agile development where the team defines the work to be completed during the upcoming sprint and creates a plan for delivering the selected backlog items.

Hybrid Planning

A planning approach that combines predictive planning for well-defined work with adaptive planning for areas where requirements may evolve.

Story Card

Physical or digital cards used in agile projects to represent user stories, typically containing a brief description of a feature or requirement from the user’s perspective.

Increment

A usable and potentially releasable portion of the product that adds value and builds upon previously completed work.

Zero-Value Pilot

A small test implementation of a solution conducted with minimal cost or risk to evaluate feasibility, validate assumptions, or gather feedback before full deployment.

Direct and Manage Project Work

The process of leading and performing the work defined in the project management plan and implementing approved changes.

Acquire Resources

The process of obtaining team members, facilities, equipment, materials, and other resources necessary to complete project work.

Agreement

A legally binding document defining procurement terms and conditions.

Selected Seller

A vendor or supplier chosen through the procurement process to provide goods or services for the project.

Source Selection Analyses

The process of evaluating seller proposals using predefined criteria to determine the most suitable supplier for the project.

Proposal Evaluation Techniques

Methods used to assess and compare seller proposals against predefined source selection criteria to identify the most suitable vendor.

Bidder Conference

A meeting with prospective sellers to clarify requirements and respond to questions.

Conduct Procurements

The process of obtaining seller responses, selecting a seller, and awarding a contract.

Acceptance Criteria

The defined conditions that a deliverable must meet to be accepted by the customer or stakeholders.

Develop Project Management Plan

The process of defining, preparing, and coordinating all plan components and consolidating them into a comprehensive project management plan.

Integration

The coordination of all project management processes and activities to ensure that project elements work together effectively to achieve project objectives.

Change authority

The individual or group with the authority to approve or reject change requests affecting the project baselines or deliverables.

Change Management Plan

A component of the project management plan that defines how changes to the project baselines, deliverables, and project documents will be requested, evaluated, approved, and implemented click to see exemple.

Change Control Procedures

Documented steps defining how changes will be submitted, evaluated, approved, or rejected.

Perform Integrated Change Control

The process of reviewing change requests, approving or rejecting changes, and managing modifications to project deliverables, documents, and the project management plan.

Procurement Documents

Documents used to request proposals, bids, or quotations from potential sellers for goods or services required by the project.

Statement of Work

A detailed description of the products, services, or results to be delivered by a seller under a contract click to see exemple.

Source Selection Criteria

The set of standards or factors used to evaluate and choose the most suitable seller or supplier during the procurement process click to see exemple.

Risk Allocation

The process of assigning responsibility for managing specific risks to the party best able to control or mitigate them.

Time and Materials

A contract type that pays the seller for actual labor hours and materials used.

Firm-Fixed-Price

A contract type in which the seller agrees to provide the specified product or service for a fixed total price, regardless of the seller’s actual costs.

Plan Procurement Management

The process of documenting project procurement decisions, specifying the approach for acquiring goods and services from outside the project team.

Plan Risk Responses

The process of developing strategies and actions to address identified project risks in order to reduce threats or enhance opportunities.

Perform Qualitative Risk Analysis

The process of prioritizing identified risks by assessing their probability of occurrence and potential impact on project objectives.

Brainstorming

A group creativity technique used to generate a large number of ideas or potential solutions for a problem without immediate judgment or evaluation.

Risk Management Plan

A component of the project management plan that describes how risk management activities will be structured and performed for the project click to see exemple.

Identify Risks

The process of determining which risks may affect the project and documenting their characteristics.

Plan Risk Management

The process of defining how to conduct risk management activities for a project.

Workshop

A structured group meeting where participants collaborate to discuss issues, generate ideas, or develop solutions related to the project.

Quality Metrics

Specific measurements used to assess whether project deliverables or processes meet defined quality standards.

Benchmarking

A technique used to compare project practices, processes, or performance against industry standards or similar projects to identify opportunities for improvement.

Stakeholder Expectations

The needs, requirements, and desired outcomes that stakeholders anticipate from the project and its deliverables.

Contractual Standards

Quality or performance requirements defined within a contract that the project or its deliverables must meet.

Regulatory Standards

Official rules, guidelines, or technical requirements established by regulatory authorities that a project or product must follow to ensure legal and industry compliance.

Plan Quality Management

The process of identifying quality requirements and standards for the project and its deliverables and documenting how the project will demonstrate compliance.

Definition Gap

A situation in which project requirements, scope, or expectations are not clearly defined or understood by stakeholders, leading to misunderstandings or misalignment.

Project Budget

The total approved funding required to complete the project work.

Determine Budget

The process of aggregating the estimated costs of individual activities or work packages to establish an approved cost baseline.

Data Analysis

A technique used to examine and evaluate data in order to support project planning, decision-making, and problem solving.

Estimate Costs

The process of developing an approximation of the monetary resources needed to complete project activities.

Activity

A distinct, scheduled piece of work performed during a project to produce a deliverable or contribute to a work package.

Work Package

A deliverable or project work component at the lowest level of the Work Breakdown Structure (WBS) that can be estimated, scheduled, and managed.

Sequence Activities

The process of identifying and documenting the relationships among project activities to determine the order in which work will be performed.

Schedule Baseline

The approved version of the project schedule used as a basis for comparison to measure and control schedule performance click to see exemple.

Project Schedule

A schedule model that presents planned start and finish dates for project activities, milestones, and deliverables.

Develop Schedule

The process of analyzing activity sequences, durations, resource requirements, and constraints to create the project schedule model.

Release Map

A planning artifact that outlines the sequence and timing of product releases, showing how features or increments will be delivered over multiple iterations or sprints.

Estimate Activity Durations

The process of approximating the number of work periods required to complete individual schedule activities with the estimated resources.

Velocity

An agile metric that measures the amount of work a team completes during a sprint, typically expressed in story points or completed backlog items.

Monte Carlo Simulation

A quantitative risk analysis technique that uses repeated random sampling and probability distributions to simulate many possible project outcomes and estimate the likelihood of meeting project objectives such as schedule or cost targets.

Affinity Estimating

A collaborative estimation technique in which team members group similar work items or user stories and estimate them collectively based on relative size or complexity.

Cross-Domain Dependency

A relationship in which work, decisions, or deliverables in one project domain or functional area depend on inputs or outcomes from another domain.

Schedule Data

Supporting information about schedule activities that describes the details of the schedule model, such as durations, dependencies, constraints, calendars, and assumptions.

Product Owner

A role in agile teams responsible for defining and prioritizing the product backlog to maximize the value delivered by the team.

Control Schedule

The process of monitoring the status of project activities, updating the project schedule, and managing changes to the schedule baseline to ensure the project is completed on time.

Sprint

A short, time-boxed iteration in agile development during which a team completes a set of planned work to deliver a usable product increment.

Hybrid Life Cycle

A project life cycle that combines predictive (plan-driven) and adaptive (agile) approaches, allowing some parts of the project to follow a structured plan while others are developed iteratively.

Activity List

A comprehensive list of all schedule activities required to complete the project work packages click to see exemple.

Schedule Logic

The defined sequence and dependency relationships between project activities that determine the order in which work is performed.

Initial Project Estimates

Preliminary approximations of project costs, durations, or resources developed early in the project to support planning and decision-making.

Decision Making

A technique used to evaluate alternatives and select the best course of action to achieve project objectives.

Three-Point Estimating

An estimating technique that improves accuracy by calculating an estimate based on three values: optimistic, most likely, and pessimistic estimates.

Bottom-Up Estimating

An estimating technique in which the cost or duration of individual activities or work packages is estimated first and then aggregated to determine the total project estimate.

Parametric Estimating

An estimating technique that uses statistical relationships between historical data and project variables to calculate cost or duration estimates.

Analogous Estimating

An estimating technique that uses historical data from similar past projects or activities to estimate the duration or cost of the current project.

Scope Baseline

The approved version of the project scope statement, Work Breakdown Structure (WBS), and WBS dictionary used as a basis for comparison and scope control.

WBS Dictionary

A document that provides detailed descriptions of each work package in the Work Breakdown Structure, including scope, deliverables, responsibilities, and other relevant information click to see exemple.

Create WBS

The process of subdividing project deliverables and project work into smaller, more manageable components called work packages.

Define Scope

The process of developing a detailed description of the project and product scope based on the approved requirements.

Expert Judgment

The use of knowledge, experience, and specialized expertise from individuals or groups to support project decision-making and problem solving.

Prototype

A preliminary version of a product or component used to visualize, test, and refine requirements before the final solution is developed.

Observation

A data-gathering technique in which the project manager or analyst watches users perform their work to understand processes, behaviors, and requirements in a real environment.

Affinity Diagrams

A technique used to organize a large number of ideas or requirements into groups based on their natural relationships or similarities.

Mind Mapping

A visual technique used to organize ideas and information around a central concept, showing relationships between requirements, concepts, or project elements.

Facilitation

A technique used to guide group discussions and activities to encourage participation, improve collaboration, and help stakeholders reach agreements or decisions.

Facilitated Workshop

A structured meeting led by a neutral facilitator where stakeholders collaborate to define requirements, resolve issues, and reach consensus on project objectives.

Document Analysis

A technique used to review existing documents and records to identify relevant information, requirements, or insights for the project.

Survey

A data-gathering technique that collects information, opinions, or feedback from a group of respondents through structured questions.

Questionnaire

A data-gathering technique that uses a set of written questions distributed to stakeholders to collect information efficiently from a large group.

Focus Groups

A data-gathering technique that brings together selected stakeholders or experts to discuss project requirements, expectations, or issues and provide feedback.

Interview

A data-gathering technique in which information is obtained by directly asking questions to stakeholders or subject matter experts.

Data Gathering

A technique used to collect information and insights from stakeholders or other sources to support project decision-making and planning.

Collect Requirements

The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.

Cost Management Plan

A component of the project management plan that describes how project costs will be estimated, budgeted, monitored, and controlled click to see exemple. 

Plan Cost Management

The process of defining how project costs will be estimated, budgeted, managed, monitored, and controlled throughout the project.

Deliverable

A unique and verifiable product, service, or result that must be produced to complete a project phase or the project itself.

Plan Scope Management

The process of defining how the project scope will be defined, validated, and controlled throughout the project.

Predictability

The consistency of behavior and decision-making over time.

Trust

The belief that others will act competently, reliably, and with positive intent.

Team Dynamics Risk

The possibility that interpersonal conflicts, poor collaboration, or ineffective communication within the team may negatively impact project performance or outcomes.

Team Ground Rules

Agreed-upon guidelines that define acceptable behaviors, communication practices, and expectations for how team members work and interact during the project.

Inclusion

The practice of ensuring individuals feel respected, valued, and able to contribute fully.

Cultural Intelligence

The ability to understand, adapt to, and work effectively with people from different cultural backgrounds.

Low-Context Communication

A communication style in which information is conveyed primarily through clear, direct, and explicit verbal or written messages, with little reliance on context or nonverbal cues.

High-Context Communication

A communication style in which much of the meaning is conveyed through context, relationships, nonverbal cues, and shared understanding rather than explicit words.

Cost of Escalation

The additional time, effort, resources, or financial impact incurred when an issue must be raised to higher levels of authority for resolution.

Communication Management Approach

A structured plan that defines how project information will be generated, collected, distributed, stored, and monitored among stakeholders.

Emotional Awareness

The ability to recognize and understand one’s own emotions and the emotions of others, and how they influence behavior and interactions.

Empathy

The ability to understand and share the feelings, perspectives, and experiences of others.

Information Overload

The situation in which a person receives more information than they can effectively process, potentially reducing understanding and decision quality.

Influence

The ability to affect the decisions, actions, or opinions of others in order to support project objectives.

Stakeholder Engagement Strategy

A planned approach for communicating and working with stakeholders to address their needs, manage expectations, and encourage their support throughout the project.

Active Listening

The practice of fully concentrating on, understanding, responding to, and remembering what another person is saying during communication.

Communication Risk

The possibility that information may be misunderstood, delayed, or not effectively transmitted among stakeholders, potentially impacting project performance or decisions.

Cultural Differences

Variations in values, beliefs, behaviors, communication styles, and social norms among individuals or groups from different cultural backgrounds that can influence interactions within a project.

Tools & Techniques

Methods, processes, or instruments used to perform a project management process and produce its outputs.

Interactive Communication

A communication method that involves real-time exchange of information between two or more parties, allowing immediate feedback and clarification.

Pull Communication

A communication method in which information is made available for stakeholders to access at their convenience, such as through websites, databases, or shared repositories.

Push Communication

A communication method in which information is sent directly to specific recipients to ensure they receive the message, such as emails, reports, or memos.

Communication Method

The different ways information is exchanged among project stakeholders, such as interactive, push, or pull communication.

Noise

Anything that interferes with the effective exchange or understanding of information.

Communication

The exchange of information in a manner that is understood by all parties.

Virtual Team

A group of project team members who work together from different geographic locations and communicate primarily through digital technologies rather than face-to-face interaction.

Conflict

A disagreement arising from differing needs, opinions, or priorities.

Interface Risk

The risk arising from dependencies and interactions between different components or teams.

Collaborating

Working together to find a solution that satisfies all parties and addresses the root cause.

Compromising

Each party gives up something to reach a temporary or partial solution.

Accommodating

Emphasizing areas of agreement and giving in to the other party to maintain harmony.

Forcing

Imposing a solution using authority or power, usually when a quick decision is required.

Conflict Management Techniques

Methods used by project managers and team members to address and resolve disagreements in a constructive manner to maintain collaboration and achieve project objectives.

Avoiding

A conflict resolution technique in which a person withdraws from or postpones addressing a conflict, typically used when the issue is minor or when more information or time is needed before resolving it.

Relationship Conflict

Personal or emotional disagreement between individuals.

Task Conflict

Disagreement about the content of the work, priorities, or technical approaches.

Storming

A stage of team development in which team members begin expressing differing opinions, leading to conflicts or disagreements as roles, responsibilities, and working styles are clarified.

Cross-Functional Team

A group of team members from different functional areas or disciplines who collaborate to achieve a common project objective.

Emotional Intelligence

The ability to recognize, understand, and manage one’s own emotions and the emotions of others in order to communicate effectively, build relationships, and make informed decisions.

Positive Reinforcement

The act of encouraging desired behavior by acknowledging and rewarding it.

Self-Determination Theory

A motivation theory developed by Edward Deci and Richard Ryan that explains human motivation as driven by the psychological needs for autonomy, competence, and relatedness, which foster intrinsic motivation and engagement when fulfilled.

Herzberg’s Two-Factor Theory

A motivation theory developed by Frederick Herzberg that states job satisfaction and dissatisfaction are influenced by two different sets of factors: motivators (such as achievement, recognition, and responsibility) that increase satisfaction, and hygiene factors (such as salary, policies, and working conditions) that prevent dissatisfaction but do not necessarily motivate employees.

Motivation

The internal or external factors that stimulate desire and energy in individuals to be continually interested and committed to a role or task.

Interpersonal & Team Skills

Abilities used by project managers and team members to communicate, collaborate, influence, resolve conflicts, and build effective working relationships within the project team and with stakeholders.

Drexler–Sibbet Team Performance Model

A team development framework created by Allan Drexler and David Sibbet that describes how teams progress through stages of orientation, trust building, goal clarification, commitment, implementation, and high performance to achieve effective collaboration and project success.

McGregor’s Theory X and Theory Y

A management theory developed by Douglas McGregor that describes two contrasting assumptions about worker motivation. Theory X assumes employees are naturally lazy, avoid responsibility, and require close supervision, while Theory Y assumes employees are self-motivated, responsible, and capable of contributing creatively when properly supported.

Maslow’s Hierarchy of Needs

A motivation theory developed by Abraham Maslow that explains human motivation as a progression of needs arranged in levels—from basic physiological needs and safety to social belonging, esteem, and ultimately self-actualization, where individuals seek personal growth and fulfillment.

Situational Leadership Model (Hersey–Blanchard)

A leadership theory developed by Paul Hersey and Ken Blanchard that suggests effective leaders adjust their leadership style based on the competence and commitment of their team members, using different combinations of directing, coaching, supporting, and delegating to match the needs of the situation.

Forming

The initial stage of team development in which team members meet, learn about the project, understand their roles and responsibilities, and begin establishing relationships while relying on guidance from the project manager.

Tuckman’s Team Development Model

A framework developed by Bruce Tuckman that explains how project teams evolve through a series of stages as members build relationships, resolve conflicts, establish norms, and become effective collaborators. The model identifies five stages—Forming, Storming, Norming, Performing, and Adjourning—each representing different levels of team maturity, communication, trust, and productivity during the lifecycle of a team.

Responsibility Assignment Matrix

A chart that maps project activities or deliverables to the team members responsible for performing or supporting the work.

Commitment

The level of dedication a resource has to project objectives.

Resource Assignment

The process of allocating specific resources, such as people, equipment, or materials, to project activities or tasks.

Core Team

A small group of key project members responsible for performing the main project work and supporting the project manager in delivering the project objectives.

Baseline

An approved version of a work product that can be changed only through formal change control and is used as a basis for comparison.

Stakeholder Engagement

The process of communicating and working with stakeholders to address their needs, expectations, and concerns throughout the project.

Stakeholder Analysis

The process of identifying project stakeholders and assessing their interests, influence, and impact on the project.

Escalation

The process of raising an issue or decision to a higher level of authority when it cannot be resolved at the current level.

Stakeholder Conflict

A situation in which stakeholders have opposing interests, expectations, or perceptions regarding the project.

Identify Stakeholders

The process of determining which individuals or groups may affect or be affected by the project.

External Stakeholder

Individuals or organizations outside the organization.

Internal Stakeholder

Individuals or groups within the performing organization.

Interest

The degree to which a stakeholder is affected by or cares about the project outcomes.

Stakeholder Register

A document that identifies project stakeholders and documents their interests, influence, and impact on the project click to see exemple.

Risk Identification

The process of recognizing and recording potential risks tthat may affect the project and documenting their characteristics early in the project life cycle.

Governance Risk

The risk that governance structures, approval paths, or authority limits may delay or constrain project decisions.

Procurement Risk

The risk that vendor selection, contract execution, or supplier performance may negatively affect the project.

Schedule Risk

The possibility that project activities may take longer than planned, causing delays to the project schedule.

Compliance

The act of adhering to laws, regulations, standards, policies, or contractual requirements applicable to a project.

Power

The ability of an individual to influence the behavior, decisions, or actions of others.

Project Approach

A high-level strategy that defines how the project will be executed, including the selected development method, processes, and techniques.

Analysis Paralysis

The state of overanalyzing a situation to the point that progress is delayed or prevented.

Sufficiency

The state in which a document contains enough information to fulfill its purpose and allow the project to proceed.

Risk Responses

Planned actions developed to address identified project risks in order to reduce threats or enhance opportunities.

Cost estimates

Quantitative assessments of the likely costs required to complete project activities or deliverables click to see exemple.

Requirement

A documented condition or capability that a product, service, or result must meet to satisfy stakeholder needs or expectations.

Planning

A group of processes performed to establish the scope, schedule and costs of the project, refine objectives, and define the course of action required to achieve the project objectives.

Progressive Elaboration

The process of refining details as more information becomes available.

Project Management Plan

A formal, approved document that describes how the project will be executed, monitored, and controlled click to see exemple.

Schedule

A timetable that defines when project activities and milestones are planned to start and finish.

Assumption

A factor believed to be true for planning purposes without definitive proof.

Input

An approved deliverable, resource, document, or information produced by previous projects or processes and used in the current project.

Phase Review

A formal evaluation at the end of a project phase to assess performance and determine whether the project should proceed to the next phase ot not.

Approval workflow

A defined sequence of review and authorization steps that specifies who must evaluate, approve, or reject project documents or decisions before they can be implemented, in accordance with organizational governance.

Regulatory requirement

Laws, regulations, or government rules that a project must comply with during its execution.

Approval gate

Formal decision points in a project where authorized stakeholders review progress and determine whether the project should proceed to the next phase.

Process

A set of interrelated activities performed in a specific order to achieve a defined objective or produce a specific output.

escalation path

A defined process that specifies how and to whom issues or decisions are elevated when they cannot be resolved at the current level of authority.

internal policies

Formal rules, guidelines, and procedures established within an organization that govern how work and activities must be performed.

strategic business need

A documented business justification explaining why an organization initiates a project in order to achieve its strategic objectives or improve business value.

Constraint

Limiting factor that restrict a project’s options or influence how the project work can be performed, such as fixed budget, schedule deadlines, regulatory requirements, available resources, or predefined scope conditions.

Scope

The sum of the products, services, and results to be provided by a project, including the work required to deliver those outputs and the boundaries that define what is included and excluded from the project.

Authority Limits

The boundaries within which the project manager can make decisions without escalation.

Risk Management

The systematic process of identifying, analyzing, and responding to project risks.

Governance

The framework of rules, roles, responsibilities, decision-making authority, and oversight mechanisms that ensure projects align with organizational objectives, comply with policies and regulations, and are controlled throughout their life cycle.

Authorization

The formal approval granting the project manager or organization the right to initiate and carry out project work, including the use of organizational resources and decision-making authority.

Benefits

Measurable improvements resulting from outcomes perceived as advantageous to stakeholders.

Vendor

External organization contracted to provide goods or services.

Business Need

A problem or opportunity that justifies initiating a project or program.

Hybrid Project

A project that combines predictive and agile delivery approaches within one initiative.

Agile Approach

A delivery approach that emphasizes iterative development, customer feedback, and adaptability.

Predictive Approach

A delivery approach where scope, schedule, and cost are defined upfront and managed through formal control processe.

Selection

The act of designating or nominating an individual to serve as project manager, identifying responsibility for leadership of the project, but not necessarily granting formal authority until the project is officially authorized.

Project Sponsor

The individual or group that provides resources and support for the project and is accountable for its success

International Football Tournament

A large-scale global sporting event involving multiple national teams, fixed opening dates, and significant public visibility.

Close Project or Phase

The process of finalizing all activities and formally completing the project.

Lessons Learned Register

A document capturing knowledge gained during the project (click to see exemple).

Operational Readiness

The degree to which operations can support and sustain the delivered product.

Handover to Operations

The formal transfer of ownership, responsibility, and risk from the project to operations.

Integrated Change Control

The process of reviewing and approving changes across the project.

Change Request

A formal proposal to modify any document, deliverable, or baseline within the project, requiring evaluation and approval through the integrated change control process. click to see exemple.

Issue

A current condition or situation that is already affecting the project objectives and requires resolution.

Work Performance Report

A document summarizing performance information for stakeholders (click to see exemple).

Work Performance Information

The result of analyzing work performance data to provide meaningful insights regarding project performance, trends, and potential issues. click to see exemple.

Work Performance Data

Raw observations and measurements collected during project execution click to see exemple.

Liquidated Damages

Pre-agreed penalties for failure to meet contractual obligations.

Compensable Delay

A delay that entitles the seller to additional time and/or money.

Excusable Delay

A delay allowed without penalty under the contract.

Force Majeure

A contract clause excusing performance due to unforeseeable events beyond control.

Procurement Management Plan

A component of the project management plan that describes how project procurements will be managed from planning through contract closure click to see exemple.

Workaround

An unplanned response to a risk that occurs when no planned response exists.

Expected Monetary Value

A risk analysis technique calculating average outcomes (click to see exemple)

Quantitative Risk Analysis

Numerical analysis of the combined effect of risks on project objectives (click to see exemple).

Residual Risk

Risk remaining after responses have been implemented.

Risk Register

A document listing identified risks, their characteristics, responses, and owners click to see exemple.

Risk

An uncertain event or condition that may affect project objectives.

Quality Expectations

Stakeholder perceptions of acceptable performance beyond formal standards.

Quality Standards

Mandatory specifications that must be complied with.

Quality Management Plan

A document describing how quality policies, standards, and requirements will be met click to see exemple.

Benefit–Cost Ratio

The ratio of expected benefits to expected costs.

Payback Period

The time required to recover the initial investment.

Internal Rate of Return

The discount rate at which NPV equals zero.

Net Present Value

The value of future cash flows discounted to today.

Return on Investment

A financial measure comparing the net benefit of an investment to its cost.

Management Reserve

Time or cost set aside by management for unforeseen work, not included in the baseline.

Contingency Reserve

Time or cost set aside for identified risks.

Cost Baseline

The approved version of the project budget used for monitoring and control click to see exemple.

Critical Path

The longest sequence of dependent activities that determines the shortest project duration.

Lag

The amount of time an activity is delayed relative to its predecessor.

Lead

The amount of time an activity can be advanced relative to its predecessor.

Rolling Wave Planning

A planning approach where near-term work is planned in detail and future work at a higher level.

Schedule Management Plan

A document that establishes how the schedule will be developed, monitored, and controlled click to see exemple.

Activity-on-Node Network

A schedule network diagram where activities are represented by nodes and dependencies by arrows click to see exemple.

Define Activities

The process of identifying and documenting specific actions needed to produce deliverables.

Decomposition

The technique of subdividing deliverables and work into smaller, more manageable components.

Work Breakdown Structure

A hierarchical decomposition of the total scope of work into manageable components (click to see exemple).

Project Scope Statement

A detailed description of the project deliverables, boundaries, and acceptance criteria click to see exemple.

Requirement Traceability Matrix

A table that links requirements to their origins and corresponding deliverables click to see exemple.

Requirements Documentation

A detailed description of individual stakeholder requirements click to see exemple.

Requirements Management Plan

A document that defines how requirements will be collected, analyzed, tracked, and reported click to see exemple.

Scope Management Plan

A component of the project management plan describing how scope will be defined, validated, and controlled click to see exemple.

Phase Gate

A review point at the end of a project phase where performance is evaluated to determine whether to continue, modify, or terminate the project)

Project Phase

A collection of logically related project activities that culminates in the completion of one or more deliverables.

Project Life Cycle

The series of phases a project passes through from initiation to closure.

Tailoring

the deliberate adaptation of project management processes to fit the project’s context, size, and complexity.

Organizational Process Assets

Plans, processes, policies, procedures, and knowledge bases specific to the organization.

Enterprise Environmental Factors

External and internal conditions not under the control of the project team that influence or constrain the project.

Psychological Safety

A shared belief that the team is safe for interpersonal risk-taking.

Servant Leadership

A leadership approach focused on serving the team by removing obstacles and enabling performance.

Leadership

The ability to guide, motivate, and influence individuals or teams toward achieving objectives.

Salience Model

A stakeholder classification model based on power, legitimacy, and urgency (click to see exemple).

Stakeholder Engagement Assessment Matrix

A tool that compares current and desired stakeholder engagement levels click to see exemple.

Power Interest Grid

A stakeholder analysis tool that categorizes stakeholders based on their level of authority (power) and their level of concern or involvement (interest) in the project.

Stakeholder

An individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a project.

Assumption Log

A document used to record assumptions and constraints throughout the project lifecycle click to see exemple.

Benefits Management Plan

A document that defines how benefits will be delivered, measured, and sustained over time and who is responsible for them click to see exemple.

Business Case

A documented economic justification for the project that explains the expected benefits, costs, and risks Click to see exemple.

Project Charter

A document issued by the sponsor that formally authorizes the project and grants the project manager authority to apply organizational resources click to see exemple.

Directive PMO

A PMO that directly manages projects and assigns project managers

Controlling PMO

A PMO that requires compliance with standards and frameworks

Supportive PMO

A PMO that provides guidance and templates with low control.

Project Management Office

An organizational structure that standardizes project-related governance processes and facilitates the sharing of resources, methodologies, and tools.

Strong Matrix Organization

An organizational structure where project managers have high authority and full-time project staff, while functional managers retain limited control.

Legitimacy

The recognized and accepted right to make decisions and take actions, derived from formal authorization, governance structures, and assigned authority rather than personal influence or urgency.

Accountability

The obligation to answer for outcomes and consequences, regardless of who performed the work.

Authority

The legitimate power granted to an individual to make decisions, allocate resources, give direction, and approve actions within defined boundaries established by the organization’s governance framework.

Governance Path

The defined route through which project decisions, documents, and issues move for review, approval, escalation, and oversight within the organization’s governance framework.

Project Governance

The framework of rules, roles, decision-making authority, and oversight used to align the project with organizational strategy and ensure accountability.

Portfolio

A collection of projects, programs, and operations managed as a group to achieve strategic objectives

Program

A group of related projects managed in a coordinated way to obtain benefits not available from managing them individually.

Project Manager

The person assigned by the performing organization to lead the team responsible for achieving project objectives.

Project

a temporary endeavor undertaken to create a unique product, service, or result

Title

Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

Ministry of Sports

A public-sector organization responsible for national sports infrastructure and programs