Scaled Agile SAFE-SSM Online Practice Questions and Exam Preparation

Scaled Agile SAFE-SSM Online Questions & Answers

• Question 11:

  Team A wants to use the IP Iteration to continue their "usual work." What is one benefit the Scrum Master/Team Coach could share with the team about using the IP Iteration as intended?

  A. The team can consider additional retrospective action items
  B. The team can perform needed system maintenance
  C. The team can participate in hackathons
  D. The team can find time to participate in ad hoc groups
  C. The team can participate in hackathons

  ---

  Explanation

  Hackathons are one of the activities that can be done during the IP Iteration to foster innovation and learning. They allow the team members to work on whatever they want, with whomever they want, as long as the work reflects the mission of the company. The teams then demo their work to others at the end of the hackathon. Hackathons can help the team explore new ideas, technologies, and solutions that can benefit the business and the customers. They can also increase the team's engagement, creativity, and collaboration.

  References: Innovation and Planning Iteration - Scaled Agile Framework, Exam Study Guide: SSM (6.0) - SAFeScrum Master

• Question 12:

  What is one method a Scrum Master/Team Coach can use to help teams overcome a fear of conflict?

  A. Enforcing work-in-process limits
  B. Giving every team member the opportunity to contribute
  C. Scheduling regular Team Syncs
  D. Aligning to shared commitments
  B. Giving every team member the opportunity to contribute

  ---

  Explanation

  One method a Scrum Master/Team Coach can use to help teams overcome a fear of conflict is to give every team member the opportunity to contribute. Fear of conflict is one of the common dysfunctions of a team, which can result in artificial harmony, lack of trust, and avoidance of issues To overcome this fear, the Scrum Master/Team Coach can facilitate a safe and respectful environment where team members can express their opinions, ideas, and concerns without being judged, ignored, or attacked Giving every team member the opportunity to contribute can help them feel valued, respected, and heard, as well as foster a culture of collaboration, feedback, and learning The Scrum Master/Team Coach can use various techniques to ensure equal participation, such as round-robin, fist of five, dot voting, silent brainstorming, and liberating structures By encouraging healthy and constructive conflict, the Scrum Master/Team Coach can help the team improve their performance, creativity, and innovation

• Question 13:

  How does the "C" in the CALMR approach to DevOps help teams manage tensions caused by differing needs?

  A. By establishing communication between different teams
  B. By creating a culture of shared responsibility
  C. By committing to a balance of speed and quality
  D. By identifying a collaborative approach to deployment
  B. By creating a culture of shared responsibility

  ---

  Explanation

  The "C" in the CALMR approach to DevOps stands for culture, which is the foundation of successful DevOps adoption. Culture refers to the values, beliefs, and behaviors that guide the collaboration and alignment of everyone in the value stream. By creating a culture of shared responsibility, teams can manage the tensions caused by differing needs, such as speed, quality, security, and stability. A culture of shared responsibility means that everyone is accountable for the outcomes of their work, and that they work together to deliver value to the customers. It also means that teams respect each other's roles and expertise, and seek feedback and learning opportunities. A culture of shared responsibility fosters trust, transparency, and continuous improvement, which are essential for DevOps.

  References: CALMR - Scaled Agile Framework The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

• Question 14:

  What is one way a Scrum Master/Team Coach can support Iteration Execution?

  A. Build value stream maps
  B. Assign story points for each User Story
  C. Facilitate team events
  D. Prioritize the team backlog
  C. Facilitate team events

  ---

  Explanation

  One of the main responsibilities of a Scrum Master/Team Coach is to facilitate team events, such as Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective. These events help the team to plan, execute, inspect, and adapt their work throughout the Iteration. By facilitating these events, the Scrum Master/Team Coach ensures that the team follows the Agile principles and practices, collaborates effectively, anddelivers value to the customers and stakeholders. (Must be taken from SAFe 6 Scrum Master resources)

  References: SAFe Scrum Master Course Outline Iteration Execution Iterations

• Question 15:

  What is the intended value of the Backlog Refinement event?

  A. The team is able to prepare requirements for Iteration Planning
  B. The team aligns on the progress of Iteration Goals
  C. The team is able to commit to a set of goals to be delivered in the Iteration
  D. The team reviews and improves processes before the next Iteration
  A. The team is able to prepare requirements for Iteration Planning

  ---

  Explanation

  The intended value of the Backlog Refinement event is that the team is able to prepare requirements for Iteration Planning. Backlog Refinement is an ongoing process where theteam collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1 One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable, and small enough to be completed in a single Iteration2 By doing so, the team can improve the quality, efficiency, and effectiveness of their work, as well as deliver value to the customers and the organization123

  References: Team Backlog - Scaled Agile Framework Backlog Refinement - Scaled Agile Framework What is backlog refinement? | Miro

