Project Management Acronyms and Abbreviations

Work Breakdown Structure. A hierarchical decomposition of the total scope of work into manageable sections. Each level breaks deliverables into smaller components until work packages are small enough to estimate and assign.

Statement of Work. A formal document that defines the project's deliverables, timeline, milestones, and acceptance criteria. Typically created before the project charter and attached to contracts with external vendors.

Scope of Work. Often used interchangeably with Statement of Work but sometimes refers specifically to the boundaries of what is and is not included in a project. Context determines which meaning applies.

Business Requirements Document. Captures the high level business needs and objectives that a project must satisfy. Typically owned by a business analyst and reviewed by stakeholders before technical requirements are written.

Must Have, Should Have, Could Have, Won't Have. A prioritization framework that sorts requirements into four tiers. Originally developed for DSDM (Dynamic Systems Development Method) and widely used in Agile environments.

Responsible, Accountable, Consulted, Informed. A matrix that clarifies who does the work (R), who owns the decision (A), who provides input (C), and who needs to know the outcome (I) for each task or deliverable.

Request for Proposal. A document sent to vendors inviting them to submit a bid for a defined scope of work. Includes evaluation criteria, timeline, and submission requirements.

Request for Information. A preliminary document used to gather general information from potential vendors before issuing an RFP. Less formal and does not commit either party.

Request for Quotation. A document requesting specific pricing for a well defined scope. More specific than an RFP and typically used when the requirements are already clear.

Specific, Measurable, Achievable, Relevant, Time bound. A goal setting framework that ensures objectives are concrete enough to track and evaluate. Used across project management, performance reviews, and OKR planning.

Critical Path Method. A scheduling technique that identifies the longest sequence of dependent tasks, which determines the minimum project duration. Any delay on the critical path delays the entire project.

Program Evaluation and Review Technique. A probabilistic scheduling method that uses three time estimates (optimistic, most likely, pessimistic) to calculate expected task duration and project completion probability.

Finish to Finish. A task dependency where the successor cannot finish until the predecessor finishes. Less common than Finish to Start but useful for tasks that must end simultaneously.

Finish to Start. The most common task dependency. The successor cannot start until the predecessor finishes. Example: testing cannot start until development finishes.

Start to Start. A dependency where the successor cannot start until the predecessor starts. Used when two tasks can run in parallel but must begin together.

Start to Finish. The rarest dependency type. The successor cannot finish until the predecessor starts. Occasionally used in just in time manufacturing scheduling.

Level of Effort. Work that is measured by time rather than by discrete deliverables. Project management, coordination, and oversight are typical LOE activities. Tracked separately from discrete and apportioned effort in earned value systems.

Precedence Diagramming Method. A visual technique for creating network diagrams that show task dependencies using nodes (activities) and arrows (relationships). The foundation for CPM calculations.

Earned Value Management. An integrated methodology that combines scope, schedule, and cost data to measure project performance. Uses metrics like CPI and SPI to objectively assess whether a project is on track.

Planned Value. The authorized budget assigned to scheduled work. Represents what the project should have spent by a given date if everything went according to plan. Also called Budgeted Cost of Work Scheduled (BCWS).

Earned Value. The value of work actually completed, measured against the budget. If a task budgeted at $10,000 is 50% complete, the EV is $5,000. Also called Budgeted Cost of Work Performed (BCWP).

Actual Cost. The real cost incurred for work performed during a specific time period. Compared against EV and PV to determine cost and schedule variance.

Cost Performance Index. EV divided by AC. A CPI of 1.0 means on budget. Above 1.0 means under budget. Below 1.0 means over budget. The most reliable early warning indicator of final cost overrun.

Schedule Performance Index. EV divided by PV. A SPI of 1.0 means on schedule. Above 1.0 means ahead. Below 1.0 means behind. Less reliable than CPI in the final third of a project.

Cost Variance. EV minus AC. A positive CV means under budget. A negative CV means over budget. Expressed in currency units, making it easier to communicate to stakeholders than CPI ratios.

Schedule Variance. EV minus PV. A positive SV means ahead of schedule. A negative SV means behind. Like CV, expressed in currency units for easier stakeholder communication.

Estimate at Completion. The projected total cost of the project based on current performance. Multiple formulas exist depending on whether future work is expected to follow original estimates or current trends.

Estimate to Complete. The expected cost to finish the remaining work. Calculated as EAC minus AC. Used in reforecasting exercises and funding requests.

Budget at Completion. The total authorized budget for the project. The baseline against which all earned value metrics are measured. Changes only through formal change control.

