Alternatives Analysis
Alternatives analysis is a technique used to evaluate different approaches, methods, or options for accomplishing project work, helping the team select the best way to define and deliver the scope.
Know it well enough for the exam? Questions on Alternatives Analysis are scenario-based, not definitional.
Practice it freeExplanation
Alternatives analysis is a broadly applicable technique used across multiple knowledge areas and processes. In scope management, it is used during Define Scope and Collect Requirements to evaluate different ways to meet project requirements, deliver the product, or structure the project work. The goal is to identify the approach that best balances scope, cost, schedule, quality, risk, and resource constraints.
The technique involves identifying multiple feasible alternatives, evaluating each against defined criteria, and selecting the option that provides the most favorable outcome for the project. Evaluation criteria may include cost, time to implement, technical feasibility, risk level, resource availability, and alignment with organizational strategy.
Alternatives analysis is not unique to scope management. It appears in cost management (evaluating make-vs-buy decisions), schedule management (evaluating scheduling approaches), risk management (evaluating response strategies), and other areas. Understanding that it is a general-purpose analytical technique applied in many contexts is important for the exam.
Key Points
- •Evaluates different approaches for accomplishing project work
- •Used in Define Scope, Collect Requirements, and many other processes
- •Considers cost, schedule, risk, feasibility, and other criteria
- •General-purpose technique applied across multiple knowledge areas
Exam Tip
Alternatives analysis appears in many processes across the PMBOK Guide. On the exam, it is the answer when the question asks about evaluating different options or approaches to accomplish work.
Frequently Asked Questions
Related Topics
Define Scope
Define Scope is the process of developing a detailed description of the project and product, resulting in the project scope statement.
Product Analysis
Product analysis is a set of techniques used in the Define Scope process to translate product descriptions and objectives into tangible deliverables and requirements.
Collect Requirements
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.
Resource Leveling
Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Stakeholder Mapping
Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Cost Performance Index (CPI)
Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.
Schedule Performance Index (SPI)
Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.
Earned Value Management (EVM)
Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.
Power/Influence Grid
The power/influence grid is a stakeholder classification model that groups stakeholders based on their level of authority (power) and their active involvement or ability to affect the project (influence).
Part of
Scope Management
Practice Alternatives Analysis
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.