How does a team demonstrate progress?
C
Explanation:
According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, one of the
core values of SAFe is alignment, which means that everyone involved in the solution development
has a common understanding of the vision, strategy, and goals. To achieve alignment, teams need to
demonstrate progress by showing the actual working product to the stakeholders and getting
feedback. This is done through the sync events such as the Team Demo and the System Demo, where
teams showcase the features and stories they have completed in the iteration or the PI. By showing
the actual working product, teams can validate their assumptions, measure the value delivered, and
identify improvement opportunities. Reference:
Exam Study Guide: SP (6.0) - SAFe®
Practitioner
,
SAFe® for Teams - Know Your Role on an Agile Team
,
SAFe for Teams | SAFe Practitioner
(SP) Certification
What is one responsibility of the Scrum Master?
C
Explanation:
The Scrum Master is a servant leader and coach for the Agile team. One of their main responsibilities
is to remove impediments that hinder the team’s progress and performance. Impediments can be
anything that blocks the team from delivering value, such as technical issues, dependencies,
conflicts, or lack of resources. The Scrum Master helps the team identify and resolve impediments as
quickly as possible, and escalates them to the appropriate level if needed. By removing
impediments, the Scrum Master helps the team stay focused, productive, and
motivated. Reference:
Exam Study Guide: SP (6.0) - SAFe® Practitioner
, [Scrum Master]
Which two statements best describe elements of Continuous Delivery? (Choose two.)
B D
Explanation:
Continuous Delivery is a set of practices that enable teams to release value to customers in short
cycles, with high quality and low risk. One of the key practices of Continuous Delivery is to automate
testing of Features and nonfunctional requirements, such as performance, security, and usability.
This ensures that the code is always in a releasable state and reduces the feedback time and cost of
defects. Another key practice of Continuous Delivery is to maintain a staging environment that
emulates production, where the final integration, validation, and acceptance testing can take place
before deployment. This reduces the risk of failures and errors in production and enables faster and
more reliable releases. Reference:
SAFe® for Teams - Know Your Role on an Agile Team
,
SAFe for
Teams 6.0 (SP) Certification Training
,
SAFe for Teams | SAFe Practitioner (SP) Certification
What type of information can be easily seen in a cumulative flow diagram?
C
Explanation:
cumulative flow diagram (CFD) is a visual tool that shows the amount of work in each stage of a
process over time. It helps teams identify bottlenecks, work in progress (WIP), and the overall
progress of a project or program increment (PI). By looking at the width of the bands in a CFD, teams
can easily see how much work is in each workflow state at any given time. This allows them to
monitor and optimize their flow of value delivery. Reference:
Cumulative Flow Diagram SAFe:
Complete Guide
,
Measure and Grow - Scaled Agile Framework
Which process guides the final approval for a release in SAFe?
A
Explanation:
: Release Governance is the process that guides the final approval for a release in SAFe. It involves a
set of roles and responsibilities that ensure the quality, compliance, and fitness for purpose of the
solution before it is released to customers. Release Governance also coordinates the timing and
frequency of releases based on market demand and business needs. Release Governance is part of
the Release on Demand aspect of the Continuous Delivery Pipeline, which is the fourth and last
element in the four-part pipeline of Continuous Exploration, Continuous Integration, Continuous
Deployment, and Release on Demand. Reference:
Release on Demand - Scaled Agile
Framework
,
SAFe for teams 93% Flashcards | Quizlet
,
Release on Demand - SAFe 4.5 Reference
Guide: Scaled Agile Framework …
The Release Train Engineer is a servant leader who displays which two actions or behaviors? (Choose
two.)
C, E
Explanation:
A servant leader is someone who puts the needs of others first and helps them develop and perform
to their highest potential. The RTE is a servant leader who listens and supports teams in problem
identification and decision-making, by facilitating ART events and processes, communicating with
stakeholders, escalating impediments, and helping manage risk. The RTE also leads by example, by
demonstrating the Lean-Agile mindset and values, fostering a culture of collaboration and
innovation, and driving relentless improvement.
Reference:
Release Train Engineer - Scaled Agile Framework
Product Management is responsible for "what gets built" as defined by the Vision, Roadmap, and
what else?
A
Explanation:
n: Product Management is responsible for defining desirable, viable, feasible, and sustainable
solutions that meet customer needs and supporting development across the product life cycle. They
align the product strategy, vision, and roadmap to the portfolio’s strategic themes and lean budgets.
They also create, maintain, and adjust the program backlog, which contains the features and
enablers that the Agile Release Train (ART) will implement. They work with customers, teams, and
product owners to understand and communicate their needs and participate in solution
validation.
They also collaborate with system architects and the release train engineer to guide the
ART toward successful delivery12
. Reference:
Product Management - Scaled Agile Framework
,
Agile
Release Train - Scaled Agile Framework
Which statement is true about the purpose of a work in process constraint?
A
Explanation:
According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, a work in
process (WIP) constraint is a limit on the amount of work that can be done at any stage of the value
stream. The purpose of a WIP constraint is to reduce the batch size, manage the queue length, and
improve the flow of value. By limiting the WIP, teams can focus on completing the most important
work items, collaborate more effectively, and deliver value faster and more frequently. A WIP
constraint also helps teams identify and resolve bottlenecks, reduce waste, and increase
quality. Reference:
Exam Study Guide: SP (6.0) - SAFe® Practitioner
,
SAFe® for Teams - Know Your
Role on an Agile Team
, [Visualize and limit WIP, reduce batch sizes, and manage queue lengths]
What is the recommended length of an Iteration?
A
Explanation:
An Iteration is a fixed timebox during which an Agile team delivers a potentially releasable
increment of value. The recommended length of an Iteration is two weeks, as this allows for fast
feedback, adaptation, and learning cycles. Longer Iterations may increase the risk of
overcommitment, scope creep, and reduced quality. Shorter Iterations may increase the overhead of
planning and coordination, and reduce the amount of value delivered per Iteration. Reference:
Exam
Study Guide: SP (6.0) - SAFe® Practitioner
, [Iteration]
What does a program board help teams identify?
B
Explanation:
: A program board is a visual summary of the features or goals, when they need to be reached, and
any cross-team dependencies impacting their delivery. The program board helps teams within the
Agile Release Train (ART) to coordinate their work and communicate their plan to the entire
organization. One of the main purposes of the program board is to help teams identify and manage
dependencies between teams, which can affect the delivery of value and increase the risk of delays
or failures. By visualizing and tracking dependencies on the program board, teams can avoid or
resolve them during the Program Increment (PI) planning event or throughout the PI
execution. Reference:
SAFe Program Board 101: Everything You Need To Know
,
SAFe Program Board:
Good Practices for SAFe PI Planning
,
Tips for using a SAFe program board
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