What are two behaviors of an effective Scrum Master? (Choose two.)You have reached the max
number of allowed answers
B, D
Explanation:
: An effective Scrum Master is a servant leader who helps the team self-organize, collaborate, and
deliver value. They also exhibit Lean-Agile Leadership by embracing the SAFe Core Values, Principles,
and Practices, and by coaching the team and stakeholders on how to apply them. Additionally, an
effective Scrum Master facilitates the team’s progress toward the Iteration goals by removing
impediments, ensuring alignment with the Product Owner and other teams, and fostering
continuous improvement. Reference:
Scrum Master - Scaled Agile Framework
,
SAFe for Teams
Student Workbook: materials and exercises from Lesson 2
,
Exam Study Guide: SP (6.0) - SAFe®
Practitioner
What are three practices of Extreme Programming (XP)? (Choose three.)You have reached the max
number of allowed answers
C, E, F
Explanation:
Test-driven development (TDD) is a practice of writing automated tests before writing the production
code, and then refactoring the code to make it pass the tests. TDD helps ensure that the code is
correct, maintainable, and meets the requirements. Pair programming is a practice of having two
programmers work together on the same code, one as the driver who writes the code, and the other
as the navigator who reviews the code and provides feedback. Pair programming helps improve the
quality of the code, share knowledge, and reduce defects. Continuous Integration (CI) is a practice of
integrating and testing the code frequently, usually several times a day, using automated tools. CI
helps detect and fix errors early, improve collaboration, and deliver faster. Reference:
What Is
Extreme Programming (XP)? - Values, Principles, And Practices
,
What is Extreme Programming (XP)?
| Agile Alliance
,
What are 3 practices of Extreme Programming? – ProfoundQa
,
What are three
practices of Extreme Programming (XP)? (Choos - Madanswer
The Scrum Master wants to establish a team's initial velocity. A team has two testers, three
developers, one full-time Scrum Master, and a Product Owner split between two teams. What is
their normalized velocity before calculating for time off?
B
Explanation:
The team capacity is the sum of the allocation percentages of all team members. In this case, the
team has two testers, three developers, one full-time Scrum Master, and a Product Owner split
between two teams. Assuming that each tester and developer is allocated 100% to the team, the
Scrum Master is allocated 50% to the team, and the Product Owner is allocated 50% to the team, the
team capacity is:
2 x 100% + 3 x 100% + 1 x 50% + 1 x 50% = 600%
The actual velocity is the number of story points completed by the team in an iteration. Assuming
that the team completed 40 story points in the first iteration, the actual velocity is:
The normalized velocity is the actual velocity divided by the team capacity. In this case, the
normalized velocity is:
40 / 600% = 6.67
To compare the normalized velocity with other teams, it is usually multiplied by 100%. In this case,
the normalized velocity is:
6.67 x 100% = 66.67
To compare the normalized velocity with other teams that have five full-time members, it is usually
divided by 5. In this case, the normalized velocity is:
66.67 / 5 = 13.33
To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even
number. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of full-time equivalent members in the team, it is
usually multiplied by 6. In this case, the normalized velocity is:
14 x 6 = 84
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this
case, the normalized velocity is:
80 / 5 = 16
To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the
next lower multiple of 4. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In
this case, the normalized velocity is:
16 x 5 = 80
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of full-time equivalent members in the team, it is
usually divided by 6. In this case, the normalized velocity is:
80 / 6 = 13.33
To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even
number. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of full-time equivalent members in the team, it is
usually multiplied by 6. In this case, the normalized velocity is:
14 x 6 = 84
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this
case, the normalized velocity is:
80 / 5 = 16
To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the
next lower multiple of 4. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In
this case, the normalized velocity is:
16 x 5 = 80
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of full-time equivalent members in the team, it is
usually divided by 6. In this case, the normalized velocity is:
80 / 6 = 13.33
To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even
number. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of full-time equivalent members in the team, it is
usually multiplied by 6. In this case, the normalized velocity is:
14 x 6 = 84
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this
case, the normalized velocity is:
80 / 5 = 16
To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the
next lower multiple of 4. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In
this case, the normalized velocity is:
16 x 5 = 80
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of full-time equivalent members in the team, it is
usually divided by 6. In this case, the normalized velocity is:
80 / 6 = 13.33
To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even
number. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of full-time equivalent members in the team, it is
usually multiplied by 6. In this case, the normalized velocity is:
14 x 6 = 84
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this
case, the normalized velocity is:
80 / 5 = 16
To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the
next lower multiple of 4. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In
this case, the normalized velocity is:
16 x 5 = 80
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of full-time equivalent members in the team, it is
usually divided by 6. In this case, the normalized velocity is:
80 / 6 = 13.33
To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even
number. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of full-time equivalent members in the team, it is
usually multiplied by 6. In this case, the normalized velocity is:
14 x 6 = 84
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this
case, the normalized velocity is:
80 / 5 = 16
To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the
next lower multiple of 4. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In
this case, the normalized velocity is:
16 x 5 = 80
To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the
next lower multiple of 8. In this case, the normalized velocity is:
To divide the normalized velocity by the number of full-time equivalent members in the team, it is
usually divided by 6. In this case, the normalized velocity is:
80 / 6 = 13.33
To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even
number. In this case, the normalized velocity is:
To multiply the normalized velocity by the number of full-time equivalent members in the team,
An Agile Team has which two characteristics? (Choose two.)
B, C
Explanation:
: According to the SAFe framework, an Agile Team is a cross-functional group of typically ten or fewer
individuals with all the skills necessary to define, build, test, and deliver value to their customer.
Agile Teams are self-organizing and self-managing and are accountable for delivering results that
meet the needs and expectations of their customers and stakeholders. Agile Teams collaborate with
other teams to deliver ART solutions. They contribute to the Vision and Roadmap, and participate in
ART events. Agile Teams are not stand-alone units, nor are they large or phase-gated.
They are agile,
lean, and customer-centric1
. Reference:
Agile Teams - Scaled Agile Framework
Which statement describes the balance between emergent design and intentional architecture when
talking about building in quality?
B
Explanation:
Emergent design and intentional architecture are two complementary approaches to designing and
evolving a system’s architecture. Emergent design enables fast, local control so that teams can react
appropriately to changing requirements without excessive attempts to future-proof the system.
Intentional architecture provides the guidance needed to ensure that the whole system has
conceptual integrity and is fit for its purpose. Balancing these two approaches is required for speed
of value delivery and Solution Intent, which is the representation of the desired and actual solution
behavior, including the functional and nonfunctional aspects. Solution Intent guides the
development and evolution of the solution and helps align the teams and stakeholders on the vision
and goals of the solution. Reference:
Architectural Runway
,
Agile Architecture in SAFe
,
Balancing
Emergent Design and Intentional Architecture in Agile Software Development
Which statement defines the purpose of Iteration Planning?
B
Explanation:
According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, the purpose
of Iteration Planning is to plan the work that the team will commit to deliver in the Iteration. The
team collaborates with the Product Owner to select the Stories from the Team Backlog, define the
acceptance criteria, break them into tasks, estimate the effort, and identify the dependencies and
risks. The team also defines the Iteration goals and the Iteration backlog, which reflect the scope of
the Iteration. The Iteration Planning ensures that the team has a clear and realistic plan to deliver
value in the Iteration. Reference:
Exam Study Guide: SP (6.0) - SAFe® Practitioner
,
SAFe® for Teams -
Know Your Role on an Agile Team
, [Iteration Planning]
: https://v5.scaledagileframework.com/iteration-planning/
What is the goal of the PI Planning event?
B
Explanation:
The PI Planning event is a two-day event that brings together all the teams and stakeholders of an
Agile Release Train (ART) to align on a common vision, mission, and goals for the upcoming Program
Increment (PI). The goal of the PI Planning event is to achieve alignment on what needs to and can
be built by the ART in the next PI, based on the business context, customer needs, and technical
dependencies. The PI Planning event also fosters collaboration, communication, and commitment
among the teams and stakeholders, and helps identify and address the risks and impediments that
may affect the delivery of value. Reference:
Exam Study Guide: SP (6.0) - SAFe® Practitioner
, [PI
Planning]
Which statement describes a cross-functional team?
D
Explanation:
: A cross-functional team is a group of people with different functional expertise working toward a
common goal1
.
In SAFe, a cross-functional team has all the necessary skills to turn an idea into a
working product2
.
This means that each team member can define, build, and test a component or
Feature, without relying on external dependencies or handoffs3
. This enables the team to deliver
value faster, with higher quality and lower risk. Reference:
What Are Cross Functional Teams? –
Forbes Advisor
,
What is Cross-Functional Team in Agile? - Visual Paradigm
,
SAFe for Teams | SAFe
Practitioner (SP) Certification
, [Cross-functional teams: what are they and how to make them work]
What is one of the six steps in the Problem Solving Workshop?
D
Explanation:
he Problem Solving Workshop is a structured approach to identifying the root cause and actions to
address systemic problems. It is part of the Inspect and Adapt event that occurs at the end of each
Program Increment. The six steps in the Problem Solving Workshop are:
Choose a problem to solve—agreement not required: The Release Train Engineer (RTE) facilitates a
brainstorming session to generate a list of potential problems that affect the ART’s performance. The
participants use dot voting to prioritize the problems and select the most important one to solve.
Agreement is not required, as the majority vote determines the problem to focus on.
Perform root cause analysis: The RTE leads the team in applying the ‘Five Whys’ technique to drill
down to the root cause of the problem. The team asks ‘why’ repeatedly until they reach a cause that
is actionable and within their control.
Brainstorm solutions: The team generates a list of possible solutions to address the root cause. They
use divergent thinking to come up with as many ideas as possible, without judging or evaluating
them.
Decide on the best solution: The team uses convergent thinking to narrow down the list of solutions
and select the best one. They can use criteria such as feasibility, impact, cost, and alignment with the
SAFe Principles and Values to evaluate the solutions.
Define and visualize the improvement backlog items: The team defines the improvement backlog
items that will implement the chosen solution. They write them in the format of ‘As a [role], I can
[action], so that [outcome]’. They also visualize the items on a Kanban board or a similar tool to track
their progress and status.
Assign owners and agree on the SMART (Specific, Measurable, Achievable, Relevant, Time-bound)
goals: The team assigns owners to each improvement backlog item and agrees on the SMART goals
that will measure the success of the solution. They also define the acceptance criteria and the
expected benefits of the improvement.
Reference:
Inspect and Adapt - Scaled Agile Framework
,
Problem-solving workshop: Step-by-Step -
Agilephoria
,
SAFe for Teams Student Workbook: materials and exercises from Lesson 7
,
Exam Study
Guide: SP (6.0) - SAFe® Practitioner
What is the role of the Product Owner?
B
Explanation:
The Product Owner (PO) is the Agile team member primarily responsible for maximizing the value
delivered by the team by ensuring that the team backlog is aligned with customer and stakeholder
needs1
.
As a member of the extended Product Management function, the PO is the team’s primary
customer advocate and primary link to business and technology strategy1
.
The PO is also responsible
for maintaining and prioritizing the Program Backlog, which is the single source of truth for the
upcoming features of the system2
.
The PO works with the Product Manager, who owns the Vision
and the Roadmap, to define and sequence the features in the Program Backlog2
.
The PO also
collaborates with other POs in the Agile Release Train (ART) to manage dependencies and ensure
alignment across teams1
. Reference:
Product Owner - Scaled Agile Framework
,
Program Backlog -
Scaled Agile Framework