21. Three collaborations make up the Lean Portfolio Management competency: Strategy and Investment Funding, Lean Governance, and what else?
Agile Portfolio Operations
22. Which role has the responsibility for accepting stories and team increments?
Release Train Engineer
23. Features in Program Backlogs can result from what?
Decomposing Enabler Stories
Refining the Team Backlog
Aggregating stories into Features
Splitting Epics or Capabilities
24. What does assigning business value to a team’s PI Objectives influence?
How often team deploys
How teams plan the implementation
How the Kanban WIP limits are set
How to achieve objectives
25. The Product Manager has content authority for the Program Backlog including: the Vision, the Roadmap, driving the PI Objectives, and what else?
Establishing Features and Benefit Hypothesis
Managing risk, helping to ensure value delivery, and driving continuous improvement
Accepting stories and team increments
Working with business stakeholders and Solution and System Architects to implement holistic technology across Value Streams
26. How do Business Owners quantify the value of PI Objectives?
By assigning business value
By totaling the Epic budget
By estimating return on investment
By assigning story points
27. Which statement describes the Team and Technical Agility enterprise competency?
Solution trains that coordinate multiple Agile Release Trains and suppliers
A collaboration that creates Lean budget and investment guardrails
Cross-functional, self-organizing teams that define, build, test and possibly deploy valuable things
A Community of Practice that leads the transformation
28. Product Managers are expected to collaborate in planning the amount of upcoming Enabler work by establishing what?
Team Backlog prioritization
Completed Epic acceptance criteria
Accurate user story sizing
29. What are two inputs to the Solution Vision? (Choose two.)
30. How frequently should the Program Backlog be reviewed?
When the Epic owners are defining the Epic Value Statement
Before every PI