• Question 16:

  What is one benefit of holding regular system demos?

  A. Problems can be escalated to ART leadership
  B. Execution can be measured across the whole ART
  C. Bottlenecks can be identified early by the teams
  D. Deliverables are reviewed with stakeholders
  B. Execution can be measured across the whole ART

  ---

  Explanation

  One benefit of holding regular system demos is that execution can be measured across the whole ART. A system demo is a significant event that provides an integrated view of new Features for the most recent Iteration delivered by all the teams in the Agile Release Train (ART). Each demo gives ART stakeholders an objective measure of progress during a Program Increment (PI). The system demo offers the ART a fact-based measure of current, system-level progress within the PI. It's the true measure of ART velocity and progress. Achieving this requires implementing the scalable engineering practices necessary to support Continuous Integration across the ART. By holding regular system demos, the ART can evaluate the quality, functionality, and usability of the solution, as well as identify and resolve any issues, risks, or dependencies. The system demo also provides an opportunity for feedback and learning from the customers, Business Owners, and other stakeholders, which can help the ART to align with the vision and goals, and to adapt to changing needs and expectations. (Must be taken from SAFe 6 Scrum Master resources)

  References: System Demo - Scaled Agile Framework SAFe Scrum Master Course Outline

• Question 17:

  What is one purpose of Iteration Goals?

  A. To identify what to present in System Demo
  B. To communicate which Stories will be completed during the Iteration
  C. To align team members to common objectives
  D. To get feedback from the organization
  C. To align team members to common objectives

  ---

  Explanation

  One purpose of iteration goals is to align team members to a common purpose and vision. Iteration goals are a high-level summary of the business and technical goals that an Agile Team agrees to accomplish in an iteration. They help the team and the product owner to reach agreement on the business value they intend to deliver, align their work to their team PI objectives, and ground everyone on their shared purpose. Iteration goals also provide transparency and management information, as well as support the coordination and dependency management of the Agile Release Train (ART).

  References: Iteration Goals - Scaled Agile Framework Exam Study Guide: SSM (6.0) - SAFeScrum Master

• Question 18:

  What is one example of an Agile Team development practice?

  A. Tracking regulations
  B. Writing requirements
  C. Demoing frequently
  D. Visualizing effort
  C. Demoing frequently

  ---

  Explanation

  One example of an Agile Team development practice is to demo working functionality frequently to the product owner and other stakeholders. This practice helps the team to get fast feedback, validate their assumptions, and ensure that they are delivering value that meets the customer needs and expectations. Demoing frequently also helps the team to improve the quality of their work, as they have to ensure that the functionality is tested and meets the definition of done before showing it to others. Demoing frequently is part of the SAFe Scrum and SAFe Team Kanban practices, and is done at the end of each iteration in the Iteration Review event.

  References: Iteration Review - Scaled Agile Framework SAFe Team Kanban - Scaled Agile Framework Agile Teams - Scaled Agile Framework

• Question 19:

  During which of the following Agile Team events do team members estimate relative story sizes?

  A. Backlog Refinement
  B. Iteration Review
  C. Iteration Planning
  D. Iteration Retrospective
  A. Backlog Refinement

  ---

  Explanation

  Backlog Refinement is the Agile Team event where team members estimate relative story sizes. Backlog Refinement is an ongoing process where the team collaborates with the Product Owner and other stakeholders to review, split, prioritize, and estimate the stories in the Team Backlog1 One of the main objectives of Backlog Refinement is to ensure that the stories are ready for Iteration Planning, which means they are clear, feasible, testable,and small enough to be completed in a single iteration2 To achieve this, the team uses relative story sizing, which is a technique to compare the effort, complexity, and uncertainty of different stories based on a common reference point3 Relative story sizing helps the team to create a consistent and shared understanding of the scope and value of the work, as well as to optimize the flow and predictability of the delivery process4 The team can use various methods to estimate relative story sizes, such as story points, T-shirt sizes, or Fibonacci numbers35 (Must be taken from SAFe 6 Scrum Master resources)

  References: Team Backlog - Scaled Agile Framework Backlog Refinement - Scaled Agile Framework Story - Scaled Agile Framework How to Estimate Agile Stories: Introducing Relative Sizing - LeanDog Why Your Agile Team Should Use Relative Story Point Estimation

• Question 20:

  Team A has decided to use the IP Iteration to continue the finalizing Feature delivery work they have been working on for the past two Iterations. What is one effect Team A might experience by continuing to stay heads-down rather than using the IP Iteration as intended?

  A. Individual team members could lose an opportunity to learn from one another
  B. Individual team members could lose an opportunity to keep their technical skills current
  C. Individual team members could lose an opportunity to consider their team work more holistically
  D. Individual team members could lose an opportunity to refresh their motivation
  C. Individual team members could lose an opportunity to consider their team work more holistically

  ---

  Explanation

  By continuing to stay heads-down on the finalizing Feature delivery work, Team A might miss the chance to reflect on their team work more holistically and identify areas for improvement. The IP Iteration is intended to provide time for the team to participate in the Inspect and Adapt event, where they can review their PI performance, analyze the root causes of any issues, and create an improvement backlog. The IP Iteration also allows the team to engage in innovation and learning activities, such as hackathons, that can foster creativity, collaboration, and experimentation. These activities can help the team generate new ideas, solutions, and feedback that can benefit their future work. By skipping the IP Iteration, Team A might lose the opportunity to learn from their past experiences, improve their processes, and innovate their products.

  References: Innovation and Planning Iteration

  - Scaled Agile Framework, Exam Study Guide: SSM (6.0) - SAFeScrum Master