To Complete Performance Index. The cost performance required on remaining work to meet a specified target (BAC or EAC). A TCPI above 1.0 means the team must be more efficient than planned on all remaining work.

Variance at Completion. BAC minus EAC. Predicts how much over or under budget the project will be when finished. A negative VAC signals a projected overrun.

Risks, Assumptions, Issues, Dependencies. A tracking log used to monitor the four categories of uncertainty that affect project delivery. Typically maintained as a shared spreadsheet or board and reviewed weekly.

Risk Breakdown Structure. A hierarchical representation of risks organized by category (technical, external, organizational, project management). Helps ensure risk identification is comprehensive and not clustered in one area.

Expected Monetary Value. Probability of a risk event multiplied by its financial impact. Used in quantitative risk analysis and decision trees. A 30% chance of a $100,000 loss gives an EMV of negative $30,000.

Failure Mode and Effects Analysis. A systematic method for evaluating potential failure points, their severity, likelihood, and detectability. Originated in manufacturing and aerospace, now used in IT and healthcare projects.

Quality Assurance. Process oriented activities that ensure the project's processes are adequate to produce quality deliverables. Focuses on preventing defects through process improvement rather than finding them after the fact.

Quality Control. Product oriented activities that verify deliverables meet defined quality standards. Includes inspections, testing, and reviews. Focuses on identifying defects in outputs.

User Acceptance Testing. The final testing phase where end users verify that a deliverable meets their requirements and is ready for production. Sign off on UAT typically triggers project closure.

Suppliers, Inputs, Process, Outputs, Customers. A high level process mapping tool used in Six Sigma and Lean to define a process before detailed analysis begins. Typically completed on a single page.

Project Management Office. An organizational unit that standardizes project governance, provides methodology support, and oversees portfolio prioritization. PMO structures range from supportive (advisory) to directive (controlling).

Project Manager. The individual accountable for planning, executing, and closing a project within scope, schedule, and budget constraints. Reports to a sponsor or PMO and manages the project team.

Product Owner. In Scrum, the person responsible for maximizing product value by managing the product backlog. Prioritizes features based on business value, stakeholder input, and user feedback.

Scrum Master. A servant leader who facilitates Scrum events, removes impediments, and coaches the team on Agile practices. Does not manage the team directly but ensures the Scrum framework is followed.

Enterprise Project Management Office. A PMO that operates at the enterprise level, overseeing all projects and programs across business units. Responsible for strategic alignment, resource allocation, and portfolio governance.

Change Control Board. A formally chartered group responsible for reviewing, evaluating, approving, or rejecting proposed changes to project baselines. Membership typically includes the sponsor, PM, and key stakeholders.

Information Technology Infrastructure Library. A set of practices for IT service management that aligns IT services with business needs. Covers service strategy, design, transition, operation, and continual improvement.

Project Management Body of Knowledge. PMI's foundational standard that defines 10 knowledge areas and 5 process groups. The 7th edition (2021) shifted from process based to principle based guidance.

Project Management Professional. PMI's flagship certification requiring 36 months of experience leading projects (with a degree) or 60 months (without), plus 35 hours of education. Recognized globally across industries.

Certified Associate in Project Management. PMI's entry level certification for those with less experience. Requires a secondary degree plus 23 hours of PM education. Valid for 3 years.

Certified ScrumMaster. Scrum Alliance's foundational Scrum certification. Requires a 2 day training course and passing exam. Focuses on Scrum framework knowledge and servant leadership principles.

Scaled Agile Framework. A framework for implementing Agile practices at enterprise scale across multiple teams. Organizes work into Agile Release Trains (ARTs) and uses Program Increment (PI) planning as its central ceremony.

Objectives and Key Results. A goal setting framework where qualitative objectives are paired with 2 to 5 measurable key results. Popularized by Intel and Google. Typically set quarterly with 60 to 70% achievement considered healthy.

Key Performance Indicator. A quantifiable metric that measures progress toward a specific objective. Effective KPIs are tied to outcomes (revenue, cycle time, defect rate) rather than activities (meetings held, emails sent).

Projects IN Controlled Environments, version 2. A process driven PM methodology widely used in the UK, Australia, and government sectors. Defines 7 principles, 7 themes, and 7 processes with a strong emphasis on business case justification.

Dynamic Systems Development Method. An Agile framework that predates the Agile Manifesto. Emphasizes the principle that time and cost are fixed while features are variable. Uses MoSCoW prioritization and timeboxing.