SAFe Lean Portfolio Manager LPM 6.0 Exam Questions

Domain 1: Introducing Lean Portfolio Management

What is the primary purpose of Lean Portfolio Management (LPM) in SAFe?

⬜ To centralize all technical decisions with the Enterprise Architect
⬜ To align strategy and execution by applying Lean and Agile principles to portfolio-level strategy, funding, and governance
⬜ To eliminate the need for Program Increment Planning
⬜ To replace the Release Train Engineer role

Which three competency dimensions make up Lean Portfolio Management?

⬜ Scrum, Kanban, and DevOps
⬜ Strategy and Investment Funding, Agile Portfolio Operations, and Lean Governance
⬜ Sprint Planning, Backlog Refinement, and Retrospectives
⬜ Vision, Roadmap, and Release Planning

What does a “one portfolio mindset” mean in Lean Portfolio Management?

⬜ Only one Value Stream is allowed per portfolio
⬜ All initiatives and investments are viewed and prioritized together against shared strategic themes, rather than managed in isolated silos
⬜ Only the Portfolio Manager may create epics
⬜ Every team in the organization must use the same tool

What role does the Lean-Agile Center of Excellence (LACE) typically play in supporting Lean Portfolio Management?

⬜ It approves every user story before development
⬜ It helps guide and accelerate the adoption of Lean-Agile practices, including LPM practices, across the enterprise
⬜ It replaces the Value Management Office entirely
⬜ It owns all Team Backlogs

How does Lean Portfolio Management typically change the way work is funded compared to traditional project-based portfolio management?

⬜ It shifts funding from individual projects to persistent Value Streams and Agile Release Trains
⬜ It requires funding to be approved separately for every single user story
⬜ It removes the need for any budget forecasting
⬜ It funds only completed, no-risk initiatives

Compared to traditional portfolio management, Lean Portfolio Management favors which approach to decision-making?

⬜ Centralized, top-down approval for every operational decision
⬜ Decentralized decision-making within a lightweight set of guardrails, keeping oversight where it adds real value
⬜ No governance or oversight of any kind
⬜ Governance only at the end of the fiscal year

Domain 2: Establishing Portfolio Strategy and Vision

What are Strategic Themes in the context of Lean Portfolio Management?

⬜ The names given to individual user stories
⬜ Differentiating, market-based business objectives that connect enterprise strategy to the portfolio and influence portfolio strategy and investment decisions
⬜ A list of software architecture patterns approved for use
⬜ The set of tools used by the Scrum Master

What is the primary purpose of a Portfolio Vision?

⬜ To document individual sprint goals
⬜ To describe the future state of the portfolio’s solutions and Value Streams in a way that guides investment and epic decisions
⬜ To replace the need for PI Objectives
⬜ To set a fixed, unchangeable multi-year roadmap

What is the purpose of a Portfolio Canvas?

⬜ To track individual developer performance
⬜ To provide a structured, one-page tool for capturing the portfolio’s customers, value proposition, Value Streams, and cost/revenue drivers
⬜ To replace the Portfolio Kanban
⬜ To document detailed acceptance criteria for epics

Who typically has primary responsibility for defining and communicating portfolio strategy and vision?

⬜ Individual Scrum Masters
⬜ Business Owners and other portfolio stakeholders, informed by Enterprise and Solution architecture input
⬜ Only the development teams
⬜ The Release Train Engineer alone

What is a Value Stream, as it relates to portfolio strategy?

⬜ The series of steps an organization uses to implement Solutions that provide continuous value to a customer
⬜ A single Program Increment’s worth of committed stories
⬜ A financial ledger used only by the finance department
⬜ A synonym for an individual Scrum team

What is the purpose of a Portfolio Roadmap?

⬜ To list every defect ever logged against the portfolio’s solutions
⬜ To provide a graphical, time-based view of major portfolio epics and milestones planned for delivery
⬜ To replace the PI Planning agenda
⬜ To document team-level technical debt only

Why is it important to connect enterprise strategy explicitly to Strategic Themes and the Portfolio Vision?

⬜ So that day-to-day investment and epic decisions stay aligned with the organization’s broader direction rather than drifting independently
⬜ Because Scaled Agile requires it as a compliance checkbox with no practical benefit
⬜ Because it eliminates the need for a Lean Business Case
⬜ Because it replaces the need for a Portfolio Kanban

Domain 3: Realizing Portfolio Vision Through Epics

What is an Epic in SAFe, in relation to Lean Portfolio Management?

⬜ A single user story that takes more than one Sprint
⬜ A significant Solution development initiative large enough to require analysis, a Lean Business Case, and financial approval before implementation
⬜ A defect reported by a customer
⬜ A synonym for a Feature within a single ART

What is the purpose of an Epic Hypothesis Statement?

⬜ To document final acceptance test results
⬜ To frame an epic as a testable hypothesis, describing the proposed solution, its business outcomes, and the leading indicators that will validate it
⬜ To replace the need for a Portfolio Vision
⬜ To assign story points to an epic

