SSM (6.0) - SAFe Scrum Master Questions and Answers
What can a Scrum Master/Team Coach recommend to a team that is showing signs of burnout, not addressing increasing technical debt, and acting out of urgency rather than considering innovation?
Options:
A constructive IP Iteration at the end of each PI
A collective Iteration Review and demo each Iteration
A communicative retrospective at the end of each Iteration
A careful plan at the beginning of each Iteration
Answer:
AExplanation:
A constructive IP Iteration is one of the recommended practices for Scrum Masters/Team Coaches to help teams avoid burnout, address technical debt, and foster innovation. An IP Iteration is a unique, dedicated iteration that occurs every PI and provides an estimating buffer for meeting PI Objectives and dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events. During the IP Iteration, teams can work on activities such as hackathons, research and design, spikes, refactoring, automation, training, and other improvement initiatives that are difficult to fit into a continuous, incremental value delivery pattern. An IP Iteration also allows teams to prepare for and participate in the PI Planning and Inspect and Adapt events, which are essential for alignment, collaboration, and learning across the ART. A constructive IP Iteration can improve the predictability and flow of value delivery, increase employee engagement and satisfaction, enhance the agility and resilience of the teams, and create a competitive advantage for the enterprise.
What is one anti-pattern that emerges when teams do not spend enough time refining the backlog?
Options:
Teams arrive to Team Sync without progress to share
Teams enter retrospectives without improvement ideas
Teams enter new Iterations without enough Stories prepared
Teams arrive to Iteration Planning without specified goals
Answer:
CExplanation:
One anti-pattern that emerges when teams do not spend enough time refining the backlog is that they enter new Iterations without enough Stories prepared. This can result in several negative consequences, such as: 123
The team may struggle to plan and commit to the Iteration Goals, as they lack clarity, feasibility, and testability of the Stories.
The team may face delays, rework, and waste, as they encounter unanticipated dependencies, risks, or technical issues during the Iteration.
The team may deliver low-quality or incomplete Stories, as they rush to meet the Iteration deadlines or compromise on the Definition of Done.
The team may lose focus, alignment, and motivation, as they work on ambiguous or unrealistic Stories that do not deliver value to the customers or the organization.
To avoid this anti-pattern, the team should dedicate sufficient time and effort to refine the backlog on a regular basis, preferably every Iteration123 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 Backlog4 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 organization
What is one Agile development value?
Options:
Healthy interactions over detailed plans
Customer collaboration over contract negotiation
Risk-taking over process development
Working teams over busy individuals
Answer:
BExplanation:
One Agile development value is customer collaboration over contract negotiation. This value is one of the four core values of the Agile Manifesto, which states: “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.” 1 This value emphasizes the importance of building a trusting and collaborative relationship with the customers, rather than relying on rigid and formal contracts that may limit the ability to respond to changing needs and expectations2 Customer collaboration means involving the customers throughout the development process, seeking their feedback, input, and validation, and delivering solutions that meet their requirements and expectations3 Customer collaboration also means respecting the customers’ opinions and perspectives, and resolving any conflicts or issues in a constructive and respectful manner4 Customer collaboration helps the Agile teams to deliver value faster and more effectively, as well as to increase customer satisfaction and loyalty34
What is one benefit of holding regular system demos?
Options:
Problems can be escalated to ART leadership
Execution can be measured across the whole ART
Bottlenecks can be identified early by the teams
Deliverables are reviewed with stakeholders
Answer:
BExplanation:
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.
What is one way a Scrum Master/Team Coach can help improve ART performance?
Options:
Prioritize the ART backlog for PI Planning
Run an Agile Team charter workshop
Communicate the PI Planning agenda
Facilitate cross-team collaboration
Answer:
DExplanation:
According to the SAFe 6 Scrum Master documentation, one of the ways a Scrum Master/Team Coach can help improve ART performance is to facilitate cross-team collaboration. Cross-team collaboration is the ability of Agile teams to work together effectively and efficiently to deliver value to the customers and stakeholders. It involves sharing information, resolving dependencies, aligning on goals, and providing feedback. Cross-team collaboration is essential for achieving the ART vision and objectives, as well as for delivering integrated and high-quality solutions.
The Scrum Master/Team Coach plays a key role in facilitating cross-team collaboration by 1:
Participating in the Scrum of Scrums (SoS) and ART Sync meetings, where they communicate the team’s progress, impediments, and dependencies, and coordinate with other teams and the Release Train Engineer (RTE)
Helping the team prepare for and participate in the PI Planning event, where they collaborate with other teams to define and commit to the PI objectives and identify risks and dependencies
Supporting the team in the System Demo, where they demonstrate the team’s work to other teams and stakeholders, and receive feedback and validation
Assisting the team in the Inspect and Adapt (I&A) event, where they review the ART performance, identify improvement opportunities, and create action plans
Encouraging the team to adopt Communities of Practice (CoPs), where they share knowledge, best practices, and learnings with other teams and experts
Promoting a culture of trust, respect, and cooperation among the team and other teams
What is one anti-pattern of the Inspect and Adapt?
Options:
No actionable improvement Features are created
Not enough team members attend the PI System demo
Too many ideas enter the problem-solving workshop
Only one problem is identified by each team in the retrospective
Answer:
AExplanation:
One anti-pattern of the Inspect and Adapt (I&A) is to have no actionable improvement Features created as a result of the problem-solving workshop. This is considered an anti-pattern because the main goal of the I&A workshop is to identify and address the systemic issues that are limiting the effectiveness of the Agile Release Train (ART). The workshop should produce one or more improvement Features that are added to the ART backlog and prioritized for the next PI Planning event. These Features should be SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) and aligned with the ART vision and goals. Without actionable improvement Features, the ART will miss the opportunity to learn and improve from the feedback and data collected during the PI.
What is one purpose of Iteration Goals?
Options:
To identify what to present in System Demo
To communicate which Stories will be completed during the Iteration
To align team members to common objectives
To get feedback from the organization
Answer:
CExplanation:
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).
What is one way uncommitted objectives help Agile Teams make a plan for the PI?
Options:
They ensure the team has additional development options
They generate additional ways to measure team progress
They create an opportunity for teams to take on harder work
They maintain the predictability of achieving the objectives
Answer:
DExplanation:
One way uncommitted objectives help Agile Teams make a plan for the PI is that they maintain the predictability of achieving the objectives. Uncommitted objectives are PI objectives that are not included in the team’s commitment or counted against teams in the ART predictability measure. They are used to identify work that can be variable within the scope of a PI, such as stretch goals, spikes, innovation, or exploration1 Uncommitted objectives help improve the predictability of delivering business value since they allow the team to adjust their scope based on the actual progress and feedback during the PI. They also provide the team with some flexibility and capacity to respond to changing needs and expectations, as well as to pursue learning and improvement opportunities12
What is one example of an Agile Team development practice?
Options:
Tracking regulations
Writing requirements
Demoing frequently
Visualizing effort
Answer:
CExplanation:
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.
According to SAFe, which of the following types of work should fit into one Iteration for one team?
Options:
Features
Epics
Tasks
Stories
Answer:
DExplanation:
According to the SAFe 6 Scrum Master documentation, the type of work that should fit into one Iteration for one team is a Story. A Story is a short description of a small piece of functionality that provides value to the customer or stakeholder. Stories are derived from Features, which are larger units of value that typically span multiple Iterations. Stories are also decomposed into Tasks, which are the specific activities that the team members perform to implement the Story. Stories are the primary backlog items that the team plans, estimates, and delivers in an Iteration. They are also the basis for defining and committing to the Iteration goals. Stories should be small enough to be completed within one Iteration, and they should meet the definition of ready and the definition of done.
Team A works collaboratively on new functionality for a customer application. The acceptance criteria have each been minimally met.
Team A decides to release the functionality with a method for collecting direct customer feedback. Which of the following high-performing team characteristics is Team A demonstrating?
Options:
Balancing abilities on the team with the challenge of the work
Taking appropriate risks without fear of failure
Focusing on success over trying to avoid failures
Using regular feedback loops built into the learning cycle
Answer:
DExplanation:
One of the high-performing team characteristics that Team A is demonstrating is using regular feedback loops built into the learning cycle. A high-performing Agile Team is a cross-functional group of people that have everything, and everyone, necessary to produce a working, tested increment of product1 They are empowered, collaborative, aligned, and committed to delivering value to the customers and the organization1 One of the factors that enable a high-performing Agile Team is using regular feedback loops to learn and improve. Feedback loops are mechanisms that provide the team with information about the outcomes and impacts of their actions, as well as the needs and expectations of their customers and stakeholders23 Feedback loops help the team to validate their assumptions, measure their progress, and adjust their plans accordingly23 Feedback loops also help the team to foster a culture of experimentation, innovation, and continuous improvement, as well as to increase customer satisfaction and loyalty23 Team A is using regular feedback loops by releasing the functionality with a method for collecting direct customer feedback. This allows them to learn from the actual users of their product, and to incorporate their feedback into the next iteration of development. This way, they can deliver value faster and more effectively, as well as to enhance the quality and usability of their product4
What is one benefit of having an IP Iteration every PI?
Options:
It creates an estimating buffer for meeting PI objectives
It creates a timeboxed opportunity for team growth
It creates a chance for teams to manage quality
It creates a guardrail for teams working too hard
Answer:
AExplanation:
One benefit of having an IP Iteration every PI is that it creates an estimating buffer for meeting PI objectives. PI objectives are a set of SMART goals that align the teams and stakeholders to a common vision and mission for the upcoming Program Increment (PI). They are derived from the business context, priorities, and dependencies, and are agreed upon and committed by the teams during PI Planning1 However, since PI objectives are based on estimates and assumptions, there is always a degree of uncertainty and variability in the delivery process. To account for this, SAFe recommends that teams reserve 10% of their capacity for each PI as an estimating buffer. This buffer is used during the IP Iteration, which is a unique, dedicated iteration that occurs every PI and provides dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt events2 By having an IP Iteration as an estimating buffer, the teams can improve the predictability and flow of value delivery, as well as reduce the stress and pressure of meeting the PI objectives23
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?
Options:
The team can consider additional retrospective action items
The team can perform needed system maintenance
The team can participate in hackathons
The team can find time to participate in ad hoc groups
Answer:
CExplanation:
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) - SAFe® Scrum Master
What is one example of Scrum Masters/Team Coaches helping without diminishing the commitment of others?
Options:
Facilitating necessary meetings for the team
Demoing the team's completed work
Encouraging handoffs so each team member contributes to the work
Coaching the team to refrain from relying on external resources
Answer:
AExplanation:
One example of Scrum Masters/Team Coaches helping without diminishing the commitment of others is facilitating necessary meetings for the team. Facilitating means providing guidance and support to the team in conducting effective and productive meetings, such as Iteration Planning, Daily Stand-up, Iteration Review, and Iteration Retrospective1 Facilitating does not mean taking over the meeting or making decisions for the team. Rather, it means creating a safe and respectful environment, ensuring clear and shared objectives, encouraging participation and collaboration, managing time and agenda, resolving conflicts and issues, and summarizing outcomes and action items23 By facilitating necessary meetings for the team, Scrum Masters/Team Coaches help the team to achieve their goals, improve their processes, and deliver value to the customers and the organization14 At the same time, they respect and empower the team’s autonomy, self-organization, and self-management, and do not interfere with their commitment or accountability14