SAFe Advanced Scrum Master
Study online at https://quizlet.com/_hus57o
1. Agile Architecture: 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.
2. Agile Release Train (ART): 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.
3. Agile Team: 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.
4. Architectural Runway: existing code, hardware components, etc., that technically enable near-term busi-
ness features
5. Built-in Quality: Practices that ensure that each Solution element, at every increment, meets appropriate
quality standards throughout development.
6. Business Owners: A small group of stakeholders who have the primary business and technical responsibility
for governance, compliance, and Return on Investment for a Solution developed by an Agile Release Train (ART). They
are key stakeholders on the ART who must evaluate fitness for use and actively participate in certain ART events.
7. CapEx and OpEx: Capital Expenses and Operating Expenses describe Lean-Agile financial accounting
practices in a Value Stream budget. In some cases, CapEx may include capitalized labor associate with the development
of intangible assets - such as software, intellectual property, and patents
8. Capabilities: A higher-level solution behavior that typically spans multiple ARTs. Capabilities are sized and split
into multiple features so that they can be implemented in a single PI.
9. Community of Practice (CoP): An organized group of people with common interests in a specific
technical or business domain. They collaborate regularly to share information, improve their skills, and actively work on
advancing the general knowledge of the domain.
10. Compliance: A strategy and set of activities and artifacts that allow teams to apply Lean-Agile development
methods to build systems that have the highest possible possible quality, while simultaneously assuring they meet any
regulatory, industry, or relevant standards.
11. Continuous Delivery Pipeline: CD Pipeline (also referred to as 'pipeline') represents the workflows,
activities, and automation needed to provide a continuous release of value to the end user.
1/9
, SAFe Advanced Scrum Master
Study online at https://quizlet.com/_hus57o
12. Continuous Deployment (CD): The process that takes validated Features from Continuous Integration
and deploys them into the production environment, where they are tested and readied for release. It is the third element
in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous
Deployment, and Release on Demand.
13. Continuous Exploration (CE): The process of constantly exploring market and user needs, and
defining a Vision, Roadmap, and set of Features that address those needs. It is the first element in the four-part
Continuous Delivery Pipeline, preceding Continuous Integration (CI) Continuous Deployment (CD), and Release on
Demand.
14. Continuous Integration (CI): The process of taking features from the Program Backlog and devel-
oping, testing, integrating, and validating them in a staging environment where they are ready for deployment and
release. It is the second element in the four-part Continuous Delivery Pipeline.
15. Core Values: The Four Core Values of alignment, Built-In Quality, transparency, and program execution rep-
resent the fundamental beliefs that are key to SAFE's effectiveness. These guiding principles represent the fundamenta
beliefs that are key to SAFe's effectiveness. These guiding principles help dictate behavior and action for everyone who
participates in a SAFe portfolio.
16. Customers: The ultimate buyer of every Solution. They are an integral part of the Lean-Agile development
process and Value Stream and have specific responsibilities in SAFe.
17. Dev Team: A subset of the Agile Team. It consists of the dedicated professionals who can develop and test
a story, feature, or component. It typically includes software developers and testers, engineers and other dedicated
specialists who are required to complete a vertical slice of functionality.
18. DevOps: DevOps is a mindset, culture, and set of technical practices that stresses communication, collaboration,
and close cooperation between Agile development teams and other technology professionals who are necessary for
developing, testing, deploying, and maintaining software and systems.
19. Develop on Cadence: A strategy for managing the inherent variability in solution development by making
sure important events and activities occur on a regular, predictable schedule. It is an essential method for managing
the inherent vaibility of systems development in a flow-based system.
20. Economic Framework: A set of decision rules that aligns everyone to the financial objectives of the
Solution, and guides the economic decision-making process. It contains four primary constructs: Lean Budgeting, Epic
funding and governance, decentralized economic decision-making, and job sequencing based on the Cost of Delay
(CoD).
2/9
Study online at https://quizlet.com/_hus57o
1. Agile Architecture: 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.
2. Agile Release Train (ART): 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.
3. Agile Team: 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.
4. Architectural Runway: existing code, hardware components, etc., that technically enable near-term busi-
ness features
5. Built-in Quality: Practices that ensure that each Solution element, at every increment, meets appropriate
quality standards throughout development.
6. Business Owners: A small group of stakeholders who have the primary business and technical responsibility
for governance, compliance, and Return on Investment for a Solution developed by an Agile Release Train (ART). They
are key stakeholders on the ART who must evaluate fitness for use and actively participate in certain ART events.
7. CapEx and OpEx: Capital Expenses and Operating Expenses describe Lean-Agile financial accounting
practices in a Value Stream budget. In some cases, CapEx may include capitalized labor associate with the development
of intangible assets - such as software, intellectual property, and patents
8. Capabilities: A higher-level solution behavior that typically spans multiple ARTs. Capabilities are sized and split
into multiple features so that they can be implemented in a single PI.
9. Community of Practice (CoP): An organized group of people with common interests in a specific
technical or business domain. They collaborate regularly to share information, improve their skills, and actively work on
advancing the general knowledge of the domain.
10. Compliance: A strategy and set of activities and artifacts that allow teams to apply Lean-Agile development
methods to build systems that have the highest possible possible quality, while simultaneously assuring they meet any
regulatory, industry, or relevant standards.
11. Continuous Delivery Pipeline: CD Pipeline (also referred to as 'pipeline') represents the workflows,
activities, and automation needed to provide a continuous release of value to the end user.
1/9
, SAFe Advanced Scrum Master
Study online at https://quizlet.com/_hus57o
12. Continuous Deployment (CD): The process that takes validated Features from Continuous Integration
and deploys them into the production environment, where they are tested and readied for release. It is the third element
in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous
Deployment, and Release on Demand.
13. Continuous Exploration (CE): The process of constantly exploring market and user needs, and
defining a Vision, Roadmap, and set of Features that address those needs. It is the first element in the four-part
Continuous Delivery Pipeline, preceding Continuous Integration (CI) Continuous Deployment (CD), and Release on
Demand.
14. Continuous Integration (CI): The process of taking features from the Program Backlog and devel-
oping, testing, integrating, and validating them in a staging environment where they are ready for deployment and
release. It is the second element in the four-part Continuous Delivery Pipeline.
15. Core Values: The Four Core Values of alignment, Built-In Quality, transparency, and program execution rep-
resent the fundamental beliefs that are key to SAFE's effectiveness. These guiding principles represent the fundamenta
beliefs that are key to SAFe's effectiveness. These guiding principles help dictate behavior and action for everyone who
participates in a SAFe portfolio.
16. Customers: The ultimate buyer of every Solution. They are an integral part of the Lean-Agile development
process and Value Stream and have specific responsibilities in SAFe.
17. Dev Team: A subset of the Agile Team. It consists of the dedicated professionals who can develop and test
a story, feature, or component. It typically includes software developers and testers, engineers and other dedicated
specialists who are required to complete a vertical slice of functionality.
18. DevOps: DevOps is a mindset, culture, and set of technical practices that stresses communication, collaboration,
and close cooperation between Agile development teams and other technology professionals who are necessary for
developing, testing, deploying, and maintaining software and systems.
19. Develop on Cadence: A strategy for managing the inherent variability in solution development by making
sure important events and activities occur on a regular, predictable schedule. It is an essential method for managing
the inherent vaibility of systems development in a flow-based system.
20. Economic Framework: A set of decision rules that aligns everyone to the financial objectives of the
Solution, and guides the economic decision-making process. It contains four primary constructs: Lean Budgeting, Epic
funding and governance, decentralized economic decision-making, and job sequencing based on the Cost of Delay
(CoD).
2/9
