The Agile Team includes the Scrum Master and which other key role?
A
Explanation:
Agile Team Composition: According to SAFe, an Agile Team is composed of cross-functional members
who work together to deliver value. The team includes:
Scrum Master: Facilitates the team’s processes, helps remove impediments, and supports
continuous improvement.
Product Owner: Represents the customer and stakeholders, prioritizes the backlog, and ensures the
team is working on the most valuable items.
Developers: The team members who design, build, and test the product.
Key Role: The Product Owner is essential to the Agile Team as they provide the vision, set priorities,
and ensure that the team is delivering value that aligns with the customer and business needs.
SAFe Scrum Master Reference:
The SAFe framework emphasizes the critical role of the Product Owner within the Agile Team,
ensuring alignment and effective backlog management.
What is the purpose of the Large Solution level in SAFe?
C
Explanation:
Large Solution Level in SAFe: This level is designed for enterprises where multiple Agile Release
Trains (ARTs) and suppliers collaborate to build and deploy complex solutions that require
coordination beyond a single ART.
Purpose: The Large Solution level provides the practices, roles, and artifacts necessary to coordinate
the efforts of multiple ARTs:
Solution Train: A structure that manages the delivery of large solutions, aligning the efforts of
multiple ARTs.
Solution Management and Solution Architect/Engineer: Roles responsible for defining the solution’s
vision, roadmap, and architecture.
Solution Backlog and Solution Kanban: Tools to manage and prioritize work across multiple ARTs.
Coordination: The primary focus is on ensuring that all ARTs are aligned, integrated, and delivering
cohesive, high-quality solutions.
SAFe Scrum Master Reference:
The SAFe framework details the Large Solution level and its role in coordinating the efforts of
multiple ARTs to deliver complex, enterprise-level solutions.
What is one problem with phase-gate Milestones?
A
Explanation:
Phase-gate milestones are traditional project management mechanisms that mark the end of one
phase and the beginning of another. One major problem with phase-gate milestones is that they
assume a point solution exists and can be built correctly the first time. This assumption does not
account for the iterative nature of Agile methodologies, where solutions are developed
incrementally and iteratively, with feedback loops and continuous improvement. Assuming a point
solution can be finalized early often leads to rigidity, lack of adaptability, and higher risks of
delivering a product that does not meet the actual needs or expectations.
What is one output from the problem-solving workshop?
D
Explanation:
One of the primary outputs from the problem-solving workshop in SAFe is identifying the top
improvement items for the next Program Increment (PI). These workshops focus on analyzing issues,
determining root causes, and formulating actionable improvements. By prioritizing and committing
to these improvement items, teams can systematically address problems and enhance their
performance and productivity in subsequent PIs.
How is average lead time measured in a Kanban system?
C
Explanation:
In a Kanban system, average lead time is measured by observing the horizontal distance between the
arrival and departure lines on a cumulative flow diagram (CFD). The CFD visualizes the flow of work
items through various stages of the workflow. The horizontal distance between the points where
work items enter and leave a particular stage represents the lead time. By calculating this distance
over multiple items, teams can determine the average lead time, providing insights into process
efficiency and areas for potential improvement.
What is the primary measurement during Inspect and Adapt?
A
Explanation:
The primary measurement during the Inspect and Adapt (I&A) event in SAFe is the program
predictability measure. This metric assesses the Agile Release Train's (ART) ability to deliver on its
commitments within a Program Increment (PI). It helps teams understand how accurately they can
plan and execute work, providing a basis for continuous improvement. By focusing on predictability,
organizations can improve their planning processes, align better with business objectives, and ensure
more reliable delivery of value.
A team integrates and tests the Stories on the last day of the Iteration. This has become a pattern for
the last three Iterations. Why is this considered an anti-pattern?
A
Explanation:
Waterfalling the Iteration: The term "waterfalling" in an Agile context refers to the anti-pattern
where teams delay integration, testing, and other critical activities until the end of the iteration,
mimicking the Waterfall model of sequential phases.
Agile Practice: In Agile, the goal is to continuously integrate and test stories throughout the iteration.
This practice ensures that issues are identified and addressed early, and the product increment is
always in a potentially shippable state.
Anti-pattern Explanation: Integrating and testing stories only on the last day of the iteration means
the team is not practicing continuous integration. This can lead to hidden defects, reduced quality,
and last-minute rushes that jeopardize the team's ability to meet commitments effectively.
SAFe Scrum Master Reference:
SAFe emphasizes continuous integration and regular testing as key practices to maintain quality and
agility. Delaying these activities to the end of the iteration undermines these principles and can lead
to significant issues.
What is a benefit of an Agile Release Train that has both cadence and synchronization?
D
Explanation:
Cadence: Refers to a regular, predictable schedule that sets the rhythm for the team or ART (Agile
Release Train) activities. It helps in aligning planning, development, and delivery cycles.
Synchronization: Ensures that multiple teams or ARTs work together in harmony, aligning their
schedules, dependencies, and delivery efforts.
Benefit Explanation: Having both cadence and synchronization means that all teams within the ART
are working in a coordinated manner, iterating together. This alignment ensures that dependencies
are managed, integration happens regularly, and the system evolves cohesively.
SAFe Scrum Master Reference:
SAFe promotes cadence and synchronization to manage complex dependencies and ensure that all
parts of the system evolve together, enhancing overall system integrity and quality.
A Scrum Master is asked to help an Agile Release Train that has struggled through multiple Pls. They
just finished the second Iteration in the current PI and have nothing to show at the System Demo.
The ART stakeholders are concerned. What should be done?
A
Explanation:
Problem Statement: The ART has nothing to show at the System Demo, indicating potential issues
with integration, quality, or coordination among teams.
Recommended Action: Stopping new development work to focus on integrating and testing the
system allows the team to identify and resolve integration issues, ensuring that the system is in a
stable state.
Scope Adjustment: Based on what is learned during integration and testing, the scope can be
adjusted to focus on delivering a coherent and functional system increment.
SAFe Scrum Master Reference:
SAFe emphasizes the importance of a stable, integrated system increment to demonstrate progress
and ensure quality. Addressing integration issues promptly is crucial for maintaining stakeholder
confidence and delivering value.
Which two statements are true about a Feature? (Choose two.)
B, C
Explanation:
Completed by a Single Agile Release Train within one PI:
Definition: A Feature in SAFe is a service or functionality that meets the needs of a customer and can
be delivered within a single Program Increment (PI) by an ART.
Explanation: Features are planned and delivered within the timeframe of a PI, ensuring that they
provide tangible value and align with the ART's objectives.
Prioritized using Weighted Shortest Job First (WSJF):
Definition: WSJF is a prioritization method used in SAFe to sequence work for maximum economic
benefit.
Explanation: Features are prioritized based on their cost of delay and the effort required to
implement them. This ensures that the most valuable and impactful features are delivered first.
SAFe Scrum Master Reference:
SAFe framework details the concept of Features, emphasizing their completion within a PI and their
prioritization using WSJF to maximize value delivery.