Which statement describes a mitigated ART PI Risk?
C
Explanation:
A mitigated ART PI Risk is one that has an agreed-upon plan for alleviation, which may involve
changing the scope, schedule, or resources of the PI. This reduces the impact or likelihood of the risk,
but does not eliminate it completely
In a 12-week PI, how often does the Innovation and Planning (IP) Iteration occur?
A
Explanation:
The Innovation and Planning (IP) Iteration is a unique, dedicated iteration that occurs every Program
Increment (PI). A PI is a timebox of 8 to 12 weeks, during which an Agile Release Train (ART) delivers
incremental value in the form of working, tested software and systems. Therefore, in a 12-week PI,
the IP Iteration occurs every quarter
What is a pattern for splitting Features into Stories?
B
Explanation:
A pattern for splitting Features into Stories is to use variations in data, which means identifying
different types of data that the feature can handle and creating a story for each type. For example, a
feature that allows users to upload files can be split into stories for different file formats, sizes, or
sources. This way, the stories are independent, testable, and valuable12
Reference:
•
Story - Scaled Agile Framework
•
User stories splitting by data variations and interfaces
What is one method for designing the end-to-end Customer experience?
A
Explanation:
Journey mapping is one method for designing the end-to-end customer experience. It is a visual
representation of the steps, emotions, and pain points that a customer goes through when
interacting with a product or service. It helps to identify the customer needs, expectations, and
goals, as well as the gaps and opportunities for improvement in the current experience. Journey
mapping also helps to align the stakeholders on the customer perspective and prioritize the features
and solutions that will deliver the most value and satisfaction123
Reference:
•
The expanding role of design in creating an end-to-end customer experience
•
End to End Customer Experience: Know and Control its 3 Elements - HEFLO BPM
•
How Design thinking Can Shape end to end Customer Experience
What is one method to establish a team's velocity?
C
Explanation:
One method to establish a team’s velocity is to compare the average story points completed
throughout the previous iterations. This gives an indication of how much work the team can
realistically deliver in a given time frame, based on their past performance. To calculate the team’s
velocity, you can use the following formula: Team velocity = total story points completed / number of
iterations. You can also use various charts and tools to visualize the team’s velocity and track its
progress over time1234
Reference:
•
Velocity in Scrum: How to Measure and Improve Performance - Atlassian
•
Discover the Concept of Team Velocity - OpenClassrooms
•
A Word on Velocity - LeadingAgile
•
Increasing Your Scrum Team’s Velocity — ClearlyAgile
What is one way Kanban boards are used in SAFe?
A
Explanation:
One way Kanban boards are used in SAFe is to manage Work-In-Progress (WIP) limits. WIP limits are
the maximum number of work items that can be in a given state or column of the Kanban board at
any time. They help to prevent bottlenecks, reduce waste, improve flow, and increase quality and
predictability. WIP limits are applied at every level of the SAFe framework, from the portfolio to the
team, to optimize the value delivery123
Reference:
•
SAFe Team Kanban - Scaled Agile Framework
•
Applying Kanban in SAFe - Scaled Agile Framework
•
What is one way Kanban boards are used in SAFE? a. To manage runway …
What is included in the Inspect and Adapt agenda?
C
Explanation:
The Inspect and Adapt (I&A) agenda in the Scaled Agile Framework (SAFe) is a significant event at the
end of each Program Increment (PI), focusing on continuous improvement and adjustment in Agile
processes. It comprises three main parts:
1. PI System Demo: This is the first part of the I&A event, intended to showcase all the features
developed by the Agile Release Train (ART) over the course of the PI. It typically includes a broader
audience and is more formal than regular system demos. Business Owners collaborate with each
Agile team to score the actual business value achieved for their Team PI Objectives.
2. Quantitative and Qualitative Measurement: This part involves the collective review of quantitative
and qualitative metrics agreed upon by the teams. This review is aimed at discussing data and trends
to measure the team's performance. Important metrics like the program predictability measure are
also analyzed, with each team's planned vs. actual business value contributing to this measure.
3. Retrospective and Problem-Solving Workshop: This structured session allows teams to reflect on
their performance, identify areas of improvement, and create action plans. It includes identifying
improvements, conducting root cause analysis using tools like the "5 Whys" or fishbone diagrams,
brainstorming solutions, prioritizing actions, and creating detailed action plans for implementation.
The I&A event promotes continuous improvement, enhanced agility, increased transparency, higher
quality outcomes, better decision-making, improved employee engagement, and alignment with
organizational goals. It's essential for both Agile Release Trains and Solution Trains to effectively
inspect and adapt their processes for optimal performance and continuous improvement.
Reference:
•
Scaled Agile Framework: Inspect and Adapt.
•
Dee Project Manager: SAFe Inspect and Adapt: Supercharge Agile Excellence.
Why is it important to establish a definition of done?
A
Explanation:
The definition of done specifies the requirements for completeness of a work product or increment
of value1. It is important to establish a clear and consistent definition of done across all Agile Teams
to ensure that the work products meet the appropriate quality standards and are ready for
integration and delivery23. Without a common definition of done, there may be confusion, rework,
delays, and technical debt3.
Reference:
•
What is the Definition of Done (DOD) in SAFe®? - Agilemania
•
Built-In Quality - Scaled Agile Framework
•
Definition of Done - Scaled Agile Framework
Which Agile Team event supports relentless improvement?
C
Explanation:
The iteration retrospective is an Agile Team event that supports relentless improvement by allowing
the team to reflect on the iteration just completed and to derive new ideas to improve the team’s
process12. This reflection helps instill the concept of relentless improvement—one of the pillars of
the SAFe House of Lean3—in the individuals and the team.
Reference:
•
Iteration Retrospective - Scaled Agile Framework
•
SAFe POPM 5 Flashcards | Quizlet
•
SAFe Lean-Agile Principles - Scaled Agile Framework
Which of the following Agile Manifesto principles aligns with conducting a System Demo?
D
Explanation:
The System Demo is an event where the Agile Release Train (ART) demonstrates the integrated and
working software to the stakeholders and customers1. The System Demo aligns with the Agile
Manifesto principle that states: "Working software is the primary measure of progress"2. This
principle emphasizes the value of delivering functional and usable software over comprehensive
documentation or adherence to a plan3. The System Demo provides feedback on the quality,
usability, and value of the software, as well as the effectiveness of the ART1.
Reference:
•
System Demo - Scaled Agile Framework
•
12 Principles Behind the Agile Manifesto | Agile Alliance
•
Manifesto for Agile Software Development