What is the primary responsibility of an Epic Owner?

⬜ Writing all the code required to implement the epic personally
⬜ Defining the epic, working with stakeholders to get it approved, and shepherding it through the Portfolio Kanban to implementation
⬜ Approving the enterprise’s annual budget
⬜ Running the Daily Stand-up for every team involved

When is a Lean Business Case typically developed for an epic?

⬜ Before the epic even enters the Portfolio Kanban Funnel
⬜ During the “Analyzing” state, to support the go/no-go decision to move the epic into the Portfolio Backlog
⬜ Only after the epic has been fully implemented
⬜ It is never required in SAFe

How does an epic typically get validated before committing full funding to it?

⬜ By skipping validation and committing the full budget immediately
⬜ By building a Minimum Viable Product (MVP) and using a Lean Startup build-measure-learn cycle to test the epic’s hypothesis
⬜ By having the Enterprise Architect approve it without any prototyping
⬜ By requiring a signed contract from the customer first

What role does an Enterprise Architect typically play when an epic is being analyzed?

⬜ They have no involvement in epic analysis
⬜ They assess the epic’s architectural impact and its effect on the Architectural Runway across Value Streams
⬜ They personally write the Lean Business Case’s financial projections
⬜ They approve the epic’s marketing plan

Domain 4: Establishing Investment Funding

What is the core Lean-Agile principle behind SAFe’s approach to portfolio funding?

⬜ Fund every individual project separately with its own budget and team
⬜ Fund Value Streams, not projects, so budgets remain stable while what’s built within them can adapt
⬜ Only fund initiatives that have zero risk
⬜ Require a new procurement cycle for every Feature

Which Lean Budget Guardrail focuses on ensuring the investment mix balances near-term delivery with longer-term strategic bets?

⬜ Guardrails for investment horizons
⬜ Capacity allocation
⬜ Approving significant initiatives
⬜ Continuous Business Owner engagement

Which Lean Budget Guardrail is used to balance investment between new business features and enabler work such as technical debt or infrastructure?

⬜ Guardrails for investment horizons
⬜ Capacity allocation
⬜ Approving significant initiatives
⬜ Continuous Business Owner engagement

Which Lean Budget Guardrail addresses the need for extra scrutiny and approval when an epic’s projected cost exceeds a defined threshold?

⬜ Capacity allocation
⬜ Guardrails for investment horizons
⬜ Approving significant initiatives
⬜ Continuous Business Owner engagement

Which Lean Budget Guardrail ensures Business Owners stay actively involved in tracking spend and outcomes rather than only approving a budget once a year?

⬜ Capacity allocation
⬜ Approving significant initiatives
⬜ Continuous Business Owner engagement
⬜ Guardrails for investment horizons

What is Strategic Investment Planning (formerly known as Participatory Budgeting) used for?

⬜ Setting individual developer salaries
⬜ Engaging portfolio stakeholders together in a structured exercise to allocate budget across Value Streams based on strategy
⬜ Approving a single team’s Iteration budget
⬜ Auditing completed epics after the fact

What is one key benefit of funding Value Streams rather than individual projects?

⬜ It reduces the cost-accounting overhead and enables faster reallocation of priorities without renegotiating funding
⬜ It removes the need for any financial reporting at all
⬜ It guarantees every epic will succeed
⬜ It eliminates the need for Enterprise Architects

Why does SAFe favor periodic, lightweight budget adjustments over rigid, once-a-year budgeting?

⬜ Because annual budgeting is required by law in most countries
⬜ Because market conditions and priorities change faster than an annual cycle can accommodate, so more frequent, lightweight adjustments keep funding aligned to current strategy
⬜ Because it eliminates the need for a Lean Business Case
⬜ Because it removes Business Owners from the funding process

Domain 5: Managing Portfolio Flow

What are the typical states of the Portfolio Kanban, in order?

⬜ Funnel, Analyzing, Portfolio Backlog, Implementing, Done
⬜ Backlog, Sprint, Review, Retrospective
⬜ Draft, Approved, Rejected, Archived
⬜ Planning, Execution, Monitoring, Closing

What is the primary purpose of the “Funnel” state in the Portfolio Kanban?

⬜ To capture all new epic ideas as they are proposed, before any significant analysis begins
⬜ To track epics that have already been fully implemented
⬜ To store rejected epics permanently
⬜ To hold the annual budget approval documents

What primarily happens while an epic is in the “Analyzing” state of the Portfolio Kanban?

⬜ The epic is being coded by development teams
⬜ The Epic Owner and stakeholders develop the Lean Business Case and assess feasibility, cost, and impact
⬜ The epic is archived and no longer tracked
⬜ Business Owners sign off on the final release

What does it mean for an epic to be in the “Portfolio Backlog” state?

⬜ The epic has been rejected and will not proceed
⬜ The epic has been approved for implementation and is waiting for the necessary Value Stream capacity
⬜ The epic is complete and delivered to customers
⬜ The epic is still being drafted and has no owner

