SAFe-Agilist Exploring Lean Portfolio Management Practice Question
Which THREE items are typically included in an Epic Hypothesis Statement? (Select three)
⚠ Common exam trap
Candidates often include 'Features' or 'User Stories' as part of the Epic Hypothesis Statement. These are implementation details, not part of the hypothesis itself, which focuses on outcomes and indicators.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The business outcome hypothesis.
The Epic Hypothesis Statement is a critical tool for ensuring that every investment is backed by a clear business outcome and a way to measure success. By defining the 'Leading Indicators' and 'Business Outcomes,' the portfolio team ensures that they are not just building features but actually solving customer problems. This structured approach helps prevent the waste of building unproven ideas and keeps the organization focused on delivering real value.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The business outcome hypothesis.
Why this is correct
The business outcome hypothesis clearly articulates the expected improvement, such as increased revenue or reduced churn. This is essential for aligning the epic with strategic goals and ensuring that the investment has a defined, measurable objective, preventing the development of features that do not provide clear business value.
- ✗
The detailed technical design specification.
Why it's wrong here
Technical design specifications are too granular and premature for an Epic Hypothesis Statement. Including them creates a false sense of certainty and limits the team's ability to innovate or pivot based on what they learn during the initial implementation phases of the epic, which contradicts Agile's iterative approach.
- ✓
The leading indicators.
Why this is correct
Leading indicators provide early signals about whether the epic is on the right track before the final business outcomes are fully realized. These metrics allow the portfolio team to make data-driven decisions about whether to pivot, persevere, or stop the epic based on real-world usage and performance data.
- ✗
The non-functional requirement list.
Why it's wrong here
While non-functional requirements are important for any system, they are not a core component of the Epic Hypothesis Statement. This document is focused on the 'why' and 'what' of a business value proposition, whereas non-functional requirements are usually captured in the backlog or system architectural documentation as separate constraints.
- ✓
The statement of the problem.
Why this is correct
The problem statement is the foundation of the hypothesis, as it clearly defines the customer pain point that the epic intends to address. Without a well-defined problem, it is impossible to formulate a valid hypothesis or measure the success of the investment, leading to wasted effort and misaligned development.
About these practice questions
Courseiva writes every SAFe-Agilist question from scratch — 315 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SAFe-Agilist practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAFe-Agilist exam.