Question 1

How can a Scrum Master help the team remain focused on achieving their Iteration goals?

Accepted Answer

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 2

What is one problem with phase-gate Milestones?

Accepted Answer

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 3

What is the purpose of the retrospective held during an Inspect and Adapt event?

Accepted Answer

B

Explanation: Inspect and Adapt (I&A) Event: This event includes a retrospective aimed at reviewing the past Program Increment (PI) and identifying issues that need to be addressed. Purpose of Retrospective: The retrospective helps the team reflect on what went well, what didn’t, and why. It is used to identify specific problems and root causes that will be addressed in the subsequent problem-solving workshop. Outcome: The issues identified during the retrospective form the basis for the problem-solving workshop, where the team collaboratively develops action plans to improve processes and outcomes. SAFe Scrum Master Reference: The I&A event in SAFe is designed to foster continuous improvement by systematically identifying and addressing issues through structured retrospectives and problem-solving workshops.

Question 4

What is one outcome of an integration point?

Accepted Answer

A

Explanation: Integration points in agile development serve as critical junctures where progress is reviewed, and decisions can be made on whether to continue on the current path or pivot based on new information. Integration Points: Regular integration points help in verifying progress, ensuring alignment with objectives, and assessing whether the current approach is delivering the desired outcomes. Pivot or Persevere: These points provide the opportunity to pivot if necessary. Teams can change their course of action based on feedback, new insights, or changing requirements, ensuring that the final product meets the needs effectively. Risk Mitigation: Regular integration reduces the risk of late discovery of issues and ensures that the product evolves in a way that adds value continuously. SAFe Scrum Master Reference: SAFe Advanced Scrum Master Training Material, Chapter on Iteration Execution​​.

Question 5

What is the output of an Inspect and Adapt event?

Accepted Answer

C

Explanation: The Inspect and Adapt (I&A) event is a critical component in the SAFe framework, held at the end of each Program Increment (PI). The main output of the I&A event is a set of improvement items that are intended to be actioned in the next PI Planning event. This helps in ensuring continuous improvement in the process and products. PI System Demo: Demonstrates the current state of the solution and provides an opportunity for the stakeholders to inspect the progress. Quantitative Measurement: Teams review metrics that reflect the current state of the development process. Problem-Solving Workshop: Identifies root causes of the biggest problems and formulates improvement items. Improvement Backlog: The improvement items identified are prioritized and added to the team's backlog for the next PI. This cycle of continuous feedback and improvement helps in refining the development process and enhancing the team's performance. SAFe Scrum Master Reference: SAFe Advanced Scrum Master Training Material, Chapter on Inspect and Adapt​​.

Question 6

How is team performance calculated in SAFe?

Accepted Answer

C

Explanation: Team Performance Measurement: In SAFe, one of the key metrics for measuring team performance is the ratio of Story points completed to Story points planned in the Program Increment (PI). Story Points: Represent the effort required to complete user stories. By comparing planned and completed Story points, teams can gauge their ability to deliver on commitments. Purpose: This metric helps in assessing how well the team is performing relative to their planned objectives, identifying areas for improvement, and making adjustments for future PIs. SAFe Scrum Master Reference: SAFe provides guidance on using Story points and other metrics to measure team performance and drive continuous improvement.

Question 7

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?

Accepted Answer

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 8

What are the benefits of organizing teams around Features?

Accepted Answer

B

Explanation: Organizing teams around Features can significantly reduce dependencies between teams. When teams are aligned to deliver specific features, they have more autonomy and can work more independently, without needing to wait for other teams to complete their parts. This alignment minimizes coordination and dependency management overhead, enabling faster and more efficient delivery. It also allows teams to focus on delivering end-to-end functionality, which enhances the quality and coherence of the product. SAFe Scrum Master Reference SAFe 5.0 framework: principles of organizing teams around features to reduce dependencies SAFe Agile Teams: benefits of feature-based team organization

Question 9

What is one way a Scrum Master can gain the confidence of a stakeholder?

Accepted Answer

D

Explanation: One way a Scrum Master can gain the confidence of a stakeholder is by making the process visible. Transparency is a key principle in Agile and SAFe, as it builds trust and ensures that stakeholders are well-informed about the progress, challenges, and successes of the team. By making the process visible through tools like information radiators, progress charts, and regular updates, the Scrum Master can demonstrate accountability, foster open communication, and build stakeholder confidence in the team's ability to deliver value. SAFe Scrum Master Reference SAFe Principles: transparency and visibility SAFe 5.0 framework: building stakeholder confidence through visible processes

Question 10

What is one requirement for achieving Continuous Deployment?

Accepted Answer

A

Explanation: Achieving Continuous Deployment involves several practices, one of which is decoupling deployment from release. This means that code can be deployed to production continuously and automatically, but it is only released to end-users when it is appropriate. Decoupling these processes allows for more frequent and reliable deployments without affecting the user experience until the features are ready for release. This practice helps in maintaining system stability and enabling faster feedback loops. SAFe Scrum Master Reference SAFe Continuous Delivery Pipeline: practices for Continuous Deployment SAFe 5.0 framework: decoupling deployment and release for continuous improvement

Question 11

Why is the program predictability measure the primary Metric used during the quantitative measurement part of the Inspect and Adapt event?

Accepted Answer

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 12

Why are phase-gate Milestones problematic?

Accepted Answer

C

Explanation: Phase-gate milestones are problematic because they often use documentation as a proxy for solution progress. This approach assumes that completing certain documents or passing through predefined gates accurately reflects the progress of the solution. However, in Agile methodologies, working software is the primary measure of progress. Relying on documentation can lead to a false sense of security, where teams believe they are on track based on completed paperwork rather than actual working software. This can delay the discovery of issues and hinder the ability to make necessary adjustments in a timely manner. SAFe Scrum Master Reference SAFe Principles: valuing working software over comprehensive documentation SAFe 5.0 framework: the drawbacks of phase-gate milestones and the emphasis on iterative progress with working solutions

Question 13

Lee is a developer on the team. At every daily stand-up Lee reports, "Yesterday, I worked on indexing.
Today, I will work on indexing. I have no impediments." What coaching should the Scrum Master
provide Lee to improve the team's visibility into his work?

Accepted Answer

D

Explanation: The Scrum Master should coach Lee to discuss his progress in the context of the Iteration goals. By framing his updates around how his work contributes to the broader objectives of the iteration, Lee can provide the team with better visibility into his progress and the impact of his work. This approach encourages team members to think beyond individual tasks and understand how their efforts align with the team's goals, fostering greater collaboration and accountability. SAFe Scrum Master Reference SAFe Principles: focusing on outcomes and aligning individual efforts with team goals SAFe 5.0 framework: effective daily stand-up practices

Question 14

The work within one state of a team's Kanban board is being completed at varying times, sometimes running faster and sometimes slower than the next state. What could resolve this issue?

Accepted Answer

C

Explanation: Creating a buffer state between two states in a Kanban board can help regulate the flow of work and address the varying completion times. Buffer State Purpose: Acts as a holding area to balance the flow between different stages of work, smoothing out variances in completion times. Flow Regulation: Ensures that work can continue smoothly without bottlenecks or idle times. Work In Progress (WIP) Limits: Helps maintain a steady flow by preventing too much work from accumulating in any one state. This approach aligns with Lean principles of managing flow and reducing variability in processes. SAFe Scrum Master Reference: SAFe Advanced Scrum Master Training Material, Chapter on Kanban Systems​​.

Question 15

Which two statements are true about a Feature? (Choose two.)

Accepted Answer

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.

Free Scaled Agile Safe-SASM Actual Exam Questions