What is happening to an epic in the “Implementing” state of the Portfolio Kanban?

⬜ It is still awaiting initial funding approval
⬜ It is actively being built by the relevant Agile Release Trains and/or Value Streams, tracked against its Lean Business Case
⬜ It has been permanently canceled
⬜ It is only being discussed at the executive level, with no team involvement yet

Why does SAFe recommend applying WIP limits to the Portfolio Kanban, similar to team and program Kanbans?

⬜ To prevent too many epics from being analyzed or implemented simultaneously, which would overload Value Streams and slow overall flow
⬜ Because Scaled Agile requires a specific number of epics per quarter
⬜ To guarantee every epic gets exactly equal funding
⬜ WIP limits are not recommended at the portfolio level

Which of the following best reflects a flow-based way of thinking about portfolio-level performance?

⬜ Judging performance only by the total dollar amount spent per quarter
⬜ Tracking how quickly and predictably epics move through the Portfolio Kanban from Funnel to Done, similar to flow metrics used at the team and ART level
⬜ Ignoring cycle time entirely since only ART-level flow matters
⬜ Measuring performance only by counting the number of Portfolio Sync meetings held

Multiple epics competing for the same Value Stream’s capacity are causing delays across the portfolio. What is the most appropriate Lean Portfolio Management response?

⬜ Approve all competing epics fully and let teams figure out sequencing informally
⬜ Use Portfolio Kanban WIP limits and capacity allocation guardrails to sequence and prioritize epics against strategy
⬜ Cancel the Value Stream entirely
⬜ Ignore the delays since portfolio flow is not measurable

Domain 6: Applying Agile Portfolio Operations

What is the primary purpose of the Portfolio Sync event?

⬜ To replace the Program Increment Planning event
⬜ To coordinate the flow of epics, resolve cross-Value-Stream dependencies, and review portfolio-level progress on a regular cadence
⬜ To finalize individual team retrospectives
⬜ To approve individual user stories

What is a core responsibility of Agile Portfolio Operations?

⬜ Writing code for every Value Stream
⬜ Coordinating and supporting the execution of Value Streams and communicating portfolio priorities and progress across the organization
⬜ Approving personal performance reviews for developers
⬜ Setting individual Sprint goals for every team

How does the Portfolio Kanban support Agile Portfolio Operations day-to-day?

⬜ It provides visibility into where every epic stands, supporting coordination and prioritization decisions across Value Streams
⬜ It replaces the need for any Portfolio Sync events
⬜ It is used only once a year during annual planning
⬜ It tracks only completed, historical work

What is the value of establishing a Community of Practice (CoP) for Lean Portfolio Management stakeholders?

⬜ It replaces the need for the LACE
⬜ It lets people practicing similar LPM roles (e.g., Epic Owners, Portfolio stakeholders) share knowledge, tools, and continuously improve their practices
⬜ It is used to formally discipline underperforming teams
⬜ It exists only to plan the annual holiday event

How should Agile Portfolio Operations help keep ART and Value Stream execution aligned with portfolio strategy?

⬜ By dictating every technical decision the ARTs make
⬜ By regularly communicating strategic priorities, roadmaps, and epic status so ARTs and Value Streams understand how their work ladders up to strategy
⬜ By eliminating PI Planning
⬜ By avoiding any interaction with ART-level events

Which activity is a good example of Agile Portfolio Operations in practice?

⬜ A single developer refactoring a legacy module
⬜ Facilitating cross-Value-Stream dependency resolution and keeping the Portfolio Roadmap updated as epics progress
⬜ Approving an individual’s expense report
⬜ Writing acceptance criteria for a single Feature

Domain 7: Applying Lean Governance

What is the primary role of the Value Management Office (VMO) in Lean Governance?

⬜ To write user stories for every team
⬜ To help coordinate decentralized decision-making across the portfolio while maintaining appropriate oversight, compliance, and reporting
⬜ To replace all Business Owners
⬜ To run the Daily Stand-up for every ART

How does Lean Governance typically balance regulatory/compliance requirements (e.g., financial audit needs) with Agile ways of working?

⬜ By ignoring compliance requirements entirely in favor of speed
⬜ By applying lightweight, right-sized guardrails and periodic reporting that satisfy compliance needs without reintroducing heavy, centralized control
⬜ By requiring every team to submit a detailed Gantt chart monthly
⬜ By outsourcing all compliance work to external auditors only

Which principle best describes Lean Governance’s approach to decision rights across the portfolio?

⬜ Decentralize decisions to those closest to the information, while retaining accountability and guardrails at the portfolio level
⬜ Centralize every decision with senior executives regardless of the decision’s scope
⬜ Remove all accountability once budgets are approved
⬜ Require legal sign-off for every user story

What kind of metrics does Lean Governance typically use to monitor portfolio health?

⬜ Only individual developer utilization rates
⬜ A mix of spend versus budget, epic flow/predictability, and outcome-based measures tied to the portfolio’s strategic themes
⬜ Only the number of retrospectives completed
⬜ Only customer complaint counts