Try 10 focused SAFe Agilist questions on Exploring Lean Portfolio Management (LPM), with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | SAFe Agilist |
| Topic area | Exploring Lean Portfolio Management (LPM) |
| Blueprint weight | 28% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Exploring Lean Portfolio Management (LPM) for SAFe Agilist. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 28% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Exploring Lean Portfolio Management (LPM)
An ART reports that a new portfolio approval step (a monthly investment review board) is delaying work from starting in the current PI. Leaders want to “fix the process,” but the request is vague and opinions differ on whether governance is the real bottleneck.
What information should you obtain first to decide on a Lean portfolio alternative?
Best answer: C
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Before changing portfolio governance, first confirm what work the approval step is actually blocking and what it costs the business to wait. Quantifying the impact on PI objectives/flow and the cost of delay enables an economic decision and supports Lean alternatives like delegating decisions with guardrails. Without that, you risk optimizing a perceived bottleneck instead of the real constraint.
In Lean Portfolio Management, portfolio decisions should improve flow, not create systemic delays for ARTs. When a new approval step appears to be a bottleneck, the first move is to clarify the economic impact: which PI objectives/features are waiting, how long they wait, and what the cost of delay is. With that information, you can compare the value of the control (risk reduction, spend governance) against the delay it introduces and choose a Lean alternative such as Lean budgets with guardrails, smaller batch approvals through the portfolio Kanban, or delegating decision authority closer to where information is.
If you can’t connect the approval delay to blocked value and measurable economic trade-offs, you can’t make a sound Lean change to portfolio governance.
You need the specific flow impact and economic trade-off to justify changing decision cadence/authority using Lean budgets and guardrails.
Topic: Exploring Lean Portfolio Management (LPM)
A portfolio epic is proposed to increase digital loan completion. The epic hypothesis states: “If we reduce application rework with guided data entry, then completed applications will increase by 8% within one PI.” The ART plans a feature: “Add guided data entry to the loan form.”
Which evidence best validates progress toward the epic hypothesis (not just feature delivery)?
Best answer: A
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: An epic hypothesis statement is validated by measurable outcomes that confirm or refute the predicted business result. The best evidence is data from a release or pilot showing the targeted increase in completed applications, because it directly tests the hypothesis rather than confirming that the feature was built.
In SAFe, a feature description explains what will be built, while an epic hypothesis statement predicts a measurable outcome (e.g., “if we do X, then Y will improve by Z”). Validation evidence for the epic should therefore be outcome-based metrics collected from real use (or a controlled pilot) that demonstrate whether the prediction is true.
Good validation evidence typically:
A System Demo and delivery progress can confirm the feature exists, but they do not by themselves validate the hypothesized business impact.
It measures the hypothesized business outcome (completion increase) rather than the output of building the feature.
Topic: Exploring Lean Portfolio Management (LPM)
Midway through a PI, the portfolio reviews spend monthly and funds work as individual projects tied to specific components. Teams start prioritizing “their” funded projects over cross-ART features, even when business priorities change.
As a SAFe Agilist, what is the most appropriate next step to reduce this local optimization?
Best answer: B
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Project-and-component-based funding creates incentives to protect local budgets instead of optimizing end-to-end value. Lean budgeting reduces this by funding value streams and empowering decentralized decisions within explicit guardrails. That allows investment to shift as priorities change while maintaining governance and alignment.
The core issue is that project/component funding drives local optimization: teams are rewarded for maximizing spend and scope within their own budget lines, even when the best outcome requires shifting investment across components or ARTs. Lean budgeting addresses this by moving from project funding to value stream (or portfolio) budgets and enabling decentralized decision-making.
A practical next step is to:
This combination keeps governance in place while reducing “use it or lose it” behavior and enabling faster portfolio flow.
Funding value streams (not projects) and setting Lean budget guardrails enables shifting spend to the highest-value work without component-level gaming.
Topic: Exploring Lean Portfolio Management (LPM)
A portfolio wants to launch “Instant Credit Decisioning” to increase approval conversion this year. Analysis shows it also requires upgrading the decisioning platform to support near-real-time data, model monitoring, and auditability. Funding is managed through Lean budgets with guardrails, and leadership wants fast learning without creating hidden work queues.
Which option best optimizes value delivery and flow while maintaining quality and alignment?
Best answer: A
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Business epics deliver direct customer or business outcomes, while enabler epics build the architectural, infrastructure, or compliance capabilities that make those outcomes feasible and sustainable. Here, “Instant Credit Decisioning” is the outcome to validate, and the platform upgrade is enabling work that should be made visible and prioritized, not hidden. Managing them as separate epics improves flow, decision-making, and guardrail compliance.
In Lean Portfolio Management, epics are used to govern and sequence significant investments through the Portfolio Kanban. A business epic is defined by the business outcome it will achieve (e.g., higher conversion from instant decisions) and is validated with leading indicators and an MVP. An enabler epic is created when meaningful architectural/infrastructure/compliance work is required to support business epics and portfolio objectives.
The flow-optimizing approach is to:
Bundling or hiding enabling work typically delays feedback and creates unmanaged queues and unplanned dependencies.
The customer-facing outcome is a business epic, while the platform upgrade is an enabler epic that supports it and should be prioritized transparently through the Portfolio Kanban.
Topic: Exploring Lean Portfolio Management (LPM)
During an LPM review, four portfolio epics are ready to be sequenced. Cost of Delay is estimated per week (USD), and job size is a relative estimate.
Using WSJF (Cost of Delay / Job Size), which epic should be prioritized first?
| Epic | Cost of Delay (per week) | Job size |
|---|---|---|
| Improve mobile checkout | $500,000 | 10 |
| Consolidate vendor contracts | $800,000 | 25 |
| Automate compliance reporting | $360,000 | 6 |
| Upgrade data platform | $1,000,000 | 30 |
Best answer: C
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: At portfolio level, WSJF sequences epics by maximizing economic outcomes: prioritize the work with the highest cost of delay per unit of job size. Computing CoD/job size identifies which epic delivers the most urgency-weighted value for the investment. The epic with the largest WSJF should be pulled next in the portfolio flow.
WSJF is used in Lean Portfolio Management to sequence epics by comparing the economic impact of waiting (Cost of Delay) against how big the work is (Job Size). To apply it, calculate a WSJF score for each epic:
Here, Automate compliance reporting has WSJF \(360{,}000/6 = 60{,}000\), which is higher than Improve mobile checkout \(50{,}000\), Upgrade data platform \(33{,}333\), and Consolidate vendor contracts \(32{,}000\). The key takeaway is that the biggest CoD is not automatically the best choice—WSJF favors the best CoD-to-size ratio.
It has the highest WSJF because its cost of delay per unit of job size is greatest.
Topic: Exploring Lean Portfolio Management (LPM)
A portfolio has proposed a new “AI-assisted claims triage” epic. It aligns to a strategic theme, but benefits, leading indicators, and architecture impact are unclear. A senior leader wants the ART to “start building now” to beat a competitor.
What is the best next step to optimize value delivery and flow while distinguishing epic analysis from implementation?
Best answer: B
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Epic analysis is where the portfolio reduces uncertainty enough to decide whether the epic is worth implementing and how to fund and prioritize it. Completing a Lean business case with a clear hypothesis, MVP, measurable outcomes, and key enabler considerations enables a fast, high-quality go/no-go decision. Only then should the epic be pulled into implementation by the ART within capacity and guardrails.
In SAFe portfolio flow, analyzing an epic is intentionally different from implementing it. During analysis, the portfolio uses the Portfolio Kanban to quickly validate the opportunity and reduce risk: clarify the hypothesis and intended outcomes, define an MVP and leading indicators, identify major enabler/architecture impacts, and compare economics (often via cost of delay/WSJF) within lean budgeting guardrails. The key decisions in analysis are whether to proceed (go/no-go), what success measures will be used, and whether capacity/funding is available.
Implementation starts only after that decision, when the epic is pulled into implementation and decomposed into features for ART backlogs and PI planning, where delivery occurs within normal flow and quality practices. The closest trap is “start building now,” which increases unmanaged rework and disrupts flow.
Analysis clarifies value, measures, and feasibility so the portfolio can make an informed go/no-go and capacity decision before pulling work into implementation.
Topic: Exploring Lean Portfolio Management (LPM)
A portfolio epic has an approved Lean business case with the hypothesis: “If we offer self-serve account onboarding, at least 30% more trial users will activate within 7 days.” After a small MVP is built and released to a limited audience, LPM is deciding whether to scale funding.
What evidence is the best SAFe-aligned input to validate the epic hypothesis before scaling investment?
Best answer: D
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Before scaling an epic, SAFe emphasizes validating the hypothesis with objective, measurable outcomes from a small MVP. The most relevant evidence is whether the MVP moved the leading indicator tied to the hypothesis for the intended users. That validated learning informs persevere, pivot, or stop decisions in the portfolio Kanban.
In SAFe LPM, epics are meant to reduce uncertainty through incremental investment and validated learning. The epic hypothesis states an expected change in a measurable outcome (a leading indicator), so the strongest evidence is real MVP outcome data compared to the hypothesis and baseline, gathered from the intended audience and context. This is the key input for deciding whether to scale funding (persevere), adjust the approach (pivot), or end the investment (stop).
Evidence to gather should be:
Plans, opinions, or readiness work may be useful, but they do not validate whether the epic will produce the promised business outcome.
Validated learning from MVP outcomes against the hypothesis’ leading metric is the most direct evidence to justify scaling investment.
Topic: Exploring Lean Portfolio Management (LPM)
In an LPM workshop, you are reviewing draft statements to ensure they are written as epic hypothesis statements. Which statement is NOT an epic hypothesis statement (i.e., it reads like a feature description)?
Best answer: B
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: An epic hypothesis statement frames an investment as a testable hypothesis: a specific customer, a need, the expected value, and how success will be measured. The statement that lists implementation requirements and security behaviors is describing a capability to build, not a hypothesis to validate.
In SAFe LPM, epics are evaluated and advanced based on a hypothesis you can validate, not just a list of functionality. A good epic hypothesis statement makes the intended value explicit and measurable by stating:
A feature description, by contrast, focuses on the solution behavior and implementation details (what to build) and may include constraints or compliance requirements, but it lacks the customer-need framing and testable business outcomes.
It specifies solution requirements without the customer/need/value hypothesis and measurable outcomes that characterize an epic hypothesis statement.
Topic: Exploring Lean Portfolio Management (LPM)
A funded value stream is preparing for the next PI. Product Management wants to pull in a set of new customer-facing features, while System Architects insist a significant enabler effort is needed to address growing performance and automation gaps. As an LPM participant, you are asked whether to adjust the planned mix of work.
What should you verify first before recommending any change?
Best answer: B
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Capacity allocation is a Lean budgeting guardrail that helps a funded value stream balance delivering new business value with sustaining architectural and technical health. Before changing the mix, you need the agreed allocation expectations and the current plan’s consumption of those allocations. That baseline enables an intentional trade-off rather than a reactive prioritization debate.
In Lean Portfolio Management, funded value streams use guardrails to support decentralized decisions while protecting long-term outcomes. Capacity allocation is one of those guardrails: it makes the intended balance of work types explicit (e.g., customer-facing features versus enablers such as architecture, performance, and automation).
Before recommending changes to the PI plan, first confirm:
With that baseline, stakeholders can discuss trade-offs (and adjust scope) while staying within the economic and technical constraints of the funded value stream. Detailed execution data and solution details can follow after the guardrail check.
Capacity allocation guardrails and current planned usage provide the baseline for balancing value delivery with required enabler work in a funded value stream.
Topic: Exploring Lean Portfolio Management (LPM)
Two weeks before PI Planning, the LPM team sees eight candidate epics competing for funding across two ARTs. Portfolio Kanban has a WIP limit of five epics in analysis, and the enterprise has two current strategic themes: (1) meet new regulatory requirements this year, and (2) reduce customer onboarding time by 30%. The ARTs’ draft roadmaps emphasize different priorities and can’t both take all requested work.
What is the best next action?
Best answer: A
What this tests: Exploring Lean Portfolio Management (LPM)
Explanation: Strategic themes connect enterprise strategy to execution and are used to guide portfolio priorities and ART roadmaps. Given limited capacity and an explicit WIP constraint in the Portfolio Kanban, the right move is to align the epic sequence and roadmap intent to the themes before PI Planning so teams plan to the most strategic outcomes.
In SAFe, strategic themes translate strategy into specific, portfolio-level business outcomes and provide the primary alignment context for portfolio decisions and ART planning. When multiple ARTs have competing demands, LPM uses the themes to steer epic prioritization and roadmap intent so that PI Planning starts with clear strategic direction.
Given the stated WIP limit, LPM should also avoid pushing more work into analysis than the system can handle. A practical next step is to collaboratively:
This preserves flow and ensures ART roadmaps reflect enterprise priorities rather than local optimization.
Strategic themes provide the alignment lens LPM uses to sequence epics and guide ART roadmaps within portfolio guardrails.
Use the SAFe Agilist Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the SAFe Agilist guide on PMExams.com, then return to PM Mastery for timed practice.