Scaled Agile Framework (SAFe) Vocabulary
Study online at https://quizlet.com/_huk3f7
1. Agile Architecture: A set of values and practices that support the active evolution of the design and
architecture of a system while implementing new system capabilities.
2. Agile Release Train (ART): A long-lived team of Agile teams, which, along with other stakeholders,
incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream.
3. Agile Team: A cross-functional group of 5 to 11 people who have the responsibility to define, build, test, and
where applicable deploy, some element of Solution value—all in a short Iteration timebox. Specifically, this group
incorporates the Dev Team, Scrum Master, and Product Owner roles.
4. Architectural Runway: Consists of the existing code, components, and technical infrastructure needed to
implement near-term features without excessive redesign and delay.
5. Built-in Quality: Practices that ensure 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 (ROI) 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. Business Solutions and Lean Systems Engineering: A competency which describes how
to apply Lean-Agile principles and practices to the specification, development, deployment, and evolution of large,
complex software applications and cyber-physical systems.
8. Capabilities: A higher-level solution behavior that typically spans multiple ARTs. Each is sized and split into
multiple features to facilitate their implementation in a single PI.
9. Communities of Practice (CoPs): Organized groups of people who have a common interest 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 a set of activities and artifacts that allow teams to apply Lean-Agile development
methods to build systems that have the highest possible quality, while simultaneously assuring they meet any regulatory,
industry, or other relevant standards.
11. Continuous Delivery Pipeline (or 'the 'pipeline'): The workflows, activities, and automation
needed to shepherd a new piece of functionality all the way from ideation to an on-demand release of value to the end
user.
12. Continuous Deployment (CD): The process that fosters innovation and builds alignment on what
should be built by continually exploring market and Customer needs, and defining a Vision, Roadmap, and set of
Features for a Solution that addresses those needs.
, Scaled Agile Framework (SAFe) Vocabulary
Study online at https://quizlet.com/_huk3f7
13. Continuous Exploration (CE): The process that fosters innovation and builds alignment on what
should be built by continually exploring market and Customer needs, and defining a Vision, Roadmap, and set of
Features for a Solution that addresses those needs.
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.
15. Core Values: These represent the fundamental beliefs that are key to SAFe's effectiveness. These guiding
principles help dictate behavior and action for everyone who participates in a SAFe portfolio.
Those principles are:
1. Alignment
2. Built-in quality
3. Transparency
4. Program execution
16. Customers: The ultimate buyer of every Solution. They are an integral part of the Lean-Agile development
process and the Value Stream and have specific responsibilities in SAFe.
17. Dev Team: A subset of the Agile Team. It consists of dedicated professionals who can develop, test, and deploy
a Story, Feature, or component. This subset typically includes software developers and testers, engineers, and other
dedicated specialists required to complete a vertical slice of functionality.
18. DevOps: A mindset, a culture, and a set of technical practices. It provides communication, integration, au-
tomation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a
Solution.
Uses the CALMR approach:
* Culture of Shared Responsibility
* Automation of Continuous Delivery Pipeline
* Lean flow accelerates delivery
* Measurement of everything
* Recovery enables low risk releases
19. DevOps and Release on Demand: A competency which describes how implementing a mindset,
a culture, and a set of technical practices as well as a continuous delivery pipeline provides the enterprise with the
capability to release value, in whole or in part, at any time necessary to meet market and customer demand.
Study online at https://quizlet.com/_huk3f7
1. Agile Architecture: A set of values and practices that support the active evolution of the design and
architecture of a system while implementing new system capabilities.
2. Agile Release Train (ART): A long-lived team of Agile teams, which, along with other stakeholders,
incrementally develops, delivers, and where applicable operates, one or more solutions in a value stream.
3. Agile Team: A cross-functional group of 5 to 11 people who have the responsibility to define, build, test, and
where applicable deploy, some element of Solution value—all in a short Iteration timebox. Specifically, this group
incorporates the Dev Team, Scrum Master, and Product Owner roles.
4. Architectural Runway: Consists of the existing code, components, and technical infrastructure needed to
implement near-term features without excessive redesign and delay.
5. Built-in Quality: Practices that ensure 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 (ROI) 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. Business Solutions and Lean Systems Engineering: A competency which describes how
to apply Lean-Agile principles and practices to the specification, development, deployment, and evolution of large,
complex software applications and cyber-physical systems.
8. Capabilities: A higher-level solution behavior that typically spans multiple ARTs. Each is sized and split into
multiple features to facilitate their implementation in a single PI.
9. Communities of Practice (CoPs): Organized groups of people who have a common interest 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 a set of activities and artifacts that allow teams to apply Lean-Agile development
methods to build systems that have the highest possible quality, while simultaneously assuring they meet any regulatory,
industry, or other relevant standards.
11. Continuous Delivery Pipeline (or 'the 'pipeline'): The workflows, activities, and automation
needed to shepherd a new piece of functionality all the way from ideation to an on-demand release of value to the end
user.
12. Continuous Deployment (CD): The process that fosters innovation and builds alignment on what
should be built by continually exploring market and Customer needs, and defining a Vision, Roadmap, and set of
Features for a Solution that addresses those needs.
, Scaled Agile Framework (SAFe) Vocabulary
Study online at https://quizlet.com/_huk3f7
13. Continuous Exploration (CE): The process that fosters innovation and builds alignment on what
should be built by continually exploring market and Customer needs, and defining a Vision, Roadmap, and set of
Features for a Solution that addresses those needs.
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.
15. Core Values: These represent the fundamental beliefs that are key to SAFe's effectiveness. These guiding
principles help dictate behavior and action for everyone who participates in a SAFe portfolio.
Those principles are:
1. Alignment
2. Built-in quality
3. Transparency
4. Program execution
16. Customers: The ultimate buyer of every Solution. They are an integral part of the Lean-Agile development
process and the Value Stream and have specific responsibilities in SAFe.
17. Dev Team: A subset of the Agile Team. It consists of dedicated professionals who can develop, test, and deploy
a Story, Feature, or component. This subset typically includes software developers and testers, engineers, and other
dedicated specialists required to complete a vertical slice of functionality.
18. DevOps: A mindset, a culture, and a set of technical practices. It provides communication, integration, au-
tomation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a
Solution.
Uses the CALMR approach:
* Culture of Shared Responsibility
* Automation of Continuous Delivery Pipeline
* Lean flow accelerates delivery
* Measurement of everything
* Recovery enables low risk releases
19. DevOps and Release on Demand: A competency which describes how implementing a mindset,
a culture, and a set of technical practices as well as a continuous delivery pipeline provides the enterprise with the
capability to release value, in whole or in part, at any time necessary to meet market and customer demand.
