SAFe Scaled Agile For Enterprise Certification Exam
Study online at https://quizlet.com/_huisde
1. House of Lean: Goal: Value Foundation: Leadership, Respect for People and Culture, Development Flow,
Innovation, Relentless Improvement
2. Lean Goal: Speed, quality, value. sustainably shorted lead time, best quality and value to people and society,
most customer delight, lowest cost, high morale, safety
3. Respect for People: Lean principle, your customer is whoever consumes your work. Develop individuals
and teams, empower teams, build partnerships based on trust and mutual respect
4. Kaizen: Lean principle,. We can do better.Reflection, continuous improvement as an enterprise value
5. Leadership: Lean foundation, management is trained, take responsibility, develop people
6. Product development flow: Lean principle. 1. Take an economic view. 2. Actively manage queues. 3.
Understand and exploit variability. 4. Reduce batch sizes. 5. Apply WIP constraints. 6. Control flow under uncertainty;
cadence and synchronization. 7. Get feedback as fast as possible. 8. Decentralized control
7. Take an economic view: Lean principle of product development flow. #1. Base your decisions on
economics. The goal is to optimize the time from concept to cash
8. Actively manage queues: Lean principle of product development flow. #2. Understand Little's Law.
Control wait times by controlling queue lengths
9. Understand and exploit variability: Lean principle of product development flow. #3. Risk taking is
central to value creation
10. Reduce Batch Size: Lean principle of product development flow. #4. Smaller batches go through the
system faster, with lower variability and risk. Large batch sizes and high utilization increase variability, causing project
slippage. Co-location and good infrastructure enable small batches
11. Apply WIP constraints: Lean principle of product development flow. #5. WIP constraints force capacity
matching, increases flow. Time box, purge lower value projects when WIP is too high, constrain local WIP pools, make
WIP continuously visible. High WIP and utilization cause reduction throughput
12. Control flow under uncertainty: Lean principle of product development flow. #6. Cadence +
Synchronization. Cadence transforms unpredictable events into predictable events, requires scope or capacity margin,
makes waiting times predictable, helps manage load by limiting available time. Regular systemwide integration provides
higher fidelity tests and objective solution assessment
13. Get fast feedback: Lean principle of product development flow. #7. Product development is the process
of converting uncertainty to knowledge. Fast feedback accelerates knowledge
14. Decentralized control: Lean principle of product development flow. #8. Centralize control for decisions
that are infrequent and can be applied globally, have significant economies of scale or high-risk. Decentralized contro
for time critical, local decisions
, SAFe Scaled Agile For Enterprise Certification Exam
Study online at https://quizlet.com/_huisde
15. Planning is for alignment: Lean principle of product development flow. #9. There is more value created
with overall alignment than with local excellence. Agile aims to change the plan when something changes
16. Agile values: Individuals and interactions: Over processes and tools
17. Agile values: working software: Over comprehensive documentation
18. Agile values: customer collaboration: Over contract negotiation
19. Agile values: responding to change: Over following a plan
20. Agile drivers in the triangle.: Value and quality driven, the vision creates feature estimates, fix the
dates and float the scope
21. Agile benefits: Early value delivery drives first to market, fast feedback, profitability, makes money faster,
reduces risk, delivers better fit for purpose
22. SAFe core values: Alignment, Code quality, Transparency, program execution
23. Four SAFe business results: Increased employee engagement, 20-50% increase in productivity,
30-70% faster time to market, 50% defect reduction
24. Describe an Agile team: Empowered, self organizing, self managing, cross functional, deliver fully tested
code every two weeks
25. How does an Agile team deliver value?: In user stories
26. Describe a SAFe team that is scaled to program level: Self organizing, self managing
team of Agile teams, continuous value delivery, aligned to a common mission via a single program backlog
27. How do program level safe teams deliver value?: In features and benefits
28. Describe how SAFe is scaled to the portfolio level.: Using Lean approaches to strategy
and investment funding, program management, and governance. Centralized strategy and decentralized execution.
Objective metrics support governance and kaizen
29. How does portfolio level SAFe deliver value?: In business and architectural epics
30. What is the product owner's content authority?: User stories
31. What is product management content authority?: Features
32. What is the typical ratio of product management to product owners?: One PM
to four PO
33. What is the typical size of an Agile Release Train: 5-12 teams 50-125 people
34. What is the typical ART program increment time box?: 10 weeks
35. What are the shared teams in Agile Release Train?: DevOps, UX, System Architect, RTE
36. How often is the team demo in the ART?: Every two weeks
37. How often is the inspect and adapt in an ART?: Every 10 weeks
Study online at https://quizlet.com/_huisde
1. House of Lean: Goal: Value Foundation: Leadership, Respect for People and Culture, Development Flow,
Innovation, Relentless Improvement
2. Lean Goal: Speed, quality, value. sustainably shorted lead time, best quality and value to people and society,
most customer delight, lowest cost, high morale, safety
3. Respect for People: Lean principle, your customer is whoever consumes your work. Develop individuals
and teams, empower teams, build partnerships based on trust and mutual respect
4. Kaizen: Lean principle,. We can do better.Reflection, continuous improvement as an enterprise value
5. Leadership: Lean foundation, management is trained, take responsibility, develop people
6. Product development flow: Lean principle. 1. Take an economic view. 2. Actively manage queues. 3.
Understand and exploit variability. 4. Reduce batch sizes. 5. Apply WIP constraints. 6. Control flow under uncertainty;
cadence and synchronization. 7. Get feedback as fast as possible. 8. Decentralized control
7. Take an economic view: Lean principle of product development flow. #1. Base your decisions on
economics. The goal is to optimize the time from concept to cash
8. Actively manage queues: Lean principle of product development flow. #2. Understand Little's Law.
Control wait times by controlling queue lengths
9. Understand and exploit variability: Lean principle of product development flow. #3. Risk taking is
central to value creation
10. Reduce Batch Size: Lean principle of product development flow. #4. Smaller batches go through the
system faster, with lower variability and risk. Large batch sizes and high utilization increase variability, causing project
slippage. Co-location and good infrastructure enable small batches
11. Apply WIP constraints: Lean principle of product development flow. #5. WIP constraints force capacity
matching, increases flow. Time box, purge lower value projects when WIP is too high, constrain local WIP pools, make
WIP continuously visible. High WIP and utilization cause reduction throughput
12. Control flow under uncertainty: Lean principle of product development flow. #6. Cadence +
Synchronization. Cadence transforms unpredictable events into predictable events, requires scope or capacity margin,
makes waiting times predictable, helps manage load by limiting available time. Regular systemwide integration provides
higher fidelity tests and objective solution assessment
13. Get fast feedback: Lean principle of product development flow. #7. Product development is the process
of converting uncertainty to knowledge. Fast feedback accelerates knowledge
14. Decentralized control: Lean principle of product development flow. #8. Centralize control for decisions
that are infrequent and can be applied globally, have significant economies of scale or high-risk. Decentralized contro
for time critical, local decisions
, SAFe Scaled Agile For Enterprise Certification Exam
Study online at https://quizlet.com/_huisde
15. Planning is for alignment: Lean principle of product development flow. #9. There is more value created
with overall alignment than with local excellence. Agile aims to change the plan when something changes
16. Agile values: Individuals and interactions: Over processes and tools
17. Agile values: working software: Over comprehensive documentation
18. Agile values: customer collaboration: Over contract negotiation
19. Agile values: responding to change: Over following a plan
20. Agile drivers in the triangle.: Value and quality driven, the vision creates feature estimates, fix the
dates and float the scope
21. Agile benefits: Early value delivery drives first to market, fast feedback, profitability, makes money faster,
reduces risk, delivers better fit for purpose
22. SAFe core values: Alignment, Code quality, Transparency, program execution
23. Four SAFe business results: Increased employee engagement, 20-50% increase in productivity,
30-70% faster time to market, 50% defect reduction
24. Describe an Agile team: Empowered, self organizing, self managing, cross functional, deliver fully tested
code every two weeks
25. How does an Agile team deliver value?: In user stories
26. Describe a SAFe team that is scaled to program level: Self organizing, self managing
team of Agile teams, continuous value delivery, aligned to a common mission via a single program backlog
27. How do program level safe teams deliver value?: In features and benefits
28. Describe how SAFe is scaled to the portfolio level.: Using Lean approaches to strategy
and investment funding, program management, and governance. Centralized strategy and decentralized execution.
Objective metrics support governance and kaizen
29. How does portfolio level SAFe deliver value?: In business and architectural epics
30. What is the product owner's content authority?: User stories
31. What is product management content authority?: Features
32. What is the typical ratio of product management to product owners?: One PM
to four PO
33. What is the typical size of an Agile Release Train: 5-12 teams 50-125 people
34. What is the typical ART program increment time box?: 10 weeks
35. What are the shared teams in Agile Release Train?: DevOps, UX, System Architect, RTE
36. How often is the team demo in the ART?: Every two weeks
37. How often is the inspect and adapt in an ART?: Every 10 weeks
