Encyclopedia of Project Management & Controls
An A–Z reference of 198+ entries covering scheduling, cost control, earned value, risk, forensic analysis, digital delivery and more — curated by Dr. Hassan Eliwa, Founder of PMMilestone.org.
Activity Definition
The process of identifying and documenting the specific actions required to produce project deliverables, decomposing work packages into discrete schedulable activities.
Agile Project Management
An iterative, adaptive approach to project delivery that emphasises customer collaboration, short feedback cycles, and continuous improvement.
As-Built Schedule
A factual, evidence-based record of how a project actually unfolded — start dates, finish dates, durations, and logic of every activity as they really happened, not as they were planned.
Acceptance Criteria
The specific, testable conditions a deliverable must meet before the customer accepts it — the contract between a team and the person who will sign off the work.
As-Built Drawings Management
The disciplined capture, red-lining and issue of drawings that reflect the works as they were actually constructed, not as they were originally designed.
Alert Fatigue Management
The discipline of pruning, tuning and prioritising monitoring alerts so that on-call engineers respond urgently to real problems instead of ignoring a flood of noise.
Baseline Schedule
The approved, time-phased plan against which actual progress is measured and variance is reported throughout the project.
Budget Control
The disciplined monitoring of project spend against the approved budget through commitments, accruals, and variance reporting.
Backlog Refinement
The ongoing practice of clarifying, splitting, estimating, and ordering items on a product backlog so the team always has a healthy queue of ready work for upcoming sprints or releases.
Burn-Down Chart
A time-series chart showing remaining work against time, used by agile teams to visualise sprint or release progress and forecast completion.
BIM Coordination
The disciplined process of combining the 3D models produced by design and trade contractors, detecting conflicts, and resolving them in a virtual environment before steel, ductwork, or pipe is fabricated and installed.
Bid Leveling
The structured normalization of competing contractor proposals so price differences reflect real scope and risk differences — not gaps in what each bidder included.
Burn Rate
The speed at which a project consumes budget or capacity per unit of time — the single fastest indicator that cost or effort is drifting off plan.
Blameless Postmortem
A structured, no-fault review after an incident or failure focused on system and process causes rather than individual blame — the operating practice behind every mature reliability culture.
Blue-Green Deployment
A release technique that runs two production environments — blue (current) and green (new) — and switches traffic between them, enabling near-zero-downtime deploys and instant rollback.
Bug Triage
The regular, disciplined meeting where new defects are reviewed, classified, prioritised and assigned — the difference between a live product backlog and a graveyard of unresolved tickets.
Backlog Refinement (Grooming) Cadence
The regular rhythm of clarifying, sizing and ordering upcoming work so the team enters every sprint with a ready-to-start backlog rather than a wish list.
Critical Path Method (CPM)
A deterministic scheduling technique that identifies the longest chain of dependent activities and the activities that drive the project completion date.
Cost Control
The integrated discipline of estimating, baselining, monitoring, forecasting, and reporting project cost to drive corrective action and protect outcomes.
Change Control
The formal process by which scope, schedule, cost, or quality changes are identified, evaluated, approved, and incorporated into the baseline.
Contingency Reserve
A controlled allocation of budget or schedule set aside to address identified risks that may materialise during execution, owned by the project manager and drawn down via a documented process.
Cost Performance Index (CPI)
An earned value efficiency metric defined as Earned Value divided by Actual Cost, indicating how much value the project has earned for every dollar actually spent.
Constructability Review
A structured early-stage review of design documents by experienced builders to surface buildability, sequencing, and cost-impact issues before they become field problems.
Continuous Integration
The engineering practice of merging code changes into a shared mainline many times a day and verifying each merge with automated builds and tests.
Cumulative Flow Diagram
A stacked-area chart of work items in each stage over time — the single most informative chart in lean and Kanban flow management.
Change Order Management
The contractual and operational process of identifying, pricing, negotiating, approving, and incorporating changes to the original scope of work — the single largest source of cost growth and disputes on construction projects.
Cost Loading
Assigning budgeted cost to each schedule activity so the time-phased schedule itself becomes the project budget baseline used for earned value and cash-flow forecasting.
Chaos Engineering
The disciplined practice of injecting controlled failures into a running system to expose weaknesses before real incidents do — proactive resilience testing at production scale.
Concurrent Delay
Two or more delay events, one owner-caused and one contractor-caused, running in the same window and each independently capable of delaying completion.
Commissioning Plan
The structured document defining how a facility or system will be tested, verified, and handed over from construction to operations.
Canary Release
A release technique that exposes a new version of software to a small subset of traffic or users first, so problems are detected on a limited blast radius before the full rollout.
Concrete Pour Card
A single-page control document that authorises a specific concrete pour by confirming design, formwork, reinforcement, embedments, weather and inspection sign-offs are all in place before the truck arrives.
Concrete Cube Testing
The sampling, curing and crushing regime that proves a concrete pour actually reached its design strength — and the auditable chain of custody that makes those results defensible.
Contract Testing
A testing strategy for services that talk to each other — each consumer records the shape of the responses it relies on, and the provider verifies against those recorded contracts on every change.
Concrete Curing Regime
The controlled temperature, moisture and time regime applied to freshly placed concrete so that it reaches its designed strength and durability rather than the strength the weather happened to allow.
Cognitive Load Management
The deliberate practice of sizing team scope, tooling and processes so engineers can hold the whole picture in their heads — the ceiling on how much complexity a team can safely own.
Change Advisory Board
The forum — traditionally ITIL, now often lightweight — that reviews and authorises high-risk production changes, or delegates the routine ones to the teams best placed to make them.
Commissioning Witness Testing
The formal, client-witnessed proving of installed systems against design intent — the point where a project stops being a construction site and starts being an operating asset.
Concrete Delivery Docket Control
The site-level discipline of checking, signing and archiving every ready-mix delivery ticket — the only reliable evidence of what was actually poured into your structure.
Chaos Engineering Practice
The deliberate injection of controlled failure into production systems to discover the weaknesses that only surface under stress — turning fear of the unknown into an engineering discipline.
Delay Analysis
Forensic and prospective techniques used to identify, quantify, and apportion responsibility for schedule delay on construction and IT projects.
Digital Twin
A continuously updated digital representation of a physical asset or process used to monitor, simulate, and optimise performance across the lifecycle.
Daily Stand-up
A short, focused, time-boxed daily meeting where the delivery team aligns on progress, plans the next 24 hours of work, and surfaces blockers.
Definition of Done
A shared, written checklist that defines what 'done' means for a unit of work — the single most important quality discipline in agile delivery.
DevOps
The cultural and engineering practice of merging software development and operations into a single, continuous flow — automating build, test, deploy, monitoring, and feedback to ship software faster and more reliably.
Dependency Mapping
The systematic identification of internal, external, mandatory, and discretionary relationships between activities so the schedule logic mirrors the way work really has to happen.
Definition of Ready (DoR)
The shared team agreement about the minimum characteristics a backlog item must have before it can be pulled into a sprint.
Daily Site Diary
The contemporaneous daily record of everything that happened on a construction site — labour, plant, weather, deliveries, visitors, instructions, delays — kept in chronological order and signed each day.
Deployment Freeze Window
A pre-agreed period during which no non-emergency changes reach production — the operational discipline that protects a business's most exposed hours from avoidable engineering risk.
Definition of Done (DoD)
The team's shared, written checklist of what must be true before any piece of work is considered complete — the fence between 'it works on my machine' and shippable.
Dilapidation Survey
A dated, photographic record of the condition of neighbouring properties and public assets before construction begins — the contractor's insurance against every crack blamed on them later.
Earned Value Management (EVM)
An integrated cost-schedule-scope measurement technique that compares planned, earned, and actual values to reveal project performance and forecast outcomes.
Estimate at Completion (EAC)
A forward-looking forecast of the total cost (or duration) of a project at completion, derived from current performance data and assumptions about future performance.
Earned Schedule
A time-based extension of earned value that converts schedule performance into units of time, fixing EVM's well-known late-project blind spot.
Epic
A large body of work in agile delivery that delivers significant business value but is too big for a single sprint — decomposed into features and user stories that flow through the team over weeks or months.
Extension of Time
A contractual entitlement that pushes the completion date when delay events outside the contractor’s control consume float on the critical path.
Error Budget
The maximum acceptable unreliability of a service in a period, derived from its SLO — the governance mechanism that lets SRE teams balance velocity with reliability.
Excavation Support Design
The engineered system — sheet piles, secant walls, soldier piles, propping or soil nailing — that keeps the sides of a deep excavation, and everything above them, in the position the design demands.
Error Budget Policy
The explicit, negotiated agreement between engineering and product that says what happens when reliability drops — the mechanism that turns SLOs from posters into decisions.
Ephemeral Preview Environment
A short-lived, per-branch or per-pull-request deployment that lets reviewers see and test changes in isolation — the practice that quietly cuts review cycles in half.
Float Management
The deliberate planning and consumption of schedule float (slack) to absorb uncertainty and prioritise management attention.
Forward Pass Scheduling
The CPM calculation that walks the network from project start to finish to determine the Early Start and Early Finish of every activity, establishing the earliest the project can possibly complete.
Feature Flag
A configuration-driven switch that lets teams turn software features on or off in production without redeploying — decoupling deploy from release and making rollback a single config change.
Force Account Work
Work performed on a time-and-materials basis — used when scope is too uncertain to price as a lump sum, with strict daily records to substantiate cost.
Fragnet (Fragmentary Network)
A small, self-contained network of activities inserted into a baseline schedule to model a delay, change, or recovery scenario without disturbing the main logic.
Feature Toggle
A software mechanism that lets code paths be turned on or off at runtime without redeploying — decoupling deploy from release.
Formwork Cycle Planning
The activity-level planning of formwork rotation, strike times and re-propping sequences that governs the pace of concrete construction and directly drives the critical path on cast-in-place structures.
Feature Team
A long-lived, cross-functional, cross-component team that delivers end-to-end customer-visible features — as opposed to a component team responsible for a single technical layer.
Feature Flag Management
The disciplined use of runtime toggles to decouple deploy from release — enabling safer rollouts, targeted experiments and instant rollback without redeploying.
Formwork Pressure Calculation
The engineering calculation that predicts the lateral pressure fresh concrete will exert on formwork — the number that decides whether the wall stands up or blows out in front of the pour team.
Gantt Chart
A bar-chart visualisation of project activities along a calendar axis, used to communicate schedule, dependencies, and progress.
Gemba Walk
A lean management practice of going to the actual place where work is performed — site, factory floor, or team room — to observe, ask questions, and learn directly rather than rely on reports.
Greenfield Project
A project built from scratch on undeveloped ground — physical or digital — with no legacy constraints, no incumbent systems to integrate, and the freedom (and burden) of defining every standard from first principles.
Project Governance
The decision-rights, escalation paths, and review cadence that keep a project accountable to its sponsors while empowering the delivery team to move at pace.
Golden Signals Monitoring
The four service-level metrics — latency, traffic, errors and saturation — that together tell you almost everything you need to know about a running system.
Hammock Activity
A summary scheduling element whose duration is dynamically derived from the start of one activity and the finish of another.
Handover Management
The structured process of transferring a completed project, phase, or deliverable from the delivery team to the receiving operator, with all documentation, training, and warranties intact.
Hotfix Deployment
An expedited release used to correct a serious production defect — sized small, scoped narrowly, deployed quickly, and recorded carefully so the urgency does not become a habit.
Heuristic Estimation
Rule-of-thumb estimating techniques — analogous, parametric, three-point — that produce defensible numbers fast when fully detailed estimates are not yet possible.
Handover Documentation Pack (O&M Manuals)
The complete, indexed, verified record of the built asset — drawings, warranties, test certificates, O&M manuals, spares lists — issued at handover so the operator can actually run the building.
Hoarding & Site Boundary Plan
The drawing and specification that fixes exactly where the construction site ends and the public world begins — a document that is quietly one of the most litigated on any urban project.
Issue Management
The structured process of logging, triaging, owning, escalating, and closing problems that threaten project objectives.
Integrated Master Schedule
A single, network-logic schedule that integrates all activities, deliverables, milestones and resources across every contributor on a programme, used as the authoritative basis for planning, reporting and analysis.
Incident Management
The structured response to unplanned events that disrupt service or safety — detection, declaration, containment, communication, resolution, and learning, all run on a playbook rather than improvised under pressure.
Iteration Planning
The team-level meeting that turns a prioritized backlog into a credible, committed plan for the next sprint — balancing capacity, dependencies, and the definition of done.
Interface Management
The disciplined identification, tracking, and resolution of the technical, contractual, and physical boundaries between packages, contractors, and disciplines on a project.
Infrastructure as Code (IaC)
The practice of provisioning and managing servers, networks, databases and cloud resources through version-controlled definitions rather than manual clicks in a console.
Job Cost Reporting
Periodic financial reporting that consolidates committed, actual, accrued, and forecast costs against the project budget at the cost-code level.
Just-in-Time Delivery
A lean logistics approach where materials, components, or work items arrive exactly when needed for the next activity, reducing inventory, waste, and double-handling.
Jidoka
The lean principle of 'autonomation' — building quality into the process by empowering people and machines to stop the line the moment a defect is detected, rather than passing the problem downstream.
Key Performance Indicator (KPI)
A quantifiable, time-bound metric that signals whether a project is moving toward or away from a defined objective.
Kanban
A pull-based work management method that visualises flow on a board, limits work-in-progress, and improves delivery through measured experiments rather than fixed iterations.
Kickoff Meeting
The deliberate event that converts a contract or charter into a working team — aligning purpose, roles, communication channels, and decision rights before execution begins.
Lessons Learned
The structured capture, validation, and reuse of project knowledge to compound organisational performance over time.
Look-Ahead Schedule
A short-term, detailed schedule (typically 3–6 weeks) extracted from the master schedule and made constraint-free, used to drive day-to-day execution and crew coordination.
Last Planner System
A collaborative lean construction planning method where the people who will perform the work commit to what they can actually do, replacing top-down schedules with promises and weekly learning.
Linear Scheduling Method
A graphical scheduling technique tailored to linear and repetitive projects — highways, pipelines, tunnels, high-rise floors — that plots progress in space against time so production rates and crew interactions are visible at a glance.
Liquidated Damages
A pre-agreed contractual sum payable by the contractor for each day of delay beyond the contract completion date — a substitute for proving actual loss.
Lead Time vs Cycle Time
Two closely related flow metrics — lead time measures from customer request to delivery; cycle time measures from active work start to delivery.
Lifting Plan (Rigging Study)
The engineered document that turns a crane lift from an ambition into a controlled operation — loads, radii, ground pressures, rigging, exclusion zones, and the named people accountable for each.
Milestone
A zero-duration scheduling marker that signals the completion of a significant deliverable, decision, or transition in the project.
Monte Carlo Simulation
A probabilistic technique that runs thousands of randomised iterations of a model to produce distributions of cost and schedule outcomes.
Milestone Trend Analysis (MTA)
A visual technique that tracks the forecast completion dates of project milestones over time, exposing schedule drift early and triggering corrective action.
Management Reserve
A budget or time allowance held by senior leadership, outside the project baseline, to absorb unknown-unknown risks that cannot be quantified during planning.
Mob Programming
A whole-team development style where everyone works on the same problem at the same time on one screen — the extreme form of pair programming, used to crush complex problems and spread knowledge fast.
Milestone Payment
A contractual payment triggered by the verified completion of a defined project milestone rather than by elapsed time or measured progress.
Method Statement
A written document that explains, step by step, how a specific construction activity will be executed safely, in what sequence, with what resources, and under what controls.
Materials Reconciliation Report
The periodic comparison of materials delivered to site against materials measured into the permanent works — the report that finds the missing rebar, cement and cladding before the auditor does.
Network Diagram
A logical graph of project activities and dependencies that exposes the sequence, parallelism, and critical path of the work.
Non-Functional Requirements
The quality attributes a system must exhibit — performance, reliability, security, scalability, accessibility — that often determine success or failure more decisively than functional features.
Near-Critical Path
Activity chains with low total float that are one delay event away from becoming the critical path — the schedule's hidden risk surface.
Non-Conformance Report (NCR)
A formal record of work that does not meet the specification, the drawings, or an approved procedure — logged, dispositioned, closed out and trended to expose systemic quality problems.
Objectives and Key Results (OKRs)
A goal-setting framework that pairs qualitative objectives with measurable key results, used to align teams and surface progress transparently.
Observability
The engineering discipline of designing systems whose internal state can be inferred from their outputs — logs, metrics, traces — so that unknown failures can be diagnosed without redeployment.
Operational Readiness
The discipline of preparing people, processes, systems, and assets so that on day one of operations the facility or product runs as designed — not as a list of open punch items.
On-Call Rotation
The sustainable arrangement by which engineers take turns to be reachable outside working hours to respond to production incidents — a discipline whose humaneness is a leading indicator of engineering culture.
Procurement Management
The disciplined planning, selection, contracting, and administration of external goods and services required to deliver the project.
Program Management
The coordinated management of related projects, sub-programmes, and operations to achieve benefits not available from managing them individually.
PERT (Program Evaluation and Review Technique)
A probabilistic scheduling method using three-point activity estimates (optimistic, most-likely, pessimistic) to compute expected durations and variance.
Punch List
The construction industry's snag list — the final inventory of incomplete or defective items that stand between substantial completion and project handover.
Pair Programming
A collaborative engineering practice where two developers work together at one workstation — one driving, one navigating — to build higher-quality software with continuous review and knowledge transfer.
Progressive Elaboration
The disciplined practice of refining project plans in successive levels of detail as more information becomes available — planning at the right level for the right horizon.
Procurement Log
A living register of every material, equipment item, subcontract package, and long-lead procurement action on a project — the single source of truth linking design, schedule, and cost.
Pull Planning
A collaborative planning technique in which trades work backward from a milestone, pulling handoffs and commitments from one another, to build a schedule the whole team actually believes.
Permit to Work
A formal, written authorisation controlling high-risk site activities — confined space entry, hot work, work at height, live electrical — issued only after specific hazards have been assessed and controls verified.
PI Planning
Program Increment Planning — the cadence-based, face-to-face event in SAFe where all teams on an Agile Release Train commit to a set of objectives for the next 8–12 week increment.
Piling Records
The rig-by-rig, pile-by-pile log of driven or bored piles — depths, sets, torques, concrete volumes and rejections — that forms the primary evidence of a foundation's integrity.
Production Readiness Review
A structured checklist-driven review that a service must pass before it is allowed to serve production traffic — covering reliability, observability, security, capacity and operational ownership.
Pre-Construction Site Survey
The physical walk, measure and record of a site before any mobilisation — the survey that decides whether the tender assumptions were fiction or a plan.
Punch List (Snag List) Management
The disciplined tracking of every outstanding defect at handover — the list that decides whether a project actually reaches practical completion or drags on for months of disputes.
Post-Incident Review (Blameless Postmortem)
The structured, blame-free examination of what happened, why, and what will change — the meeting that turns a painful outage into organisational learning.
Progressive Delivery
The practice of releasing changes to production in controlled, observable stages — a small percentage of users first, then wider audiences as confidence grows — rather than to everyone at once.
Quality Management
The planned set of activities by which an organisation ensures deliverables meet requirements through prevention, assurance, and control.
Quality Gate
A formal checkpoint at which work is evaluated against pre-defined criteria and either passed forward, paused for rework, or stopped — preventing defects from flowing into later, more expensive stages.
Quantitative Risk Analysis
The numerical analysis of identified project risks to estimate their combined effect on cost and schedule — typically using probabilistic models such as Monte Carlo simulation.
Risk Management
The structured identification, analysis, response planning, and ongoing monitoring of uncertain events that could affect project objectives.
Resource Leveling
A scheduling technique that adjusts activity timing to resolve resource over-allocations, smoothing demand against available capacity.
RACI Matrix
A responsibility assignment chart that clarifies, for each task or decision, who is Responsible, Accountable, Consulted and Informed — eliminating the diffuse-ownership ambiguity that kills projects.
Rolling Wave Planning
A planning technique that details near-term work to a fine grain while keeping later work at a higher level, then progressively refines as the project proceeds.
Refactoring
The disciplined practice of changing the internal structure of code without changing its external behaviour — improving design, reducing complexity, and paying down technical debt without altering functionality.
Retainage
A percentage of progress payments withheld from contractors until defined performance milestones — usually substantial completion and final acceptance — are met.
RFI Management
The disciplined tracking of Requests for Information — the formal channel through which contractors ask designers to clarify, correct, or resolve ambiguities in the construction documents.
Release Train
A cadence-based delivery pattern — most closely associated with SAFe's Agile Release Train — that coordinates multiple agile teams to plan, build, and release on a shared, predictable rhythm.
Runbook
A written, step-by-step operational procedure that tells an on-call engineer exactly how to detect, diagnose and remediate a specific class of incident on a specific system.
Rebar Bending Schedule
The dimensioned list that tells the steel-fixing crew — and the fabricator — every diameter, length, shape code and quantity of reinforcement needed for a concrete element.
Rollback Plan
The pre-agreed, tested sequence for reverting a change if it fails in production — the difference between a five-minute recovery and a five-hour outage.
Release Notes Discipline
The habit of writing honest, useful, timely release notes for every change that reaches users — the smallest engineering practice with the largest and most under-appreciated effect on trust, support cost and adoption.
Stakeholder Engagement
The structured planning and execution of communications and relationships with parties whose support, indifference, or opposition shape project outcomes.
Scope Management
The discipline of defining, controlling, and protecting what the project will and will not deliver, from charter through handover.
S-Curve
A cumulative plot of planned, earned, or actual project quantity against time, used to visualise progress, productivity, and forecasting.
Sprint Retrospective
A time-boxed agile ceremony at the end of each sprint where the team inspects how it worked together and commits to specific improvements for the next sprint.
Submittal Management
The structured process of reviewing and approving shop drawings, product data, and samples that translate the design intent into what is actually fabricated and installed.
Story Points
A relative, unitless estimate of effort that captures complexity, uncertainty, and volume in a single number — and works only when teams resist the urge to convert them back into hours.
Service-Level Objective
A measurable reliability target — typically expressed as a percentage over a time window — that defines how reliable a service needs to be to satisfy users, and against which engineering trade-offs are made.
Schedule Compression
Techniques to shorten the schedule without reducing scope — primarily crashing (adding resources) and fast-tracking (overlapping activities) — used when end-date pressure exceeds the original plan.
Shop Drawing
A detailed fabrication or installation drawing prepared by the contractor, subcontractor, or supplier that translates design intent into buildable, dimensioned instructions.
Swarming
The practice of temporarily concentrating a whole team on a single high-priority item — story, incident, or blocker — until it is finished, rather than working many items in parallel.
Snagging Process
The systematic identification, logging, and closure of minor defects on a construction project before handover — the industry's most under-appreciated cost centre.
Spike (Agile)
A time-boxed investigation used when a story cannot be estimated or designed without further research or prototyping.
Site Logistics Plan
The drawing-and-narrative package that shows how a construction site will physically operate — access, deliveries, laydown, cranes, welfare, and traffic — through each major phase of the works.
Sprint Zero
A short pre-delivery sprint used to establish the environment, tooling, backlog, and team norms needed before productive delivery sprints begin.
Story Slicing
The craft of breaking a large user story into smaller stories that each deliver end-to-end value, fit within a sprint, and can be independently accepted.
Service Level Indicator (SLI)
A quantitative measurement of a service's behaviour — such as request success rate or latency at the 99th percentile — that expresses reliability in numbers the users actually experience.
Site Instruction
A written direction from the contract administrator or engineer to the contractor to carry out, vary or clarify work on site — the contractual mechanism that turns a verbal decision into an enforceable action.
Scaffolding Inspection Register
The statutory log of scaffold inspections — every seven days, after alteration, after weather — that determines whether the scaffold may be used, and who carries the legal risk if it is used when it should not be.
Site Mobilization Plan
The staged plan for turning a raw site into an operating construction workplace — access, welfare, utilities, permits, security — sequenced so the first productive activity can start on the day the schedule assumes it will.
Sectional Completion
A contractual mechanism that allows discrete sections of the works to reach practical completion — and to trigger their own damages, warranties and defect periods — independently of the rest of the project.
Service Level Objective (SLO)
The measurable, agreed target for a service's reliability — the number that decides whether the team ships new features next week or fixes reliability instead.
Sprint Goal Discipline
The practice of committing every sprint to a single, testable outcome — the goal — and using it to say no to everything that does not serve it.
Snagging Register
The live list of small defects, unfinished work and cosmetic issues identified as a project approaches completion — the difference between a handover that lands and one that drags for months.
Time-Impact Analysis (TIA)
A forward-looking schedule-delay analysis technique that quantifies the time impact of a specific change or delay event by inserting a fragnet into the current schedule.
Takt Time Planning
A lean production approach that paces work to a steady rhythm — the takt time — by sizing work zones so each crew finishes one zone in the same time, creating predictable flow.
Technical Debt
The accumulated cost of expedient engineering decisions — the metaphorical interest you pay every time you change a system that was built quickly rather than carefully.
Test-Driven Development
An engineering discipline of writing a failing test before the code that makes it pass — producing better-designed, better-tested software at a sustainable pace.
Trend Program
A structured forward-looking process to identify, value, and act on potential cost or schedule changes before they are formal change orders — the early-warning radar of capital projects.
Temporary Works Register
A live schedule of every temporary structure on site — shoring, formwork, scaffolding, edge protection, cranes bases, propping — with designer, checker, load-case and removal date for each.
Trunk-Based Development
A source-control practice in which all developers commit small changes to a single shared branch (trunk/main) at least daily, using feature flags rather than long-lived branches to manage in-progress work.
Toolbox Talk
A short, focused pre-shift safety briefing led by the foreman on a single hazard relevant to the day's work — the most-used and most-abused safety communication tool on any site.
Three Amigos Meeting
A short, focused conversation between a product person, a developer and a tester before a user story is committed — to surface ambiguity, agree on examples and shorten the feedback loop that would otherwise happen in code review.
Temporary Works Design Register
The controlled list of every temporary works item on a site — from a trench box to a tower crane base — with its design category, designer, checker, permit and load status.
Team Topologies
A model for organising software delivery teams into four types — stream-aligned, platform, enabling and complicated-subsystem — with defined interaction modes to reduce cognitive load and speed up flow.
Uncertainty Analysis
The quantitative assessment of variability in cost and schedule estimates arising from incomplete information, natural variation, and identified risk events.
User Story Mapping
A two-dimensional technique for visualising the user journey across the top axis and the depth of functionality down the axis — used to slice releases by value rather than by component.
Value Engineering
A systematic, function-focused review process that reduces life-cycle cost without sacrificing required performance, quality, or function.
Velocity
An agile team's empirical measure of how much work it completes per sprint — used to forecast capacity for upcoming sprints, not to compare or judge teams.
Variance at Completion
The forecast difference between the budget at completion (BAC) and the estimate at completion (EAC) — the single number that tells the board where the project is heading financially.
Value Stream Mapping
A Lean technique for visualising every step from customer request to delivered value, distinguishing value-add work from waste.
Work Breakdown Structure (WBS)
A deliverable-oriented hierarchical decomposition of project scope into manageable work packages used to organise estimating, scheduling, and control.
WIP Limits
A Kanban discipline that caps the number of work items in progress at each stage, forcing teams to finish before starting and exposing the bottlenecks that quietly destroy flow.
Work Package
The lowest level of the WBS — a discrete deliverable scope element that can be estimated, scheduled, resourced, and controlled as a single unit.
WIP Limit (Work in Progress Limit)
A cap on how many items a team may have in progress at once — the single most effective policy for improving flow.
Weather Contingency Planning
The disciplined process of forecasting weather impacts on programme, embedding realistic weather allowances into the schedule, and defining trigger-based response actions for each critical activity.
Wind-Speed Working Limits
The documented wind-speed thresholds at which specific site activities must be paused, protected or shut down — the difference between a well-run site and a lifting accident.
X-Bar Control Chart
A statistical process-control tool that plots the mean of subgroup samples over time to detect drift in a measurable project or production process.
Cross-Functional Team (X-Functional Team)
A team that combines the disciplines needed to deliver an outcome end-to-end — engineering, design, operations, commercial — eliminating handoffs that destroy schedule and quality.
Zero-Based Budgeting
A budgeting method that builds every cost from a zero base for each new period, requiring justification for every line item rather than incremental adjustment of the prior budget.
Zero-Downtime Migration
The set of patterns that move a live system from an old state to a new one — database, service, provider or region — without an outage window, using dual writes, shadow reads, and staged cutovers.
Frequently Asked Questions
What is the PMMilestone Encyclopedia of Project Management & Controls?
A research-grade, A–Z encyclopedia of project management and project controls terminology. Every entry is structured around a definition, key principles, practical applications, related entries, and frequently asked questions — written for practising engineers, not students cramming for exams.How do I find a specific term in the encyclopedia?
Use the search box for keyword search across term, definition and category, the topic filter to scope by domain (Schedule, Cost, Risk, Forensic, EVM, etc.), or click any letter A–Z to see all entries under that letter. Each letter page is a clean index with definitions and outbound links to the full entries.What topics does the encyclopedia cover?
Schedule management, cost engineering, earned value management, risk and contingency, forensic delay analysis, project integration, procurement, performance measurement, governance, quality, scope, knowledge management, leadership, and project methodologies (PMBOK, PRINCE2, Agile, Lean, Last Planner System).Are the encyclopedia entries cited and reviewed?
Yes. Every entry is authored by Dr. Hassan Eliwa, PhD (Founder of PMMilestone.org) and cross-referenced against PMBOK 7, AACE recommended practices, DCMA scheduling guidance, and field practice on EPC and infrastructure projects.What's the difference between this encyclopedia and the PM Glossary on PMMilestone.org?
The PM Glossary on PMMilestone.org gives a single-line definition for quick lookup. This encyclopedia is long-form: each entry runs to several thousand words covering principles, applications, common misconceptions, FAQs and curated further reading — designed to be the canonical reference for that term.Which encyclopedia entries pair with the EVM, SPI and CPI calculators?
Start with Earned Value Management, Schedule Performance Index, Cost Performance Index, Earned Schedule, Estimate at Completion and Variance Analysis. Each entry links to the matching calculator on PMMilestone.org so you can apply the formula to your own project data.