SAFE 5 ADVANCED SCRUM MASTER FINAL EXAM
ACTUAL QUESTIONS AND ANSWERS SURE A+
✔✔Lean-Agile Leaders - ✔✔Lifelong learners who are responsible for the successful
adoption of SAFe and the results it delivers. They empower and help teams build better
systems by learning, exhibiting, teaching and coaching SAFe's Lean-Agile principles
and practices.
✔✔Lean-Agile Mindset - ✔✔The combination of beliefs, assumptions, and actions of
SAFe leaders and practitioners who embrace the concepts of the Agile Manifesto and
Lean thinking. It's the personal, intellectual and leadership foundation for adopting and
applying SAFe's principles and practices.
✔✔Metrics - ✔✔Agreed-upon measures used to evaluate how well the organization is
progressing toward the portfolio, large solution, program, and team's business and
technical objectives.
✔✔Milestones - ✔✔Used to track progress toward a specific goal or event. There are
three types of SAFe milestones: Program Increment, fixed-date, and learning
milestones.
✔✔Model Based Systems Engineering (MBSE) - ✔✔The practice of developing a set of
related system models that help define, design and document a system under
development. These models provide an efficient way to explore, update, and
communicate system aspects to stakeholders, while significantly reducing or eliminating
dependence on traditional documents.
✔✔Nonfunctional Requirements (NFRs) - ✔✔Define system attributes such as security,
reliability, performance, maintainability, scalability, and usability. They serve as
constraints or restrictions on the design of the system across the different backlogs.
, ✔✔Portfolio Backlog - ✔✔The portfolio backlog is the highest-level backlog in SAFe. It
provides a holding mechanism for the upcoming business and enabler epics required to
create a portfolio solution set, a set that provides the competitive differentiation and
operational efficiencies necessary to address the strategic themes and facilitate
business success.
✔✔Portfolio Kanban - ✔✔A method used to visualize and manage the analysis,
prioritization and flow of portfolio epics from ideation to implementation and completion.
✔✔Portfolio Level - ✔✔The SAFe Level that contains the guidance, practices and roles
needed to initiate and govern a set of development value streams. This is where
strategy and investment funding are defined for value streams and their Solutions. This
level also provides Agile program guidance and Lean governance for the people and
resources needed to deliver solutions.
✔✔Portfolio SAFe configuration - ✔✔Helps align portfolio execution to the enterprise
strategy, by organizing Agile development around the flow of value, through one or
more value streams. It provides business agility through principles and practices for
portfolio strategy and investment funding, Agile program guidance, and Lean
governance.
✔✔Pre- and Post-PI Planning - ✔✔Planning events that are used to prepare for, and
follow-up after, PI Planning for Agile Release Trains (ARTs) and Suppliers in a Solution
Train.
✔✔Product Management - ✔✔The role that has content authority for the Program
Backlog. They are responsible for identifying customer needs, prioritizing features and
developing the program Vision and Roadmap.
✔✔Product Owner (PO) - ✔✔Responsible for defining Stories and prioritizing the Team
Backlog to streamline the execution of program priorities, while maintaining conceptual
and technical integrity of the Features or components for the team. The PO has a
significant role in quality control and is the only team member empowered to accept
stories as done. For most enterprises converting to Agile, this is a new and critical role,
typically translating into a full-time job, requiring the PO to support each Agile team (or,
at most, two teams).
✔✔Program Backlog - ✔✔The final state in the Program Kanban, which is also the last
state of Continuous Exploration. It's the holding area for a prioritized list of Features that
have been analyzed and are intended to address user needs and deliver business
benefits for a single Agile Release Train (ART). It also contains the Enabler features
necessary to build the Architectural Runway.
✔✔Program Increment (PI) - ✔✔A timebox in which an Agile Release Train (ART)
delivers incremental value in the form of working, tested software and systems. They
ACTUAL QUESTIONS AND ANSWERS SURE A+
✔✔Lean-Agile Leaders - ✔✔Lifelong learners who are responsible for the successful
adoption of SAFe and the results it delivers. They empower and help teams build better
systems by learning, exhibiting, teaching and coaching SAFe's Lean-Agile principles
and practices.
✔✔Lean-Agile Mindset - ✔✔The combination of beliefs, assumptions, and actions of
SAFe leaders and practitioners who embrace the concepts of the Agile Manifesto and
Lean thinking. It's the personal, intellectual and leadership foundation for adopting and
applying SAFe's principles and practices.
✔✔Metrics - ✔✔Agreed-upon measures used to evaluate how well the organization is
progressing toward the portfolio, large solution, program, and team's business and
technical objectives.
✔✔Milestones - ✔✔Used to track progress toward a specific goal or event. There are
three types of SAFe milestones: Program Increment, fixed-date, and learning
milestones.
✔✔Model Based Systems Engineering (MBSE) - ✔✔The practice of developing a set of
related system models that help define, design and document a system under
development. These models provide an efficient way to explore, update, and
communicate system aspects to stakeholders, while significantly reducing or eliminating
dependence on traditional documents.
✔✔Nonfunctional Requirements (NFRs) - ✔✔Define system attributes such as security,
reliability, performance, maintainability, scalability, and usability. They serve as
constraints or restrictions on the design of the system across the different backlogs.
, ✔✔Portfolio Backlog - ✔✔The portfolio backlog is the highest-level backlog in SAFe. It
provides a holding mechanism for the upcoming business and enabler epics required to
create a portfolio solution set, a set that provides the competitive differentiation and
operational efficiencies necessary to address the strategic themes and facilitate
business success.
✔✔Portfolio Kanban - ✔✔A method used to visualize and manage the analysis,
prioritization and flow of portfolio epics from ideation to implementation and completion.
✔✔Portfolio Level - ✔✔The SAFe Level that contains the guidance, practices and roles
needed to initiate and govern a set of development value streams. This is where
strategy and investment funding are defined for value streams and their Solutions. This
level also provides Agile program guidance and Lean governance for the people and
resources needed to deliver solutions.
✔✔Portfolio SAFe configuration - ✔✔Helps align portfolio execution to the enterprise
strategy, by organizing Agile development around the flow of value, through one or
more value streams. It provides business agility through principles and practices for
portfolio strategy and investment funding, Agile program guidance, and Lean
governance.
✔✔Pre- and Post-PI Planning - ✔✔Planning events that are used to prepare for, and
follow-up after, PI Planning for Agile Release Trains (ARTs) and Suppliers in a Solution
Train.
✔✔Product Management - ✔✔The role that has content authority for the Program
Backlog. They are responsible for identifying customer needs, prioritizing features and
developing the program Vision and Roadmap.
✔✔Product Owner (PO) - ✔✔Responsible for defining Stories and prioritizing the Team
Backlog to streamline the execution of program priorities, while maintaining conceptual
and technical integrity of the Features or components for the team. The PO has a
significant role in quality control and is the only team member empowered to accept
stories as done. For most enterprises converting to Agile, this is a new and critical role,
typically translating into a full-time job, requiring the PO to support each Agile team (or,
at most, two teams).
✔✔Program Backlog - ✔✔The final state in the Program Kanban, which is also the last
state of Continuous Exploration. It's the holding area for a prioritized list of Features that
have been analyzed and are intended to address user needs and deliver business
benefits for a single Agile Release Train (ART). It also contains the Enabler features
necessary to build the Architectural Runway.
✔✔Program Increment (PI) - ✔✔A timebox in which an Agile Release Train (ART)
delivers incremental value in the form of working, tested software and systems. They
