Entry Certificate in Business Analysis™ (ECBA™) — Lesson 3: Requirements Lifecycle, Prioritization, Traceability, and Design Options

Learning Objectives

• Translate requirement quality, acceptance criteria, and prioritization methods into actions that can be implemented and verified.
• Compare viable approaches to traceability relationships and document their effect on solution options.
• Determine the appropriate response when high-priority requirements have no traceable outcome, owner, or acceptance evidence.

Detailed Topics

• Clarify requirement quality by identifying purpose, ownership, boundaries, dependencies, and decision criteria.
• Apply acceptance criteria to the scenario and preserve the evidence supporting the selected approach.
• Compare alternatives for prioritization methods and explain practical value, risk, and operating consequences.
• Challenge traceability relationships with a realistic exception that exposes assumptions or weak accountability.
• Document solution options with acceptance conditions, review responsibility, and a clear next action.

Instructor Demonstration

The instructor demonstrates how to write and prioritize requirements, connect them to the business need, and compare possible responses. The walkthrough explains which requirements and solution option should move forward for detailed delivery, builds the prioritized requirements catalogue and option assessment, and tests the exception where high-priority requirements have no traceable outcome, owner, or acceptance evidence.

Hands-On Exercise

Complete a controlled exercise to write and prioritize requirements, connect them to the business need, and compare possible responses and preserve the result in the prioritized requirements catalogue and option assessment.

1. Confirm the facts, stakeholders, constraints, evidence sources, and success conditions relevant to requirement quality.
2. Perform the central analysis involving acceptance criteria, prioritization methods, and traceability relationships.
3. Introduce the exception where high-priority requirements have no traceable outcome, owner, or acceptance evidence and revise the proposed response.
4. Complete the prioritized requirements catalogue and option assessment with ownership, acceptance evidence, unresolved concerns, and follow-up actions.

Scenario Analysis

• Identify the assumption with the greatest influence on which requirements and solution option should move forward for detailed delivery.
• Compare two defensible responses involving traceability relationships and explain their trade-offs.
• Specify the evidence required before the prioritized requirements catalogue and option assessment can be accepted.

Troubleshooting Guidance

Trace the first difference between the intended outcome and the available evidence. Recheck scope, roles, source quality, dependencies, decision criteria, and retained records independently. The analysis remains incomplete while high-priority requirements have no traceable outcome, owner, or acceptance evidence.

Validation Checklist

• Scope and ownership for requirement quality are explicit.
• The selected treatment for acceptance criteria is supported by reviewable evidence.
• The exception involving traceability relationships was tested and its impact recorded.
• The prioritized requirements catalogue and option assessment contains acceptance criteria, accountable owners, and next actions.

Lesson Outcome

Learners can apply Requirements Lifecycle, Prioritization, Traceability, and Design Options, explain which requirements and solution option should move forward for detailed delivery, and support the conclusion with a prioritized requirements catalogue and option assessment.