Study guide
3.3 Solution Option Evaluation: Feasibility Studies & Make/Buy/COTS Tradeoffs
PMI Professional in Business Analysis PMI-PBA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction, Exam Logistics & Business Analysis Framework
1.1 PMI-PBA Exam Format, Scoring, Logistics & Eligibility 1.2 Business Analyst vs Project Manager: Roles, Boundaries & Standards 1.3 Business Analysis Across Predictive, Adaptive & Hybrid Lifecycles
2 Chapter 2: Needs Assessment — Problem Framing & Opportunity Analysis
2.1 Defining Business Problems, Opportunities & Scope Statements 2.2 Root Cause Analysis: 5 Whys, Fishbone & Interrelationship Digraphs 2.3 Assessing Current Capabilities, Operational Constraints & Organizational Maturity
3 Chapter 3: Needs Assessment — Future State & Feasibility Analysis
3.1 Defining the Desired Future State & Product Scope Boundaries 3.2 Gap Analysis: Capability Matrices, Risk of Inaction & Transition States 3.3 Solution Option Evaluation: Feasibility Studies & Make/Buy/COTS Tradeoffs
4 Chapter 4: Needs Assessment — Business Case, Valuation & Stakeholder Values
4.1 Financial Valuation & Metrics: ROI, NPV, IRR, Payback & Cost-Benefit Analysis 4.2 Developing the Business Case & Aligning SMART Project Goals 4.3 Identifying Stakeholders & Establishing Stakeholder Values Baseline
5 Chapter 5: Planning — BA Approach & Context Framing
5.1 Reviewing Business Case, Project Charter & Context Framing 5.2 Establishing the Business Analysis Approach & Tailoring Strategy 5.3 Business Analysis Work Breakdown, Scheduling & Effort Estimation
6 Chapter 6: Planning — Stakeholder Engagement & Communication
6.1 Stakeholder Analysis: Power/Interest Grid, Salience Model & Onion Diagrams 6.2 Planning Stakeholder Communication, Engagement & Distributed Collaboration 6.3 Managing Stakeholder Expectations, Alignment & Conflict Resolution Pathways
7 Chapter 7: Planning — Governance, Traceability & Change Control
7.1 Developing the Requirements Management Plan (RMP) 7.2 Defining Requirements Traceability Strategy & Hierarchy 7.3 Defining Requirements Change Control Protocols & CCB Workflow 7.4 Document Control, Baselining & Defining Business Metrics/Acceptance Criteria
8 Chapter 8: Analysis — Requirements Elicitation Techniques & Collaboration
8.1 Elicitation Planning, Types & Stakeholder Preparation 8.2 Interactive Elicitation: Interviews, Focus Groups & JAD Workshops 8.3 Observational & User-Centered Elicitation: Job Shadowing & Surveys 8.4 Document Analysis, Interface Analysis & Reverse Engineering
9 Chapter 9: Analysis — Requirements Modeling & Decomposition
9.1 Scope Modeling: Context Diagrams, Ecosystem Maps & Feature Breakdowns 9.2 Process & Workflow Modeling: BPMN, Swimlanes & Value Stream Mapping 9.3 Data & Rules Modeling: ERDs, Data Dictionaries, DFDs & Decision Tables 9.4 Interface Modeling, Wireframing, User Journey Maps & Prototyping
10 Chapter 10: Analysis — Requirements Specification & Acceptance Criteria
10.1 Requirements Taxonomy: Business, Stakeholder, Solution, Transition, Project & Quality 10.2 User Stories, Epics, INVEST Criteria & Acceptance Criteria 10.3 Non-Functional Requirements & Quality Attributes 10.4 Consensus Building, Tradeoff Analysis & Resolving Competing Requirements
11 Chapter 11: Analysis — Verification, Validation, Prioritization & Approval
11.1 Requirements Verification & Quality Characteristics 11.2 Requirements Validation & Strategic Business Alignment 11.3 Requirements Prioritization Techniques: MoSCoW, Kano & WSJF 11.4 Product Risk Analysis & Design Option Evaluation
12 Chapter 12: Traceability & Monitoring — Traceability Matrix & Baselining
12.1 Constructing & Maintaining the Requirements Traceability Matrix (RTM) 12.2 Monitoring Requirements Across Lifecycle Artifacts 12.3 Requirements Baselining, Scope Management & Preventing Creep
13 Chapter 13: Traceability & Monitoring — Lifecycle States & Change Management
13.1 Managing Requirements Status & Lifecycle State Transitions 13.2 Communicating Requirements Status, Visual Dashboards & Burndowns 13.3 Requirements Change Management & Multi-Dimensional Impact Analysis 13.4 Resolving Requirements Conflicts, Defect Triage & Variance Management
14 Chapter 14: Evaluation & Professional Conduct
14.1 Validating Test Evidence & Results Against Acceptance Criteria 14.2 Solution Gap Analysis, Discrepancy Resolution & Workarounds 14.3 Facilitating Stakeholder Sign-Off, Operational Readiness & Transition 14.4 Evaluating Long-Term Solution Performance & Value Realization 14.5 PMI Code of Ethics, Professional Conduct & Continuing Certification (CCR)
3.3 Solution Option Evaluation: Feasibility Studies & Make/Buy/COTS Tradeoffs
Key Takeaways Explain This Topic AI
Solution option evaluation requires rigorous multi-criteria appraisal across multiple viable alternatives, including doing nothing, process optimization, custom building, and commercial procurement.
The OTESL feasibility framework assesses proposed solutions across five critical dimensions: Operational, Technical, Economic, Schedule, and Legal/Regulatory feasibility.
Make vs. Buy vs. COTS/SaaS analysis weighs core intellectual property differentiation and custom workflows against commercial time-to-market, vendor roadmaps, and commodity standardized processes.
Total Cost of Ownership (TCO) extends far beyond initial acquisition and implementation fees to encompass ongoing software licensing, custom integrations, cloud consumption, annual maintenance, technical debt, and end-of-life migration.
Business analysts lead requirements-driven vendor evaluations by defining structured evaluation scorecards for RFIs/RFPs, facilitating vendor demonstrations, and executing time-boxed Proof of Concept (PoC) or technical spikes to eliminate architectural uncertainty.
Last updated: September 2026
3.3 Solution Option Evaluation: Feasibility Studies & Make/Buy/COTS Tradeoffs
Note
PMI-PBA Exam Context : In Needs Assessment, evaluating solution options and conducting feasibility studies represents the culmination of Domain 1 (Task 2 & Task 4). Exam questions frequently test your mastery of the OTESL feasibility dimensions , the strategic criteria governing Make vs. Buy vs. COTS/SaaS decisions, the "iceberg principle" of Total Cost of Ownership (TCO) , and the business analyst's role in conducting objective, requirements-driven vendor evaluations.
Once capability gaps are identified, the organization must decide how to bridge them. It is rare that only a single solution pathway exists. A mature business analysis practice generates and evaluates multiple viable solution options before committing capital.
The business analyst must never function as a rubber stamp for pre-selected solutions. Whether an executive is enamored with a vendor sales presentation or engineering is determined to build an in-house platform from scratch, the BA is responsible for executing a structured, objective, and data-driven Feasibility Analysis .
The OTESL Feasibility Framework
On the PMI-PBA exam, the primary standard for evaluating solution options is the OTESL Framework , which analyzes proposed solutions across five interdependent feasibility dimensions: ┌─────────────────────────────────────────┐
- │ The OTESL Feasibility Lens │
- └────────────────────┬────────────────────┘
- │
- ┌────────────────┬───────────────┼───────────────┬────────────────┐
- ▼ ▼ ▼ ▼ ▼
- Operational Technical Economic Schedule Legal/Regulatory
- Culture • Architecture • NPV / ROI • Deadlines • Data Privacy
- Change impact • Legacy APIs • CapEx / OpEx • Milestones• Licensing
- Usability • Scalability • 5-Year TCO • Resources • Compliance
- 1. Operational Feasibility
Evaluates how well the proposed solution fits the organization's existing culture, operational workflows, and human capabilities:
Will frontline employees embrace the new system, or will cultural resistance cause system abandonment?
Does the organization possess the operational maturity to execute new business processes?
What degree of organizational change management (OCM) and training is required?
2. Technical Feasibility
Assesses whether the solution can be engineered, integrated, and scaled within the enterprise's architectural and technological constraints:
Is the proposed technology mature and proven, or is it bleeding-edge and unverified?
Does internal IT have the requisite expertise to develop, maintain, and support the architecture?
Can the platform integrate seamlessly with existing legacy mainframes, enterprise data warehouses, and identity providers?
Can the system meet non-functional performance benchmarks (e.g., 10,000 transactions per second with sub-50ms latency)?
3. Economic Feasibility
Appraises the financial viability and business return of the solution:
Does the initiative generate a positive Net Present Value (NPV) and Return on Investment (ROI) across its projected lifecycle?
What is the discounted Payback Period?
Does the organization have sufficient capital expenditure (CapEx) or operational expenditure (OpEx) budget to fund the complete lifecycle?
4. Schedule Feasibility
Evaluates whether the solution can be successfully delivered within hard organizational or market deadlines:
Can the solution be fully deployed before critical statutory or compliance deadlines take effect (e.g., new federal reporting mandates)?
Are critical-path dependencies (e.g., third-party vendor integrations, data migration runs) achievable given current staffing levels?
5. Legal, Ethical, and Regulatory Feasibility
Ensures the proposed solution complies with all jurisdictional laws, industry mandates, and contractual obligations:
Does the solution comply with strict data residency and privacy statutes (e.g., GDPR, CCPA/CPRA, HIPAA)?
Are there intellectual property, patent infringement, or open-source licensing risks?
Does the architecture satisfy strict industry security standards (e.g., PCI-DSS, SOC 2 Type II, ISO 27001)?
The Make vs. Buy vs. COTS vs. SaaS Decision Dilemma
One of the most consequential strategic choices in solution option evaluation is selecting the delivery modality. The business analyst analyzes the trade-offs among four primary archetypes: +-------------------------------------------------------------------------------------+
- | Strategic Delivery Archetype Comparison |
- +-------------------------------------------------------------------------------------+
- | MODALITY | BEST SUITED FOR | PRIMARY ADVANTAGE / RISK |
- |-----------------+--------------------------------------+-----------------------------|
- | Custom Build | Core competitive advantage, highly | Max flexibility & IP control|
- | (Make) | proprietary algorithms/workflows. | / High CapEx & tech debt. |
- |-----------------+--------------------------------------+-----------------------------|
- | Commercial COTS | Standard industry processes hosted | Proven features & support |
- | (Buy On-Prem) | on-premise for deep data control. | / Customization lock-in trap|
- |-----------------+--------------------------------------+-----------------------------|
- | Cloud SaaS | Commodity enterprise functions | Rapid deployment & low CapEx|
- | (Cloud Service) | (CRM, HRIS, General Ledger). | / Loss of control & recurring|
- |-----------------+--------------------------------------+-----------------------------|
- | Business Process| Low-budget operational bottlenecks; | Zero software acquisition |
- | Optimization | non-technical root causes. | / Limited scalability. |
- +-------------------------------------------------------------------------------------+
- 1. Custom In-House Development ("Make")
Strategic Rationale : Pursued when the capability represents the company's core competitive differentiator —the proprietary "secret sauce" that distinguishes it in the marketplace (e.g., Amazon's recommendation engine, a hedge fund's high-frequency trading algorithm). Custom development provides total control over the architecture, user experience, and roadmap.
Associated Risks : High upfront Capital Expenditure (CapEx), lengthy delivery timelines, risk of software defects, and permanent organizational responsibility for maintenance, patching, security vulnerabilities, and legacy technical debt.
2. Commercial Off-The-Shelf ("Buy / COTS")
Strategic Rationale : Pursued when the business need centers on well-established enterprise workflows (e.g., ERP, warehouse management, billing). COTS solutions offer proven functionality, vendor product roadmaps, and peer-group testing.
The Dangerous "Customization Trap" : When organizations attempt to heavily customize COTS packages to match their legacy, idiosyncratic business processes, implementation costs skyrocket, future vendor upgrade pathways are broken, and the platform becomes an unmaintainable "Frankenstein" system. PMI-PBA best practice dictates that organizations adopt process re-engineering to match the COTS tool rather than customizing the COTS tool to match broken legacy processes.
3. Software-as-a-Service ("SaaS / Cloud")
Strategic Rationale : Modern enterprise standard for commodity business capabilities (e.g., Salesforce for CRM, Workday for HRIS). Rapid time-to-market, automated vendor-managed patching, zero local server maintenance, and shifts expenditures from upfront CapEx to predictable subscription OpEx.
Associated Risks : Long-term recurring subscription cost escalation, data residency and privacy concerns (data residing in multi-tenant cloud environments), reliance on vendor availability SLAs, and limited capability to customize specialized workflows.
4. Business Process Optimization (BPO / Lean Alternative)
Strategic Rationale : The business analyst must always evaluate whether a technology acquisition is truly necessary. Many performance gaps stem from bloated approval hierarchies, redundant manual handoffs, or ambiguous policies. Eliminating non-value-add steps through Lean or Six Sigma process re-engineering often resolves the need with zero software development.
Total Cost of Ownership (TCO): The Iceberg Principle
Executive decision-makers frequently fall victim to the visible price fallacy —comparing solutions solely on their initial acquisition or licensing quote. The business analyst counters this distortion by developing a comprehensive Total Cost of Ownership (TCO) model spanning a 3- to 5-year operational lifecycle. ▲
- / \ VISIBLE ACQUISITION COSTS (15 - 25%)
- / \ • Initial software licenses
- / \ • Base subscription fees / Hardware purchase
- /───────\ ◄───────────────────────────────────────────── [ Waterline ]
- / \
- / \ SUBMERGED OPERATIONAL & LIFECYCLE COSTS (75 - 85%)
- / \ • Custom integration & API middleware engineering
- / \• Data cleansing, ETL scripting, & legacy migration
- / \• User training, re-skilling, & change management (OCM)
- / \• Annual vendor maintenance fees (18-25% of license/yr)
- / \• Cloud infrastructure consumption & data egress
- / \• Technical debt remediation & future upgrades
- /─────────────────────────\• Eventual decommissioning & data archiving
Submerged Cost Categories to Model in TCO:
Integration and Customization : Developing and maintaining API connectors between the new platform and legacy enterprise systems.
Data Migration and Cleansing : Extracting, scrubbing, transforming, and validating millions of legacy records.
Annual Maintenance and Support : COTS software typically charges 18% to 25% of the initial perpetual license fee annually for maintenance, security patches, and support.
Infrastructure and Cloud Hosting : Compute instances, database storage, backup redundancy, network bandwidth, and disaster recovery hosting.
Organizational Change Management (OCM) : Developing training curriculums, conducting user workshops, productivity loss during the initial learning curve, and support desk staffing.
Decommissioning and Archiving : Costs associated with safely sunsetting legacy platforms, auditing data completeness, and paying long-term read-only archival storage.
Multi-Criteria Feasibility Comparison Matrix
To synthesize solution evaluations for executive steering committees, the business analyst builds a weighted Feasibility Comparison Matrix . The following matrix demonstrates how four alternative solution pathways were evaluated for an enterprise claims processing modernization:
Evaluation Dimension Weight Option 1: Custom In-House Build Option 2: Commercial COTS (On-Prem) Option 3: Cloud Multi-Tenant SaaS Option 4: Lean Process Re-Engineering
Operational Feasibility 20% Score: 4/5 ; Tailored perfectly to staff workflows; minimal operational friction. Score: 2/5 ; Forces massive workflow changes; strong employee pushback anticipated. Score: 4/5 ; Intuitive, modern UI; high user adoption in industry benchmarks. Score: 3/5 ; Eliminates redundant approvals, but manual paper handling remains.
Technical Feasibility 25% Score: 2/5 ; High technical risk; internal team lacks microservices & cloud expertise. Score: 4/5 ; Mature, proven enterprise architecture with pre-built legacy ERP connectors. Score: 5/5 ; Zero local server footprint; vendor manages high availability & updates. Score: 5/5 ; Zero technical risk; uses existing hardware and spreadsheets.
Economic (5-Yr TCO) 25% Score: 2/5 ; $7.8M 5-Yr TCO (High upfront dev + internal ongoing maintenance). Score: 3/5 ; $5.4M 5-Yr TCO ($2M license + 22% annual support + $1.5M integration). Score: 4/5 ; $3.9M 5-Yr TCO (Predictable OpEx subscription; low upfront CapEx). Score: 5/5 ; $450K 5-Yr TCO (Consulting & internal workshop fees only).
Schedule Feasibility 15% Score: 1/5 ; 24 months to MVP; exceeds statutory regulatory compliance deadline. Score: 3/5 ; 14 months deployment; tight alignment with compliance window. Score: 5/5 ; 5 months to production launch; easily beats regulatory deadline. Score: 4/5 ; 3 months rollout; fast execution but fails long-term volume scale.
Legal & Regulatory 15% Score: 5/5 ; Full internal data sovereignty; 100% compliance control. Score: 4/5 ; On-premise deployment satisfies state insurance privacy rules. Score: 4/5 ; SOC 2 Type II certified; requires business associate data agreements. Score: 2/5 ; Unencrypted spreadsheets violate upcoming statutory audit laws.
- Weighted Final Score 100% 2.65 / 5.00 3.15 / 5.00 4.35 / 5.00 (RECOMMENDED) 3.85 / 5.00
- Requirements-Driven Vendor Evaluation and Proof of Concept (PoC)
When solution options involve commercial software or third-party cloud vendors, the business analyst plays a pivotal role in ensuring that vendor selection is driven by validated requirements , not vendor sales showmanship. Requirements Baseline (Functional & Non-Functional)
- │
- ▼
- Request for Information (RFI) ──> Broad market research (5 to 10 vendors)
- │
- ▼
- Request for Proposal (RFP) ──> Detailed scoring against weighted requirements (Shortlist 3)
- │
- ▼
- Scripted Vendor Demonstrations──> Standardized business scenarios with identical test data
- │
- ▼
- Proof of Concept (PoC Spike) ──> Time-boxed technical test of high-risk integrations
- │
- ▼
- Final Vendor Contract & Business Case Approval
Best Practices for Vendor Evaluations:
Standardized Scripted Demonstrations : Never allow software vendors to present generic marketing demonstrations. The BA develops detailed, scripted operational scenarios containing representative enterprise data, requiring each competing vendor to execute identical business processes during their presentation.
RFI vs. RFP vs. RFQ : Understand the distinct procurement instruments: RFI (Request for Information) gathers broad market capabilities; RFP (Request for Proposal) evaluates detailed technical and functional compliance against weighted requirements; RFQ (Request for Quote) focuses strictly on commercial pricing and SLA terms.
Proof of Concept (PoC) and Technical Spikes : For critical architectural questions—such as whether a SaaS platform can ingest 50,000 records/minute across the enterprise firewall—the BA collaborates with architects to execute a time-boxed (e.g., 2-week) PoC to test and eliminate high-risk technical assumptions prior to contract execution.