What is a team's primary goal in an Iteration?
C
Explanation:
The primary goal of a team in an Iteration is to deliver working functionality that meets the
acceptance criteria and the definition of done. This functionality is demonstrated to the stakeholders
and customers in the Iteration Review and Demo event, where the team receives feedback and
validation. By delivering working functionality at the end of the Iteration, the team contributes to the
Incremental value delivery, one of the SAFe Lean-Agile Principles.
:
Iteration Goals
Iteration Planning
Iteration Review and Demo
According to SAFe, which of the following key traits of effective Scrum Masters/Team Coaches is
crucial for team members to accept coaching?
B
Explanation:
According to SAFe, empathy is one of the key traits of effective Scrum Masters/Team Coaches.
Empathy means displaying an authentic understanding and concern for a team member’s beliefs or
feelings. By being empathetic, Scrum Masters/Team Coaches can build trust and rapport with the
team, which are essential for people to accept and welcome coaching. Empathy also helps Scrum
Masters/Team Coaches to tailor their coaching style and approach to the needs and preferences of
each team member.
:
Scrum Master/Team Coach
According to SAFe which of the following key traits of effective - Studocu
What is one practice Scrum Masters/Team Coaches can use to run successful meetings?
A
Explanation:
One of the best practices Scrum Masters/Team Coaches can use to run successful meetings is to
leave meetings with clear action items. Action items are specific tasks that need to be done by a
certain person or group by a certain deadline. They help the team to follow up on the outcomes of
the meeting, track progress, and ensure accountability. Action items should be SMART: Specific,
Measurable, Achievable, Relevant, and Time-bound. Scrum Masters/Team Coaches should document
and communicate the action items to the team and stakeholders, and review them in the next
meeting.
:
Scrum Master/Team Coach
How To Run Effective Scrum Meetings - Xebia
Four agile ceremonies, demystified | Atlassian
Who are important attendees to the PI System Demo?
C
Explanation:
According to the SAFe 6 Scrum Master documentation, one of the important attendees to the PI
System Demo is the Business Owners. Business Owners are a small group of stakeholders who have
the primary business and technical responsibility for governance, compliance, and return on
investment (ROI) for a Solution developed by an Agile Release Train (ART). They are key stakeholders
on the ART who must evaluate fitness for use and actively participate in certain ART events. The PI
System Demo provides them an opportunity to see the integrated view of new features delivered by
the ART, give feedback, and influence the future direction of the solution.
:
System Demo
[Business Owners]
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?
C
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. Reference: Innovation and
Planning Iteration - Scaled Agile Framework, Exam Study Guide: SSM (6.0) - SAFe® Scrum Master
What is one potential root cause of Team Sync anti-patterns?
B
Explanation:
According to the SAFe 6 Scrum Master documentation, one of the potential root causes of Team Sync
anti-patterns is the lack of collective ownership. Collective ownership means that the team members
share responsibility for the quality and delivery of the team’s work. They collaborate, communicate,
and coordinate their efforts to achieve the team goals. They also support each other, provide
feedback, and resolve issues together. When there is a lack of collective ownership, team members
may exhibit some of the following Team Sync anti-patterns 1:
Reporting to managers (status meetings): Team members use the Team Sync as a way to report their
progress to the SM/TC or other managers, rather than to synchronize with their peers. This can
create a hierarchical and command-and-control culture, where team members are not empowered
to self-organize and self-manage.
Monologues: Team members give long and detailed updates that are not relevant or useful to other
team members. This can make the Team Sync boring, inefficient, and ineffective, as team members
lose interest and attention.
Cross-functional team standups (updates are not related to other people’s work): Team members
work on different features or components that are not aligned with the team goals or the Iteration
goals. This can result in silos, dependencies, and integration issues, as well as reduced collaboration
and coordination.
“Nothing to report” can be a good thing: Team members say they have nothing to report, either
because they have not done any work, or because they do not want to share their work with the
team. This can indicate a lack of transparency, trust, and accountability, as well as a missed
opportunity to get feedback and support from the team.
To overcome these anti-patterns, the SM/TC should coach the team on the purpose and value of the
Team Sync, and help them adopt the best practices for effective Team Syncs, such as 2:
Having a clear agenda and timebox
Focusing on the team goals and the Iteration goals
Asking the three key questions: What did I do yesterday? What will I do today? Do I have any
impediments?
Using visual aids, such as task boards or Kanban boards, to track progress and identify issues
Encouraging active participation, collaboration, and feedback
Ending with clear action items and follow-ups
:
Scrum Master/Team Coach
Team Sync
Top 7 Anti Patterns of Scrum Master - Simpliaxis
Scrum Anti-Patterns Taxonomy | Scrum.org
[11 Daily Scrum Anti-Patterns We Commonly Hear from Users In … - Geekbot
According to SAFe, which of the following metrics are reported at the Inspect and Adapt event?
A
Explanation:
According to the SAFe 6 Scrum Master documentation, one of the metrics that are reported at the
Inspect and Adapt event is the ART predictability measure. This metric shows how well the ART
delivers on its PI objectives, which are the SMART commitments made by the teams during PI
planning. The ART predictability measure is calculated by dividing the total actual business value
achieved by the total planned business value, as shown in the PI system demo. The ART predictability
measure helps the ART to assess its performance, identify gaps, and improve its forecasting accuracy
and reliability.
:
Inspect and Adapt
Program Increment
Exam Study Guide: SSM (6.0) - SAFe® Scrum Master
What is one way a Scrum Master/Team Coach can help improve ART performance?
D
Explanation:
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
:
Scrum Master/Team Coach
Team Sync
PI Planning
System Demo
Inspect and Adapt
[Communities of Practice]
What is one element on the Scrum Master/Team Coach responsibility wheel?
B
Explanation:
According to the SAFe 6 Scrum Master documentation, one of the elements on the Scrum
Master/Team Coach responsibility wheel is to facilitate PI Planning. PI Planning is a two-day event
where all the teams and stakeholders of an Agile Release Train (ART) collaborate to align on a
common vision, define and commit to the PI objectives, and identify and manage risks and
dependencies. The Scrum Master/Team Coach facilitates PI Planning by 1:
Helping the team prepare for the event, such as reviewing the business context, vision, and backlog,
and creating draft plans
Supporting the team during the event, such as facilitating breakout sessions, resolving issues, and
ensuring alignment and collaboration with other teams
Assisting the team after the event, such as finalizing the plans, updating the PI board, and conducting
a retrospective
Facilitating PI Planning is one of the ways the Scrum Master/Team Coach helps the team and the ART
achieve their goals and deliver value.
:
PI Planning
Scrum Master/Team Coach
Say Hello to SAFe 6.0! - Scaled Agile Framework
How can teams use Iteration planning to stay aligned on their work?
B
Explanation:
According to the SAFe 6 Scrum Master documentation, one of the ways teams can use Iteration
planning to stay aligned on their work is by committing to a set of goals to be delivered. Iteration
goals are a summary of the business and technical outcomes that the team intends to achieve in the
Iteration. They are based on the stories selected from the team backlog, the team’s capacity, and the
acceptance criteria. By committing to a set of goals, the team creates a shared understanding of the
purpose and scope of the Iteration, as well as the expected value and quality. The team also aligns
with the ART vision and objectives, and communicates their commitment to the stakeholders and
customers. Iteration goals help the team to stay focused, motivated, and accountable throughout the
Iteration.
:
Iteration Planning
Iteration Goals
Scrum Master/Team Coach