SaFe Agile Advanced Scrum Master Exam Questions and
Answers Latest () (Verified Answers)
Portfolio Backlog - ANSWER-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 - ANSWER-A method used to visualize and manage the analysis,
prioritization and flow of portfolio epics from ideation to implementation and
completion.
Portfolio Level - ANSWER-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 - ANSWER-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 - ANSWER-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 - ANSWER-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) - ANSWER-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 - ANSWER-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) - ANSWER-A timebox in which an Agile Release Train (ART)
delivers incremental value in the form of working, tested software and systems.
,They are typically eight to twelve weeks long, and the most common pattern for
one is four development iterations, followed by one Innovation and Planning (IP)
iteration.
Program Increment (PI) Planning - ANSWER-A cadence-based, face-to-face event
that serves as the heartbeat of the Agile Release Train (ART), aligning all the
teams on the ART to a common mission and vision.
Program Kanban - ANSWER-The Program and Solution Kanban systems are
methods used to visualize and manage the flow of value from ideation to analysis,
implementation, and release. They support the flow of Features and Capabilities
through the full Continuous Delivery Pipeline of Continuous Exploration, Continuous
Integration, Continuous Deployment, and Release on Demand.
Program Level - ANSWER-Contains the roles and activities needed to continuously
deliver solutions via an Agile Release Train (ART).
Refactoring - ANSWER-The activity of improving the internal structure or
operation of a code or component without changing its external behavior.
Agile Architecture - ANSWER-Agile architecture is a set of values and practices
that support the active evolution of the design and
architecture of a system, concurrent with the implementation of new business
functionality. With this
, approach, the architecture of a system, even a large one, evolves over time while
simultaneously
supporting the needs of current users. This avoids Big Up-Front Design (BUFD)
and the starting and
stopping of stage-gated methods.
Agile Release Train (ART) - ANSWER-A long-lived and cross-functional team-of-
Agile-teams, which along with other stakeholders, develops and delivers solutions
incrementally, using a series of fixed-length Iterations within a Program
Increment (PI) timebox. Aligns teams to a common business and technology
mission.
Agile Team - ANSWER-A cross-functional group of five to ten people who have the
ability and authority to define, build, and test some element of Solution value—all
in a short Iteration timebox. Specifically, it incorporates the DevTeam, Scrum
Master, and Product Owner roles.
Architectural Runway - ANSWER-existing code, hardware components, etc., that
technically enable near-term business features
Built-in Quality - ANSWER-Practices that ensure that each Solution element, at
every increment, meets appropriate quality standards throughout development.
Answers Latest () (Verified Answers)
Portfolio Backlog - ANSWER-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 - ANSWER-A method used to visualize and manage the analysis,
prioritization and flow of portfolio epics from ideation to implementation and
completion.
Portfolio Level - ANSWER-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 - ANSWER-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 - ANSWER-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 - ANSWER-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) - ANSWER-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 - ANSWER-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) - ANSWER-A timebox in which an Agile Release Train (ART)
delivers incremental value in the form of working, tested software and systems.
,They are typically eight to twelve weeks long, and the most common pattern for
one is four development iterations, followed by one Innovation and Planning (IP)
iteration.
Program Increment (PI) Planning - ANSWER-A cadence-based, face-to-face event
that serves as the heartbeat of the Agile Release Train (ART), aligning all the
teams on the ART to a common mission and vision.
Program Kanban - ANSWER-The Program and Solution Kanban systems are
methods used to visualize and manage the flow of value from ideation to analysis,
implementation, and release. They support the flow of Features and Capabilities
through the full Continuous Delivery Pipeline of Continuous Exploration, Continuous
Integration, Continuous Deployment, and Release on Demand.
Program Level - ANSWER-Contains the roles and activities needed to continuously
deliver solutions via an Agile Release Train (ART).
Refactoring - ANSWER-The activity of improving the internal structure or
operation of a code or component without changing its external behavior.
Agile Architecture - ANSWER-Agile architecture is a set of values and practices
that support the active evolution of the design and
architecture of a system, concurrent with the implementation of new business
functionality. With this
, approach, the architecture of a system, even a large one, evolves over time while
simultaneously
supporting the needs of current users. This avoids Big Up-Front Design (BUFD)
and the starting and
stopping of stage-gated methods.
Agile Release Train (ART) - ANSWER-A long-lived and cross-functional team-of-
Agile-teams, which along with other stakeholders, develops and delivers solutions
incrementally, using a series of fixed-length Iterations within a Program
Increment (PI) timebox. Aligns teams to a common business and technology
mission.
Agile Team - ANSWER-A cross-functional group of five to ten people who have the
ability and authority to define, build, and test some element of Solution value—all
in a short Iteration timebox. Specifically, it incorporates the DevTeam, Scrum
Master, and Product Owner roles.
Architectural Runway - ANSWER-existing code, hardware components, etc., that
technically enable near-term business features
Built-in Quality - ANSWER-Practices that ensure that each Solution element, at
every increment, meets appropriate quality standards throughout development.
