Study guide
12.1 Constructing & Maintaining the Requirements Traceability Matrix (RTM)
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)
12.1 Constructing & Maintaining the Requirements Traceability Matrix (RTM)
Key Takeaways Explain This Topic AI
ECO Domain 4 Task 1 mandates tracking requirements throughout their lifecycle using formal traceability techniques to maintain continuous alignment with authorized business needs and project scope.
The structural architecture of a production-grade Requirements Traceability Matrix (RTM) links business objectives directly to functional specifications, technical architecture components, source code modules, and verification test cases.
Bidirectional traceability enforces dual lineage: forward traceability guarantees complete scope realization and verification coverage, while backward traceability justifies every technical deliverable by linking it back to an approved business need.
Requirements dependency modeling categorizes structural interrelationships—such as parent-child, prerequisite, enables, and conflicts-with—enabling precise blast-radius calculations during change impact analysis.
Continuous RTM audits detect and eliminate critical governance anomalies, including orphan deliverables (untraced code representing gold plating) and verification deficits (approved requirements lacking test coverage).
Last updated: September 2026
12.1 Constructing & Maintaining the Requirements Traceability Matrix (RTM)
Note
PMI-PBA Examination Alignment : Domain 4 (Traceability and Monitoring) accounts for 15% of all scored examination questions (~26 questions). Within Domain 4, Task 1 establishes the foundational mandate: "Track requirements throughout their lifecycle using traceability techniques to ensure requirements continue to satisfy the business need and align with project scope." Candidates are heavily evaluated on their ability to design production-grade traceability matrices, manage forward and backward lineage, evaluate complex dependency networks during change impact analysis, and audit matrices to expose orphaned code and uncovered specifications.
The Strategic Mandate of Traceability in Business Analysis
In complex enterprise systems, requirements do not exist in isolation. A single high-level business objective typically spawns dozens of stakeholder requirements, which decompose into hundreds of functional specifications, which in turn drive architectural decisions, database schemas, code commits, and verification suites. Without a rigorous, formalized mechanism to manage these interconnections, projects inevitably succumb to architectural fragmentation, unmanaged scope drift, test coverage blind spots, and expensive compliance failures.
Under The PMI Guide to Business Analysis and Business Analysis for Practitioners: A Practice Guide , requirements traceability is defined as the ability to track the life of a requirement in both forward and backward directions—from its initial conception in the business case, through its elaboration, design, specification, development, and testing, to its ultimate operational deployment and maintenance.
Traceability transforms requirements management from a disconnected documentation exercise into a dynamic, auditable engineering discipline. It serves five primary enterprise functions:
Scope Realization Verification : Verifying that 100% of approved, baselined requirements are actually designed, constructed, and verified in the delivered software product.
Defensive Scope Governance : Ensuring that no unauthorized, out-of-scope, or gold-plated capabilities enter the solution without formal review and approval.
Precision Change Impact Analysis : Empowering the business analyst and technical leads to determine the exact "blast radius" across architectural components, code branches, and test suites whenever a requirement is modified, added, or retired.
Regulatory and Statutory Compliance : Delivering an immutable, audit-ready chain of custody demanded by federal and global regulatory standards (e.g., FDA 21 CFR Part 11, ISO 9001, DO-178C, Basel III, HIPAA, PCI-DSS).
Maintenance and Defect Triage Efficiency : Accelerating defect root-cause analysis during quality assurance and operational production by tracing software faults directly back to the governing business rule or requirement statement.
Bidirectional Traceability Mechanics: Forward versus Backward Lineage
True traceability is never a one-way street. The PMI-PBA standard strictly enforces bidirectional traceability , which demands two distinct, concurrent paths of lineage across the entire solution lifecycle: +===================================================================================================+
- | BIDIRECTIONAL TRACEABILITY ARCHITECTURE |
- +===================================================================================================+
- | |
- | [ Business Need / Strategic Goal ] <======================================================+ |
- | │ │ |
- | ▼ (Forward Lineage) │ |
- | [ Stakeholder Requirement ] │ |
- | │ │ |
- | ▼ (Forward Lineage) │ |
- | [ Solution Requirement (Functional / NFR) ] │ |
- | │ │ |
- | ▼ (Forward Lineage) │ |
- | [ Architecture / Design Specification ] │ |
- | │ │ |
- | ▼ (Forward Lineage) │ |
- | [ Source Code / Implementation Build ] │ |
- | │ │ |
- | ▼ (Forward Lineage) │ |
- | [ Test Cases / Verification Suites ] │ |
- | │ │ |
- | ▼ (Forward Lineage) │ |
- | [ Operational Deliverable / Deployed System ] ─── (Backward Lineage: Proof of Justification) ────┘ |
- | |
- +===================================================================================================+
- 1. Forward Traceability (Requirement-to-Deliverable & Verification)
Direction : Originates at the high-level business need and moves forward through stakeholder requirements, solution specifications, technical designs, software code commits, and verification test cases.
Governing Question : "Has every approved requirement been fully realized, constructed, and verified in the downstream deliverables?"
Primary Purpose : To guarantee completeness of delivery . Forward traceability ensures that no authorized requirement is dropped, forgotten, or partially implemented during the chaos of development.
Verification Linkage : A critical sub-dimension of forward traceability is traceability-to-test . Every functional and non-functional requirement must trace forward to one or more test cases, verification scripts, or user acceptance scenarios. If a requirement has no mapped test case, it cannot be verified, leaving the enterprise vulnerable to deploying defective code.
2. Backward Traceability (Deliverable-to-Origin & Business Need)
Direction : Originates at any downstream technical artifact—a source code class, an API endpoint, a database stored procedure, a user interface widget, or a test case—and traces backward to the approved solution requirement, stakeholder request, and foundational business objective that justified its existence.
Governing Question : "Why does this technical deliverable exist, who requested it, and what authorized business goal does it serve?"
Primary Purpose : To defend the enterprise against gold plating, unauthorized scope additions, and technical rogue features . If a developer writes a brilliant piece of software functionality that cannot be traced backward to an approved requirement, that code is unauthorized, represents unvetted risk, and violates project governance.
Structural Architecture of an Enterprise RTM
A Requirements Traceability Matrix (RTM) is the primary physical or digital artifact utilized by the business analyst to record, maintain, and navigate bidirectional traceability. While simple projects may track basic links, enterprise programs operating in mission-critical or regulated environments require a multi-column, production-grade schema.
A compliant enterprise RTM must incorporate the following ten mandatory structural columns:
Requirement Identifier (Req ID) : A persistent, unique alphanumeric key assigned at elicitation that never changes throughout the project lifecycle (e.g., REQ-PAY-001 ). Sub-requirements use dot-notation (e.g., REQ-PAY-001.1 ).
Requirement Description : An atomic, unambiguous, testable statement specifying the required system capability, constraint, or business rule (typically phrased using RFC 2119 imperative language: "The system shall..." ).
Requirement Category / Classification : Categorizes the requirement type in accordance with PMI-PBA taxonomy: Business Requirement, Stakeholder Requirement, Solution Requirement (Functional or Non-Functional), or Transition Requirement.
Originating Source / Business Need : The formal document, business case metric, problem statement, or statutory regulation from which the requirement emerged (e.g., Charter-OBJ-02 , BRD-Sect-4.1 , PCI-DSS-Req-3.4 ).
Stakeholder Requester / Owner : The designated business sponsor, SME, or organizational stakeholder who authored, championed, and accepts accountability for the requirement.
WBS Work Package / Delivery Component : The specific Work Breakdown Structure (WBS) deliverable code, Epic identifier, or Jira ticket tracking the execution of the requirement (e.g., WBS 1.4.2.3 , EPIC-882 ).
Architecture & Design Specification : The technical design document, UML diagram, API schema contract, or wireframe detailing how the requirement is engineered (e.g., HLD-ARCH-Sect-5.2 , API-Endpoint-v2-Tokenize ).
Implementation Artifact / Code Commit : The version-controlled source code repository path, pull request (PR) number, or build version containing the compiled logic (e.g., PR #1409 , git:commit:a7f4c92 , Build-v3.1.0-RC2 ).
Verification / Test Case ID : The formal test script, automated regression suite class, or UAT scenario that proves the requirement meets its acceptance criteria (e.g., TC-SEC-104 , TestTokenizeCreditCard.java ).
Lifecycle Status : The real-time governance state of the requirement (e.g., Proposed , In Review , Approved , In Architecture , In Build , In Test , Verified , Accepted , Deferred , Rejected ).
Complete Production-Grade Requirements Traceability Matrix (RTM) Table
The following table illustrates a complete, production-grade RTM for an enterprise Omnichannel Payment Processing Platform, demonstrating multidimensional bidirectional traceability across business, functional, architectural, implementation, and verification domains:
Req ID Requirement Description Req Type Originating Business Need Stakeholder Owner WBS / Epic ID Design / Architecture Spec Code Commit / Build Artifact Test Case ID Lifecycle Status
REQ-PAY-001 The payment gateway shall tokenize primary account numbers (PAN) using AES-256 vaultless tokenization prior to database persistence. Solution: Functional Strategic Objective 1: Zero data breach liability; PCI-DSS Level 1 compliance VP of InfoSec & Compliance WBS 1.4.2: Payment Ingestion Engine HLD-SEC-04: Crypto & Tokenization Architecture git:repo/pay:c89e1a (PR #342) TC-PAY-0101 (Automated Vaultless Encryption Test) Verified (Passed UAT)
REQ-PAY-002 The payment gateway shall process high-volume card authorizations with a 99th-percentile response latency not exceeding 400 milliseconds. Solution: Non-Functional (Performance) Strategic Objective 2: Maximize retail checkout throughput (< 0.1% cart abandonment) Director of Digital Retail Channels WBS 1.4.5: High-Speed Transaction Router HLD-PERF-08: In-Memory Redis Routing Topology git:repo/router:d42b7e (Build v2.1.4) TC-PERF-0205 (JMeter 10,000 TPS Load Test) Verified (Latency avg 312ms)
REQ-PAY-003 The system shall evaluate transaction payloads against real-time fraud scoring models and decline transactions with risk scores exceeding 85. Solution: Functional Strategic Objective 3: Reduce annual card-not-present fraud chargebacks by 35% Chief Risk Officer (CRO) WBS 1.4.8: AI Risk Decision Engine HLD-AI-02: Streaming Kafka Machine Learning Spec git:repo/risk:f990a1 (PR #512) TC-RISK-0311 (Synthetic Fraud Pattern Suite) In Test (QA Stage)
REQ-PAY-004 The system shall generate daily multi-currency settlement batches partitioned by acquiring banking partner at 23:59:59 UTC. Solution: Functional Business Case: Eliminate manual treasury reconciliation and $450K annual FX leakage Corporate Treasury Controller WBS 1.5.1: Treasury Reconciliation Ledger HLD-LED-06: Batch Settlement & Clearing Pipeline git:repo/ledger:b112c3 (PR #608) TC-TREAS-0402 (Cross-Border Batch Run Test) Approved (In Development)
REQ-PAY-005 The payment gateway shall queue offline transactions locally for up to 72 hours when primary cloud connectivity is severed, auto-replaying upon restore. Solution: Functional (Resilience) Retail Ops Need: Guarantee store continuity during regional ISP network outages VP of Retail Store Operations WBS 1.4.9: Edge Store Controller Pipeline HLD-EDGE-09: Local SQLite Store-and-Forward Spec Pending Architecture Sign-off TC-RESIL-0501 (Simulated WAN Cable Disconnect) In Review (Architecture Phase)
REQ-PAY-006 The checkout application shall comply with WCAG 2.2 Level AA accessibility standards, supporting full keyboard navigation and screen reader tags. Solution: Non-Functional (Accessibility) Legal Mandate: Americans with Disabilities Act (ADA) statutory compliance Chief Legal Counsel WBS 1.3.2: Omnichannel Customer Checkout UI UI-SPEC-ACC-03: Semantic HTML & ARIA Landmarks git:repo/web-ui:a1029c (PR #784) TC-ACC-0601 (Axe-core & Screen Reader Audit) Verified (Zero Critical Violations)
Modeling Complex Requirement Dependencies
Requirements rarely progress in isolation; they exist within a complex, interconnected dependency graph. Certified PMI-PBA practitioners do not merely track one-to-one linear relationships; they model the specific structural topology of how requirements interact. Understanding these dependency types is essential for conducting accurate change impact analysis: [ High-Level Business Need ]
- │
- ▼ (Decomposition / Parent-Child)
- [ REQ-01: Payment Processing ]
- │
- ┌──────────────────────┼──────────────────────┐
- │ (Parent-Child) │ (Parent-Child) │ (Parent-Child)
- ▼ ▼ ▼
- [ REQ-01a: Auth ] [ REQ-01b: Capture ] [ REQ-01c: Settle ]
- │ ▲
- │ (Prerequisite) │
- └──────────────────────┘ (REQ-01a must execute before REQ-01b can occur)
[ REQ-02: Biometric Auth ] ──(Enables)──> [ REQ-03: Zero-Click 1-Tap Checkout ]
- [ REQ-04: Sub-Second SLA ] <..(Conflicts-With)..> [ REQ-05: 4-Pass Deep Malware Scan ]
- Core Dependency Classifications
Parent-Child (Hierarchical Decomposition) :
Represents vertical decomposition where a broad stakeholder requirement or epic (Parent) is broken down into multiple detailed functional specifications (Children).
Governance Rule : A parent requirement cannot be marked as "Verified" or "Accepted" until 100% of its child requirements have passed verification.
Prerequisite / Depends-On (Precedence Constraint) :
An operational or technical dependency where Requirement B cannot be designed, built, or executed until Requirement A is fully realized.
Example : REQ-CAPTURE-02 (Capture Funds) has a strict prerequisite dependency on REQ-AUTH-01 (Authorize Transaction). One cannot capture funds that have not been pre-authorized.
Enables / Facilitates (Capability Multiplier) :
Requirement A is not strictly mandatory for Requirement B to function, but the presence of Requirement A significantly enhances, accelerates, or optimizes Requirement B.
Example : Implementing REQ-BIOMETRIC-01 (Fingerprint Biometric Authentication) enables REQ-ONECLICK-04 (Frictionless Mobile Checkout), unlocking higher conversion rates.
Conflicts-With / Constrains (Architectural Trade-Off) :
Two requirements pull the system architecture in opposing directions, creating an engineering tension that requires documented trade-offs and explicit stakeholder compromise.
Example : REQ-PERF-01 (Mandating sub-200ms transaction latency) directly conflicts with REQ-SEC-09 (Mandating multi-layer cryptographic hashing and external anti-money laundering sanction list API queries). The business analyst must model this conflict to facilitate executive agreement on performance versus risk thresholds.
Navigating the Dependency Graph for Change Impact Analysis
When an executive sponsor or client submits a change request modifying an existing requirement, the business analyst uses the RTM's dependency network to calculate the blast radius :
Downstream Traversal : Tracing from the modified requirement down to all child specifications, technical designs, code commits, and test suites that must be refactored.
Upstream Traversal : Tracing from the modified requirement back to the business objective to ensure the proposed change does not invalidate the original business case or violate statutory constraints.
Lateral Traversal : Tracing through prerequisite, enabled, and conflicting dependencies to identify secondary systems or functional modules that will experience ripple effects or performance degradation.
Manual Spreadsheets versus Automated ALM Traceability Engines
While small, low-complexity projects occasionally track requirements using desktop spreadsheets (e.g., Microsoft Excel), enterprise projects quickly overwhelm manual tools. The PMI-PBA candidate must understand the structural trade-offs between manual matrices and modern Application Lifecycle Management (ALM) platforms:
Capability Dimension Manual Matrix (Excel / Google Sheets) Enterprise ALM Platform (Jira Align, Azure DevOps, DOORS, Polarion)
Scalability & Volume Degrades rapidly beyond 200 requirements; multi-tab spreadsheets become unmanageable. Horizontally scalable; effortlessly manages tens of thousands of requirements, epics, and user stories.
Concurrency & Collaboration Severe file-locking, overwrite conflicts, and version fragmentation ("RTM_v2_final_FINAL.xlsx"). Real-time multi-user concurrency with role-based access control, fine-grained locking, and audit logs.
Bidirectional Dynamic Linking Manual string copying of IDs; hyperlinking is fragile and breaks upon document renaming. Object-oriented dynamic relationships; bi-directional links update automatically across all views.
Version History & Baselining Manual "Save As" snapshots; impossible to compare historical deltas between versions systematically. Automated cryptographic snapshot baselining; instant side-by-side delta visualization across any two historical baselines.
CI/CD & DevOps Integration Completely disconnected from engineering pipelines; manual updates require developer self-reporting. Native API integration with Git, GitHub, GitLab, Jenkins, and Azure Pipelines; commits auto-link to Req IDs upon merge.
Automated Impact Analysis Analyst must manually scan hundreds of rows; high risk of missing secondary dependencies. Graph-database dependency mapping; one-click visual blast-radius reporting for any proposed change.
Regulatory Audit Compliance Frequently rejected by rigorous auditors (FDA, FAA, SEC) due to lack of tamper-proof audit trails. Fully compliant with FDA 21 CFR Part 11, ISO 9001, and DO-178C electronic signature and immutable logging standards.
Auditing the RTM: Catching Governance Anomalies
A primary responsibility of the business analyst under ECO Domain 4 Task 1 is conducting periodic, rigorous RTM audits . These audits inspect the matrix for structural integrity and expose three dangerous governance anomalies: RTM AUDIT DEFECT TOPOLOGY
- [ 1. Orphan Deliverable ] [ 2. Coverage Deficit ] [ 3. Dead-End Requirement ]
- ┌─────────────────────────┐ ┌─────────────────────────┐ ┌─────────────────────────┐
- │ Source Code / Commit │ │ Approved Requirement │ │ Child Specification │
- │ (Exists in Repository) │ │ (Baselined in RTM) │ │ (Dangling in RTM) │
- └────────────┬────────────┘ └────────────┬────────────┘ └────────────┬────────────┘
- │ (No Backward Lineage) │ (No Forward Lineage) │ (No Parent Link)
- ▼ ▼ ▼
- ┌─────────────────────────┐ ┌─────────────────────────┐ ┌─────────────────────────┐
- │ [ NO PARENT REQ ] │ │ [ NO TEST CASE ] │ │ [ NO PARENT EPIC ] │
- │ GOLD PLATING │ │ UNTESTED SOFTWARE │ │ UNALIGNED FEATURE │
- │ (Unauthorized Risk) │ │ (Quality Defect) │ │ (Architectural Waste) │
- └─────────────────────────┘ └─────────────────────────┘ └─────────────────────────┘
- 1. Orphan Deliverables (Gold Plating & Rogue Code)
The Anomaly : Source code files, API endpoints, microservices, or database tables exist in the repository but have no backward traceability link to an approved, baselined requirement or business objective.
The Root Cause : Developers "helpfully" built unrequested features during spare capacity, engineered speculative functionality for future use, or responded to verbal hallway requests from informal stakeholders.
The Business Risk : Introduces unvetted, untested code paths; increases cybersecurity attack surfaces; inflates ongoing maintenance and refactoring costs; and misallocates capital away from authorized deliverables.
BA Corrective Action : Investigate code provenance immediately. If the code serves an undocumented, valid business need, halt development and route a formal change request through the Change Control Board (CCB) for retrofitted evaluation. If the code provides no strategic value, require engineering to remove it from the build branch.
2. Coverage Deficits (Untested Requirements)
The Anomaly : An approved, baselined requirement has downstream architectural designs and code commits, but possesses zero forward traceability links to test cases or verification scenarios .
The Root Cause : The QA team lacked time to author test scripts; the requirement was written ambiguously without testable acceptance criteria; or testing was bypassed due to aggressive schedule pressure.
The Business Risk : The system cannot be validated. Deploying untested code into production results in catastrophic operational failures, regulatory compliance fines, and data corruption.
BA Corrective Action : Flag the coverage deficit as a blocking quality gate defect. Collaborate with the QA lead and technical architect to draft objective, testable verification scripts mapped directly to the requirement's acceptance criteria before permitting UAT sign-off.
3. Dead-End Requirements (Dangling & Detached Specs)
The Anomaly : Granular functional requirements or user stories exist in the backlog or RTM that do not trace upward to an authorized parent feature, business objective, or charter goal.
The Root Cause : Disconnected brainstorming sessions; unpruned backlog debt; or remnants of canceled project initiatives.
BA Corrective Action : Perform backlog pruning. Challenge the business value of detached specifications and formally retire or archive them unless an explicit business case justification is established.