What are the four SAFe configurations?
SAFe draws from what (four) primary bodies of knowledge?
SAFe (Scaled Agile Framework) draws from four primary bodies of knowledge that inform its principles and practices:
What is a Lean-Agile Mindset?
A foundational belief system combining Lean Thinking and Agile Development, guiding behaviors and decisions to support business agility.
What are the two core principles behind the Lean-Agile Mindset?
What are the core principles of Lean Thinking?
“Take an economic view” refers to which principle?
Principle #1
This principle emphasizes the importance of understanding the economics of product development to make informed decisions that optimize value delivery. It highlights that all decisions made at any level should consider their economic impact, ensuring that the organization delivers the best value and quality in the shortest sustainable lead time.
What are the ten SAFe Lean-Agile Principles?
1 – Take an economic view
#2 – Apply systems thinking
#3 – Assume variability; preserve options
#4 – Build incrementally with fast, integrated learning cycles
#5 – Base milestones on objective evaluation of working systems
#6 – Make value flow without interruptions
#7 – Apply cadence, synchronize with cross-domain planning
#8 – Unlock the intrinsic motivation of knowledge workers
#9 – Decentralize decision-making
#10 – Organize around value
What is the main goal of applying an economic view in SAFe?
A. Delivering the most features possible
B. Making decisions based on intuition
C. Delivering maximum value in the shortest sustainable lead time
D. Reducing the number of Agile teams
C. Delivering maximum value in the shortest sustainable lead time
This principle focuses on system economics — understanding Cost of Delay, balancing development and operational costs, and optimizing for value delivery speed.
What does applying systems thinking mean in SAFe?
A. Focusing on improving individual team performance
B. Optimizing the entire system rather than individual parts
C. Centralizing decision-making
D. Reducing the number of iterations
B. Optimizing the entire system rather than individual parts.
Systems thinking ensures the whole value stream is optimized, preventing sub-optimization of parts that harm overall performance. Taking a holistic approach to solution development
What practice supports the principle “Assume variability; preserve options”?
A. Defining a single solution early and committing
B. Evaluating multiple design options and eliminating weaker ones over time
C. Avoiding experimentation to reduce risk
D. Finalizing architecture before development
B. Evaluating multiple design options and eliminating weaker ones over time.
This uses Set-Based Design, keeping multiple alternatives open to manage uncertainty until data guides the best choice.
“A leader encourages decentralized decision-making and continuous learning. Which principle does this reflect?”
Principle #8: Unlock the intrinsic motivation of knowledge workers.
Principle #9: Decentralize Decision-Making:
An organization reorganizes its teams into value streams to focus on delivering customer outcomes rather than functions. What principle is this?
Principle #10: Organize around value
💡 Aligning structure to value streams improves flow and responsiveness.
A Kanban board shows that too many stories are in progress. The team decides to limit WIP to improve flow. What principle is being applied?
Principle #6: Make value flow without interruptions
Visualize and limit WIP, reduce batch sizes, and manage queue lengths
💡 Flow improves when WIP is limited.
A System Demo after each iteration helps teams validate the integrated system. Which principle is applied here?
Principle #4: Build incrementally with fast, integrated learning cycles
💡 Integration and feedback accelerate learning.
A Product Manager must prioritize multiple Epics. She calculates the Cost of Delay and divides it by the job size to decide what to do first. Which principle is she applying?
Principle #1: Take an economic view
💡 This principle guides prioritization using WSJF to maximize value and minimize delay.
Multiple teams plan together during PI Planning to align goals and synchronize deliverables. What principle does this reflect?
Principle #7: Apply cadence; synchronize with cross-domain planning
💡 Cadence creates rhythm; synchronization aligns work across teams.
A Scrum Master promotes autonomy by letting the team decide how to meet sprint goals. What principle supports this?
Principle #8: Unlock the intrinsic motivation of knowledge workers
💡 Motivation grows when teams have control over their work.
A development team resolves technical issues locally without waiting for management approval. What principle are they applying?
Principle #9: Decentralize decision-making
💡 Delegating authority speeds up decisions and reduces bottlenecks.
An ART aligns product management, development, and operations to deliver value end-to-end. What principle supports this?
Principle #10: Organize around value
💡 Value-focused organization replaces functional silos.
During PI Planning, a team decides to delay a low-value feature to focus on one with a higher Cost of Delay. What principle supports this decision?
Principle #1: Take an economic view
💡 Economic thinking ensures resources are focused on the highest-value work.
At the start of a project, architects evaluate three design approaches and keep two viable options open until they gather more data. What principle are they following?
Principle #3: Assume variability; preserve options
💡 Encourages exploring multiple options and using data to converge.
A company holds regular ART sync meetings to align multiple teams on progress and dependencies. Which principle supports this?
Principle #7: Apply cadence; synchronize with cross-domain planning
💡 Predictable cadence and synchronization improve alignment and integration.
Strategic decisions like product portfolio direction remain centralized, while teams decide on implementation details. What principle does this demonstrate?
Principle #9: Decentralize decision-making
💡 Centralize only when necessary; decentralize operational decisions.
A team reduces their feature batch size to deliver smaller increments more often. Which principle does this demonstrate?
Principle #6: Visualize and limit WIP, reduce batch sizes, and manage queue lengths
💡 Smaller batches increase feedback frequency and predictability.