SAFe POPM - Section 2 | Questions & Answers (100 %Score) Latest Updated 2024/2025
Comprehensive Questions A+ Graded Answers | With Expert Solutions
Set-Based Design (SBD) - Set-based design is a practice that maintains multiple requirements and design
options for a longer period in the development cycle. Empirical data is used to narrow focus based on
the emergent knowledge presented at integration-based learning points. Produces more optimal
technical and economic outcomes.
Set-Based Design AKA - Set-Based Concurrent Engineering (SBCE)
Which Principle does Set-Based Design Apply to? - Principle 3: Assume variability; preserve options
Four Critical Errors of Phase-Gate Milestones - - Centralizing requirements and design decisions in siloed
functions that do not actually build the system
- Forcing too-early design decisions and false-positive feasibility
- Assuming a point solution exists and can be built correctly the first time
- Making up-front decisions creates large batches of requirements, code, tests, and queues leading to
large-batch handoffs and delayed feedback.
Incremental Milestones vs. Phase-Gates - System is build in increments and each integration point
demonstrates some evidence of feasibility of the solution in process. Each milestone involves
requirements, design, development, and testing all producing an increment of value.
Which Principle does Incremental Milestones belong to? - Principle 5 - Base milestones on objective
evaluation of working systems
Benefits of decentralized decision-making - - Reduces delays
- Inproves product development flow and throughput
- facilitates faster feedback & more innovative solutions
- Higher levels of empowerment (additional benefit)
, Characteristics of decisions that should be Centralized - - Infrequent: not urgent and deeper
consideration is appropriate (e.g., product strategy, international expansion)
- Long-lasting: Unlikely to change in the short-term (e.g., commitment to tech platform or realignment
around value streams)
- Provide economies of scale: Deliver large and broad economic benefits (e.g., standard tooling,
offshoring)
Characteristics of decisions that should be Decentralized - - Frequent: problem is recurrent and common
(e.g., backlog prioritization, response to defects)
- Time-critical: High cost of delay (e.g., point releases, customer emergencies, dependencies w/ other
teams)
- Requires Local Information: Need specific local context (e.g., specific customer needs, significant design
problem, self-organization to emerging challenge)
Decentralized decision-making applies to what Principle? - Principle 9: Decentralize decision-making
Who leads PI Planning preparation? - PM takes the lead preparing for PI Planning, supported by the PO.
They own feature priorities.
Agile team owns what at PI? - Story planning and high-level estimates
Architect/Engineering and UX have what role in PI Planning? - Work as intermediaries for governance,
interfaces and dependancies
Inputs to PI Planning (PI Planning Prep) - - Create/update Vision and Roadmap
- Socialize the Top 10 features to set expectations for the PI Planning meeting
Who ensures the Vision and Program/Team Backlogs are aligned to Strategic Themes? - PMs collaborate
w/ Lean Portfolio Management.
Non-functional requirements - Constraints on the services or functions offered by the system such as
timing constraints, constraints on the development process, standards, etc. (e.g., performance,
reliability, platforms).
Comprehensive Questions A+ Graded Answers | With Expert Solutions
Set-Based Design (SBD) - Set-based design is a practice that maintains multiple requirements and design
options for a longer period in the development cycle. Empirical data is used to narrow focus based on
the emergent knowledge presented at integration-based learning points. Produces more optimal
technical and economic outcomes.
Set-Based Design AKA - Set-Based Concurrent Engineering (SBCE)
Which Principle does Set-Based Design Apply to? - Principle 3: Assume variability; preserve options
Four Critical Errors of Phase-Gate Milestones - - Centralizing requirements and design decisions in siloed
functions that do not actually build the system
- Forcing too-early design decisions and false-positive feasibility
- Assuming a point solution exists and can be built correctly the first time
- Making up-front decisions creates large batches of requirements, code, tests, and queues leading to
large-batch handoffs and delayed feedback.
Incremental Milestones vs. Phase-Gates - System is build in increments and each integration point
demonstrates some evidence of feasibility of the solution in process. Each milestone involves
requirements, design, development, and testing all producing an increment of value.
Which Principle does Incremental Milestones belong to? - Principle 5 - Base milestones on objective
evaluation of working systems
Benefits of decentralized decision-making - - Reduces delays
- Inproves product development flow and throughput
- facilitates faster feedback & more innovative solutions
- Higher levels of empowerment (additional benefit)
, Characteristics of decisions that should be Centralized - - Infrequent: not urgent and deeper
consideration is appropriate (e.g., product strategy, international expansion)
- Long-lasting: Unlikely to change in the short-term (e.g., commitment to tech platform or realignment
around value streams)
- Provide economies of scale: Deliver large and broad economic benefits (e.g., standard tooling,
offshoring)
Characteristics of decisions that should be Decentralized - - Frequent: problem is recurrent and common
(e.g., backlog prioritization, response to defects)
- Time-critical: High cost of delay (e.g., point releases, customer emergencies, dependencies w/ other
teams)
- Requires Local Information: Need specific local context (e.g., specific customer needs, significant design
problem, self-organization to emerging challenge)
Decentralized decision-making applies to what Principle? - Principle 9: Decentralize decision-making
Who leads PI Planning preparation? - PM takes the lead preparing for PI Planning, supported by the PO.
They own feature priorities.
Agile team owns what at PI? - Story planning and high-level estimates
Architect/Engineering and UX have what role in PI Planning? - Work as intermediaries for governance,
interfaces and dependancies
Inputs to PI Planning (PI Planning Prep) - - Create/update Vision and Roadmap
- Socialize the Top 10 features to set expectations for the PI Planning meeting
Who ensures the Vision and Program/Team Backlogs are aligned to Strategic Themes? - PMs collaborate
w/ Lean Portfolio Management.
Non-functional requirements - Constraints on the services or functions offered by the system such as
timing constraints, constraints on the development process, standards, etc. (e.g., performance,
reliability, platforms).
