LEading Safe

What is one pillar of the SAFe House of Lean??

• Transparency

• Innovation

• Agile

• Quality

What is one Guardrail on Lean Budget spend?

• Investment horizons

• Centralized decision-making

• Lean Portfolio Metrics

• Customer participation in PI Planning

Who is responsible for managing the Portfolio Kanban?

• System Team

• Epic Owners

• Solution Management

• Lean Portfolio Management

How does SAFe recommend using a second operating system to deliver value?

• Leverage Solutions with economies of scale

• Build a small entrepreneurial network focused on the Customer instead of the existing hierarchies

• Organize the Enterprise around the flow of value while maintaining the hierarchies

• Create teams to focus on innovation and growth and break down the existing organizational structures

What does the Continuous Delivery Pipeline enable?

• Ongoing learning

• Delivery of large batches

• Increased technical debt

• Continuous refactoring

What is one tool used to focus on users in Design Thinking?

• Story Maps

• Solution spaces

• Indirect customer market analysis

• Role definitions

Why do Business Owners assign business value to team PI Objectives?

• To ensure the teams do not work on architectural Enablers

• To override the decisions made in WSJF prioritization

• To provide guidance on the business value of the team objectives

• To determine the highest value using WSJF

Which SAFe Principle includes working with purpose, mission, and minimum constraints?

• Base Milestones on an objective evaluation of working systems

• Unlock the intrinsic motivation of knowledge workers

• Organize around value

• Build projects around motivated individuals

How can trust be gained between the business and development?

• Deliver predictability

• Release new value to production every day

• Maintain Iterations as a safe zone for the team

• Automate the delivery pipeline

If small batches go through the system faster with lower variability, then which statement is true about batch size?

• Batch sizes cannot influence behavior

• Low utilization increases variability

• Large batches can cause projects to miss targets

• Good infrastructure enables large batches