Question #1
What are two timestamps required to measure lead time when using a Team Kanban board? (Choose two.)
- A . When the Story is released to users and validated
- B . When the Story is deployed
- C . When the Agile Team pulls a Story onto the board
- D . When the Story is accepted by the Product Owner
- E . When the team completes validation of the Story
Correct Answer: C, D
C, D
Explanation:
In SAFe (Scaled Agile Framework), lead time is an essential metric used to measure the efficiency and effectiveness of a process. Lead time is defined as the total time it takes for a work item to move through the entire process from the moment it is initiated until it is completed.
To measure lead time accurately using a Team Kanban board, two specific timestamps are crucial:
When the Agile Team pulls a Story onto the board (Timestamp C):
This is the starting point of the lead time. It marks the moment when the team commits to working on a particular story by pulling it into the workflow. This action indicates that the story is now in progress and the clock starts ticking from this point.
When the Story is accepted by the Product Owner (Timestamp D):
This is the endpoint of the lead time. It signifies that the story has been completed to the satisfaction of the team and has met the acceptance criteria defined by the Product Owner. When the Product Owner accepts the story, it indicates that the work is done and the lead time measurement stops. These two timestamps effectively capture the duration a story takes to go through the development process, providing valuable insights into process efficiency and identifying areas for improvement. SAFe Scrum Master Reference
SAFe Advanced Scrum Master learning materials
SAFe 5.0 Scrum Master Certification resources
The 2020 Scrum Guide: Scrum Guide 2020
This information aligns with the principles and practices outlined in the SAFe framework and the Scrum Guide, ensuring a comprehensive understanding of lead time measurement within a Team Kanban board context.
C, D
Explanation:
In SAFe (Scaled Agile Framework), lead time is an essential metric used to measure the efficiency and effectiveness of a process. Lead time is defined as the total time it takes for a work item to move through the entire process from the moment it is initiated until it is completed.
To measure lead time accurately using a Team Kanban board, two specific timestamps are crucial:
When the Agile Team pulls a Story onto the board (Timestamp C):
This is the starting point of the lead time. It marks the moment when the team commits to working on a particular story by pulling it into the workflow. This action indicates that the story is now in progress and the clock starts ticking from this point.
When the Story is accepted by the Product Owner (Timestamp D):
This is the endpoint of the lead time. It signifies that the story has been completed to the satisfaction of the team and has met the acceptance criteria defined by the Product Owner. When the Product Owner accepts the story, it indicates that the work is done and the lead time measurement stops. These two timestamps effectively capture the duration a story takes to go through the development process, providing valuable insights into process efficiency and identifying areas for improvement. SAFe Scrum Master Reference
SAFe Advanced Scrum Master learning materials
SAFe 5.0 Scrum Master Certification resources
The 2020 Scrum Guide: Scrum Guide 2020
This information aligns with the principles and practices outlined in the SAFe framework and the Scrum Guide, ensuring a comprehensive understanding of lead time measurement within a Team Kanban board context.
Question #2
Which two events provide opportunities for the team to collaborate? (Choose two.)
- A . Iteration Planning
- B . Portfolio Sync
- C . Solution Demo
- D . Pre-PI Planning
- E . Backlog refinement
Correct Answer: A, E
A, E
Explanation:
Iteration Planning:
Purpose: Iteration Planning is a crucial event where the team collaborates to determine what will be delivered in the upcoming iteration and how the work will be accomplished. The entire team,
including the Scrum Master, Product Owner, and Developers, come together to plan the iteration’s work.
Process:
The Product Owner presents the prioritized backlog items to the team.
The team discusses each item, clarifies any ambiguities, and breaks down the items into tasks. The team estimates the effort required for each task and commits to what they believe can be achieved in the iteration.
Outcome: A detailed iteration plan that includes the selected backlog items and a clear understanding of the tasks and responsibilities for each team member. Backlog Refinement:
Purpose: Backlog Refinement (also known as Grooming) is an ongoing process where the team and
the Product Owner collaborate to review and update the backlog. This ensures that the backlog is in
good shape for future iteration planning.
Process:
The team reviews the items in the backlog to ensure they are well understood and ready for future iterations.
The Product Owner provides context and clarifications for each backlog item.
The team discusses the requirements, refines the acceptance criteria, and estimates the effort required for each item.
The backlog items are prioritized based on their value and urgency.
Outcome: A well-maintained and prioritized backlog that facilitates effective and efficient iteration planning.
SAFe Scrum Master
Reference: Iteration Planning:
SAFe Advanced Scrum Master training materials emphasize the importance of Iteration Planning as a key event for team collaboration, ensuring everyone is aligned on the iteration goals and tasks.
2020 Scrum Guide: The Iteration Planning section outlines the collaborative nature of this event and its role in setting the stage for successful iterations. Backlog Refinement:
In the SAFe framework, Backlog Refinement is highlighted as an essential activity to maintain a healthy backlog, allowing the team to prepare for future iterations effectively.
Scrum Open: This document discusses the significance of Backlog Refinement in fostering team collaboration and ensuring the backlog is well-groomed and ready for planning.
A, E
Explanation:
Iteration Planning:
Purpose: Iteration Planning is a crucial event where the team collaborates to determine what will be delivered in the upcoming iteration and how the work will be accomplished. The entire team,
including the Scrum Master, Product Owner, and Developers, come together to plan the iteration’s work.
Process:
The Product Owner presents the prioritized backlog items to the team.
The team discusses each item, clarifies any ambiguities, and breaks down the items into tasks. The team estimates the effort required for each task and commits to what they believe can be achieved in the iteration.
Outcome: A detailed iteration plan that includes the selected backlog items and a clear understanding of the tasks and responsibilities for each team member. Backlog Refinement:
Purpose: Backlog Refinement (also known as Grooming) is an ongoing process where the team and
the Product Owner collaborate to review and update the backlog. This ensures that the backlog is in
good shape for future iteration planning.
Process:
The team reviews the items in the backlog to ensure they are well understood and ready for future iterations.
The Product Owner provides context and clarifications for each backlog item.
The team discusses the requirements, refines the acceptance criteria, and estimates the effort required for each item.
The backlog items are prioritized based on their value and urgency.
Outcome: A well-maintained and prioritized backlog that facilitates effective and efficient iteration planning.
SAFe Scrum Master
Reference: Iteration Planning:
SAFe Advanced Scrum Master training materials emphasize the importance of Iteration Planning as a key event for team collaboration, ensuring everyone is aligned on the iteration goals and tasks.
2020 Scrum Guide: The Iteration Planning section outlines the collaborative nature of this event and its role in setting the stage for successful iterations. Backlog Refinement:
In the SAFe framework, Backlog Refinement is highlighted as an essential activity to maintain a healthy backlog, allowing the team to prepare for future iterations effectively.
Scrum Open: This document discusses the significance of Backlog Refinement in fostering team collaboration and ensuring the backlog is well-groomed and ready for planning.
Question #3
Which statement is true about batch size, lead time, and utilization?
- A . Higher team member utilization leads to longer lead times
- B . There is no direct relationship between lead time and utilization
- C . As batch size increases, lead time decreases
- D . There is no direct relationship between lead time and batch size
Correct Answer: A
A
Explanation:
Utilization refers to the percentage of a team’s capacity that is being used. When team members are highly utilized (i.e., their capacity is nearly fully booked), it often leads to longer lead times.
This is because:
High utilization reduces the team’s flexibility to handle new or unexpected work.
It can cause bottlenecks as individuals or teams become overburdened with tasks.
There is less room for managing variability, leading to delays and increased cycle times.
In contrast, lower utilization rates typically allow for more flexibility and quicker response times, reducing lead times. Therefore, higher utilization generally results in longer lead times due to increased bottlenecks and reduced capacity to handle new tasks efficiently. SAFe Scrum Master Reference
SAFe Advanced Scrum Master learning materials
Principles of Lean-Agile development: optimizing flow by managing queue lengths and reducing batch sizes to improve lead times and throughput.
A
Explanation:
Utilization refers to the percentage of a team’s capacity that is being used. When team members are highly utilized (i.e., their capacity is nearly fully booked), it often leads to longer lead times.
This is because:
High utilization reduces the team’s flexibility to handle new or unexpected work.
It can cause bottlenecks as individuals or teams become overburdened with tasks.
There is less room for managing variability, leading to delays and increased cycle times.
In contrast, lower utilization rates typically allow for more flexibility and quicker response times, reducing lead times. Therefore, higher utilization generally results in longer lead times due to increased bottlenecks and reduced capacity to handle new tasks efficiently. SAFe Scrum Master Reference
SAFe Advanced Scrum Master learning materials
Principles of Lean-Agile development: optimizing flow by managing queue lengths and reducing batch sizes to improve lead times and throughput.
Question #4
How can a Scrum Master help the team remain focused on achieving their Iteration goals?
- A . By supporting the rules of the team process
- B . By leading a team’s efforts in relentless improvements
- C . By eliminating impediments
- D . By exhibiting Lean-Agile Leadership
Correct Answer: C
C
Explanation:
One of the key responsibilities of a Scrum Master is to help the team stay focused on their Iteration goals. This involves removing any obstacles or impediments that may hinder their progress. By eliminating impediments, the Scrum Master ensures that the team can work more efficiently and effectively, thereby maintaining their focus on achieving the goals set for the iteration.
Steps to eliminate impediments include:
Regularly communicating with the team to identify any obstacles they are facing.
Collaborating with stakeholders and other teams to resolve issues quickly.
Ensuring that any identified impediments are documented and tracked until they are resolved. Facilitating problem-solving sessions and using techniques such as root cause analysis to address
underlying issues.
By proactively removing these barriers, the Scrum Master supports the team in maintaining a steady and uninterrupted workflow, which is crucial for meeting iteration goals. SAFe Scrum Master Reference
SAFe Scrum Master Role and Responsibilities
The 2020 Scrum Guide: Scrum Guide 2020
Principles of Lean-Agile Leadership in SAFe: focusing on continuous improvement and supporting the team in overcoming obstacles.
C
Explanation:
One of the key responsibilities of a Scrum Master is to help the team stay focused on their Iteration goals. This involves removing any obstacles or impediments that may hinder their progress. By eliminating impediments, the Scrum Master ensures that the team can work more efficiently and effectively, thereby maintaining their focus on achieving the goals set for the iteration.
Steps to eliminate impediments include:
Regularly communicating with the team to identify any obstacles they are facing.
Collaborating with stakeholders and other teams to resolve issues quickly.
Ensuring that any identified impediments are documented and tracked until they are resolved. Facilitating problem-solving sessions and using techniques such as root cause analysis to address
underlying issues.
By proactively removing these barriers, the Scrum Master supports the team in maintaining a steady and uninterrupted workflow, which is crucial for meeting iteration goals. SAFe Scrum Master Reference
SAFe Scrum Master Role and Responsibilities
The 2020 Scrum Guide: Scrum Guide 2020
Principles of Lean-Agile Leadership in SAFe: focusing on continuous improvement and supporting the team in overcoming obstacles.
Question #5
Which of the SAFe Core Values enables trust across the ART?
- A . Transparency
- B . Adaptation
- C . Built-in Quality
- D . Decentralized decision-making
Correct Answer: A
A
Explanation:
SAFe Core Values are the fundamental beliefs that guide behaviors and decision-making in SAFe (Scaled Agile Framework). They are critical for fostering a culture that supports Lean-Agile principles.
Transparency:
Definition: Transparency in SAFe means having an open and honest environment where everyone has access to the information they need. It involves making work visible to all stakeholders, sharing risks, and ensuring that everyone understands the status of the work.
Importance: Transparency enables trust across the Agile Release Train (ART) because it ensures that everyone is aware of what is happening, leading to informed decision-making and reducing misunderstandings. It builds a culture of openness and accountability.
SAFe Framework
Reference: In SAFe, transparency is crucial for effective collaboration and alignment across teams and stakeholders. It ensures that progress, challenges, and changes are communicated openly, fostering trust and collective problem-solving. SAFe Scrum Master
Reference: SAFe training materials emphasize the importance of transparency as a core value that underpins trust and collaboration within and across teams.
The SAFe website and guides detail how transparency is implemented through various practices like visual management, open communication, and regular feedback loops.
A
Explanation:
SAFe Core Values are the fundamental beliefs that guide behaviors and decision-making in SAFe (Scaled Agile Framework). They are critical for fostering a culture that supports Lean-Agile principles.
Transparency:
Definition: Transparency in SAFe means having an open and honest environment where everyone has access to the information they need. It involves making work visible to all stakeholders, sharing risks, and ensuring that everyone understands the status of the work.
Importance: Transparency enables trust across the Agile Release Train (ART) because it ensures that everyone is aware of what is happening, leading to informed decision-making and reducing misunderstandings. It builds a culture of openness and accountability.
SAFe Framework
Reference: In SAFe, transparency is crucial for effective collaboration and alignment across teams and stakeholders. It ensures that progress, challenges, and changes are communicated openly, fostering trust and collective problem-solving. SAFe Scrum Master
Reference: SAFe training materials emphasize the importance of transparency as a core value that underpins trust and collaboration within and across teams.
The SAFe website and guides detail how transparency is implemented through various practices like visual management, open communication, and regular feedback loops.
Question #6
Which two Framework elements would a Scrum Master have the strongest connection and most frequent interaction? (Choose two.)
- A . Business Owners
- B . Release Train Engineer
- C . Systems Team
- D . Product Owner
- E . Epic Owner
Correct Answer: B, D
B, D
Explanation:
Release Train Engineer (RTE):
Role: The RTE is a servant leader and coach for the Agile Release Train (ART). They facilitate ART events and processes, assist teams in delivering value, and help manage risks and dependencies. Interaction with Scrum Master:
Scrum Masters frequently collaborate with the RTE to coordinate cross-team activities and dependencies.
They work together during events like PI Planning, Scrum of Scrums, and Inspect & Adapt (I&A) workshops to ensure alignment and continuous improvement.
The RTE provides support and guidance to Scrum Masters, helping them resolve impediments that
affect the ART.
Product Owner (PO):
Role: The Product Owner is responsible for defining and prioritizing the team backlog, ensuring that
the team is working on the most valuable tasks.
Interaction with Scrum Master:
Scrum Masters work closely with Product Owners to facilitate effective backlog refinement sessions, ensuring that the backlog items are well-understood and ready for iteration planning.
They support the Product Owner in maintaining a clear and prioritized backlog, helping to communicate the vision and goals to the team.
During iteration planning and reviews, Scrum Masters assist Product Owners in engaging with the team and stakeholders, ensuring that feedback is collected and incorporated. SAFe Scrum Master
Reference: Release Train Engineer:
SAFe materials outline the critical role of the RTE in coordinating the ART and supporting Scrum Masters in their efforts to remove impediments and ensure smooth execution of plans.
Scrum Open: Discusses the collaborative relationship between Scrum Masters and RTEs in facilitating
ART events and managing dependencies.
Product Owner:
The SAFe framework emphasizes the importance of the Scrum Master-Product Owner partnership in driving the delivery of value and maintaining a healthy backlog.
Product Owner Open: Provides insights into how Scrum Masters and Product Owners work together to align on priorities and ensure the team is focused on the right tasks.
B, D
Explanation:
Release Train Engineer (RTE):
Role: The RTE is a servant leader and coach for the Agile Release Train (ART). They facilitate ART events and processes, assist teams in delivering value, and help manage risks and dependencies. Interaction with Scrum Master:
Scrum Masters frequently collaborate with the RTE to coordinate cross-team activities and dependencies.
They work together during events like PI Planning, Scrum of Scrums, and Inspect & Adapt (I&A) workshops to ensure alignment and continuous improvement.
The RTE provides support and guidance to Scrum Masters, helping them resolve impediments that
affect the ART.
Product Owner (PO):
Role: The Product Owner is responsible for defining and prioritizing the team backlog, ensuring that
the team is working on the most valuable tasks.
Interaction with Scrum Master:
Scrum Masters work closely with Product Owners to facilitate effective backlog refinement sessions, ensuring that the backlog items are well-understood and ready for iteration planning.
They support the Product Owner in maintaining a clear and prioritized backlog, helping to communicate the vision and goals to the team.
During iteration planning and reviews, Scrum Masters assist Product Owners in engaging with the team and stakeholders, ensuring that feedback is collected and incorporated. SAFe Scrum Master
Reference: Release Train Engineer:
SAFe materials outline the critical role of the RTE in coordinating the ART and supporting Scrum Masters in their efforts to remove impediments and ensure smooth execution of plans.
Scrum Open: Discusses the collaborative relationship between Scrum Masters and RTEs in facilitating
ART events and managing dependencies.
Product Owner:
The SAFe framework emphasizes the importance of the Scrum Master-Product Owner partnership in driving the delivery of value and maintaining a healthy backlog.
Product Owner Open: Provides insights into how Scrum Masters and Product Owners work together to align on priorities and ensure the team is focused on the right tasks.
Question #7
What is the primary goal of decentralized decision-making?
- A . To resolve dependencies
- B . To minimize VVIP www
- C . To empower knowledge workers
- D . To reduce delay
Correct Answer: D
D
Explanation:
Decentralized decision-making is a principle in SAFe aimed at distributing decision authority to the people closest to the information and most affected by the decisions. The primary goal of decentralized decision-making is to reduce delay in the decision-making process, which can often occur when decisions need to pass through multiple layers of hierarchy. By empowering individuals and teams to make decisions quickly, organizations can respond faster to changes, improve agility, and maintain a steady flow of work.
D
Explanation:
Decentralized decision-making is a principle in SAFe aimed at distributing decision authority to the people closest to the information and most affected by the decisions. The primary goal of decentralized decision-making is to reduce delay in the decision-making process, which can often occur when decisions need to pass through multiple layers of hierarchy. By empowering individuals and teams to make decisions quickly, organizations can respond faster to changes, improve agility, and maintain a steady flow of work.
Question #8
What goes into the Portfolio Backlog?
- A . Strategic Themes
- B . Projects
- C . Capabilities
- D . Epics
Correct Answer: D
D
Explanation:
The Portfolio Backlog in SAFe contains the larger initiatives, known as Epics. Epics are substantial pieces of work that require analysis, investment, and development effort over multiple Program Increments (PIs). They represent significant business or technical needs that drive the long-term strategy of the organization. These Epics are prioritized and managed in the Portfolio Backlog, where they can be decomposed into smaller, actionable items as they progress through the development process.
D
Explanation:
The Portfolio Backlog in SAFe contains the larger initiatives, known as Epics. Epics are substantial pieces of work that require analysis, investment, and development effort over multiple Program Increments (PIs). They represent significant business or technical needs that drive the long-term strategy of the organization. These Epics are prioritized and managed in the Portfolio Backlog, where they can be decomposed into smaller, actionable items as they progress through the development process.
Question #9
Why is the program predictability measure the primary Metric used during the quantitative measurement part of the Inspect and Adapt event?
- A . To measure the predictability of business value delivered in the PI timebox
- B . To predict the scope of the remaining requirements in the Program Backlog
- C . To forecast when remaining features could be delivered to customers
- D . To match customer demand to the Agile Release Train’s velocity
Correct Answer: A
A
Explanation:
The program predictability measure is the primary metric used during the quantitative measurement part of the Inspect and Adapt (I&A) event in SAFe. This measure assesses how reliably the Agile Release Train (ART) can deliver business value within the Program Increment (PI) timebox. It helps to: Evaluate the team’s ability to meet their commitments. Identify areas where predictability can be improved.
Ensure that the business value planned for the PI is actually delivered.
By focusing on the predictability of business value, organizations can better align their planning and execution efforts, ultimately enhancing customer satisfaction and achieving strategic goals more effectively.
SAFe Scrum Master Reference
SAFe Inspect and Adapt events
SAFe 5.0 framework: using program predictability as a key metric to assess and improve ART performance.
A
Explanation:
The program predictability measure is the primary metric used during the quantitative measurement part of the Inspect and Adapt (I&A) event in SAFe. This measure assesses how reliably the Agile Release Train (ART) can deliver business value within the Program Increment (PI) timebox. It helps to: Evaluate the team’s ability to meet their commitments. Identify areas where predictability can be improved.
Ensure that the business value planned for the PI is actually delivered.
By focusing on the predictability of business value, organizations can better align their planning and execution efforts, ultimately enhancing customer satisfaction and achieving strategic goals more effectively.
SAFe Scrum Master Reference
SAFe Inspect and Adapt events
SAFe 5.0 framework: using program predictability as a key metric to assess and improve ART performance.
Question #10
If the distance between the arrival and departure curves on a team’s cumulative flow diagram is growing apart, what is likely happening?
- A . Lead time is increasing
- B . Unplanned work is pushed into the backlog
- C . WIP is decreasing
- D . The backlog is being reprioritized
Correct Answer: A
A
Explanation:
Cumulative Flow Diagram (CFD): A CFD is a visual tool used in Kanban and Scrum to show the progress of work items through different stages of the workflow over time.
Arrival and Departure Curves: These curves represent the work items entering (arrival) and leaving (departure) the system.
Growing Distance: If the distance between the arrival and departure curves on the CFD is growing apart, it indicates that work items are taking longer to move through the system.
Lead Time: This term refers to the total time from when a work item is created until it is completed.
An increasing distance between the curves means that work items are spending more time in the
system, thus increasing the lead time.
SAFe Scrum Master
Reference: SAFe materials on flow metrics and Kanban principles highlight the importance of monitoring lead time and using CFDs to identify bottlenecks and inefficiencies in the workflow.
A
Explanation:
Cumulative Flow Diagram (CFD): A CFD is a visual tool used in Kanban and Scrum to show the progress of work items through different stages of the workflow over time.
Arrival and Departure Curves: These curves represent the work items entering (arrival) and leaving (departure) the system.
Growing Distance: If the distance between the arrival and departure curves on the CFD is growing apart, it indicates that work items are taking longer to move through the system.
Lead Time: This term refers to the total time from when a work item is created until it is completed.
An increasing distance between the curves means that work items are spending more time in the
system, thus increasing the lead time.
SAFe Scrum Master
Reference: SAFe materials on flow metrics and Kanban principles highlight the importance of monitoring lead time and using CFDs to identify bottlenecks and inefficiencies in the workflow.
Question #11
The Agile Team includes the Scrum Master and which other key role?
- A . Product Owner
- B . Release Train Engineer
- C . Project Manager
- D . Product Manager
Correct Answer: A
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.
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.
Question #12
What is the purpose of the Large Solution level in SAFe?
- A . To coordinate the work of multiple Agile Teams on the Agile Release Train (ART)
- B . To regulate large batch delivery across multiple ARTs at the Solution level
- C . To coordinate multiple Agile Release Trains that develop the same Solution
- D . To create large Portfolio-level Solutions that the ART can use to create organizational alignment
Correct Answer: C
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.
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.
Question #13
What is one problem with phase-gate Milestones?
- A . They assume a point Solution exists and can be built right the first time
- B . They force design decisions too late in the process
- C . They account for variability inherent in the process
- D . They require the Product Owner to act as gatekeeper or guardian of the process
Correct Answer: A
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.
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.
Question #14
What is one output from the problem-solving workshop?
- A . ROAMed risks
- B . All the potential Solutions the team could identify
- C . An assessment report
- D . Top improvement items for the next PI
Correct Answer: D
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.
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.
Question #15
How is average lead time measured in a Kanban system?
- A . By taking the average velocity over the last three iterations
- B . Measure the vertical distance between arrival and departure lines on a cumulative flow diagram
- C . Measure the horizontal distance between arrival and departure lines on a cumulative flow diagram
- D . Measure the lead time for at least three items and calculate the statistical mean of the items
Correct Answer: C
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.
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.
Question #16
What is the primary measurement during Inspect and Adapt?
- A . Program predictability measure
- B . Team NPS score
- C . Number of Features delivered
- D . Number of automated tests
Correct Answer: A
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
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.
Question #17
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 . Because the team is waterfalling the Iteration
- B . Because the team demonstrates the full Stories to the Product Owner during the Iteration review
- C . Because the team consistently meets their commitments, and the Product Owner accepts the Stories
- D . Because it is difficult to manage dependencies with other teams
Correct Answer: A
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.
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.
Question #18
What is a benefit of an Agile Release Train that has both cadence and synchronization?
- A . The Agile Release Train is able to control the injection on new work
- B . Dependencies are identified across the Agile Release Train
- C . Teams participate in the portfolio backlog refinement
- D . The entire system is iterating
Correct Answer: D
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.
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.
Question #19
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 . Stop working on any new functionality and fully integrate and test the system; adjust scope based on what is learned
- B . Have every team demonstrate their team increment to the stakeholders separately in the team branch
- C . Find a vendor that specializes in integrating system increments from multiple teams
- D . Re-architect the system so that there are no dependencies between the teams; integration is not required at this time
Correct Answer: A
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.
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.
Question #20
Which two statements are true about a Feature? (Choose two.)
- A . It is developed within a single Agile Team
- B . It is fully completed by a single Agile Release Train within one PI
- C . It is prioritized using weighted shortest job first
- D . It has one Capability as a parent
Correct Answer: B, C
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.
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.
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.
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.
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.
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.