Transform Agile glossary

Leading an agile transformation means learning a second vocabulary, from scaling frameworks and portfolio funding to delivery metrics and federal contracting rules. This glossary explains the terms executives, PMO staff and transformation leads meet most often. Where a framework, guide or regulation defines a term officially, the entry follows that source's own wording.

Agile anti-pattern: A recurring practice that looks agile but undermines its purpose. Common examples include treating velocity or deployment counts as targets, appointing a Product Owner with no decision authority, and running Sprints inside an otherwise unchanged sequential process.; Related:Water-Scrum-Fall Goodhart's law Product Owner
Agile Manifesto: The 2001 Manifesto for Agile Software Development, written by 17 software practitioners. It states four value preferences, such as "Individuals and interactions over processes and tools," is backed by twelve principles, and notes that while the items on the right have value, the items on the left are valued more.; Related:Scrum Kanban
Agile readiness assessment: A structured look at whether an organization is prepared to adopt agile ways of working, done before or early in a transformation. It typically examines leadership support, funding and governance, team structure, technical practices and culture, and is used to decide where to start and which obstacles to tackle first. Published criteria such as GAO's Agile Assessment Guide can serve as a reference point.; Related:GAO Agile Assessment Guide Pilot team Transformation roadmap
Agile Release Train (ART): In SAFe, "a long-lived team of Agile teams that incrementally develops, delivers, and often operates one or more solutions in a development value stream." SAFe says ARTs are generally made up of 50 to 125 people and are cross-functional, with the capabilities to define, build, validate and release their solutions.; Related:Release Train Engineer (RTE)PI Planning Value stream
Agile transformation: An organization-wide change in how work is planned, funded, governed and delivered so that it follows agile values and principles, not just a change in how software teams run their day. It usually touches structure, roles, budgeting and leadership behavior as well as team practices, and it is normally done in stages rather than all at once.; Related:Business agility Transformation roadmap Pilot team
Business agility: Agility that reaches beyond IT into the whole business. SAFe defines it as the ability to compete and thrive in the digital age "by quickly responding to market changes and emerging opportunities" with innovative, digitally enabled business solutions.; Related:Agile transformation SAFe (Scaled Agile Framework)
Change fail rate: A DORA instability metric: the ratio of deployments that require immediate intervention after they go out, typically a rollback or a hotfix. DORA's research finds that speed and stability are not tradeoffs, and that top performers do well across all five metrics.; Related:DORA metrics Deployment rework rate Failed deployment recovery time
Change lead time: A DORA throughput metric: "the amount of time it takes for a change to go from committed to version control to deployed in production."; Related:DORA metrics Deployment frequency Flow metrics
Conway's Law: Mel Conway's observation that "any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure." Fred Brooks gave it the name in The Mythical Man-Month. For leaders, it means team structure and system architecture have to be changed together.; Related:Feature team Value stream
Cost of Delay: The money or value lost by delaying or not doing a piece of work for a period of time, relative to other work. In SAFe it is the numerator in WSJF prioritization, and SAFe's WSJF page opens with Don Reinertsen's line: "If you only quantify one thing, quantify the Cost of Delay."; Related:Weighted Shortest Job First (WSJF)Epic
Deployment frequency: A DORA throughput metric: the number of deployments over a given period, or the time between deployments. DORA warns against turning it into a blanket mandate for every application.; Related:DORA metrics Change lead time Goodhart's law
Deployment rework rate: A DORA instability metric: the ratio of deployments that are unplanned but happen as a result of an incident in production.; Related:DORA metrics Change fail rate Technical debt
Digital Services Playbook: A guide of 13 "plays" for building digital services, published by the U.S. DOGE Service, such as "Build the service using agile and iterative practices" and "Assign one leader and hold that person accountable." Each play comes with a checklist, and the TechFAR Hub offers a statement of objectives template that translates it into contract requirements.; Related:TechFAR Handbook Statement of objectives (SOO)
DORA metrics: Software delivery performance metrics from DORA, a long-running research program on software delivery and operations performance. DORA has moved from its original "four keys" to five metrics: three for throughput (change lead time, deployment frequency, failed deployment recovery time) and two for instability (change fail rate, deployment rework rate). DORA advises applying them to one application or service at a time and not using them to make teams compete.; Related:Change lead time Deployment frequency Goodhart's law
Epic: In SAFe, "a significant solution development initiative." Business epics deliver value directly to customers and enabler epics build technical foundations; because of their size, SAFe requires a defined minimum viable product (MVP) and approval by Portfolio Leadership, and manages them through the portfolio Kanban rather than as projects.; Related:Portfolio Kanban Weighted Shortest Job First (WSJF)Lean Portfolio Management (LPM)
Executive Action Team (EAT): The Scrum@Scale leadership team that "fulfills the Scrum Master accountabilities for an entire agile organization." It focuses on how the teams can get work done faster, creating the conditions for agile work to function and taking on continuous improvement and impediment removal.; Related:Scrum@Scale Executive MetaScrum (EMS)Executive sponsor
Executive MetaScrum (EMS): The Scrum@Scale forum where Chief Product Owners meet with executives and key stakeholders to fulfill the Product Owner role for the entire agile organization. It is where leadership and stakeholders express their preferences, focused on what the teams produce.; Related:Scrum@Scale Executive Action Team (EAT)Product Owner
Executive sponsor: The senior leader who owns a transformation's outcomes, secures its funding and removes organizational obstacles that teams cannot remove themselves. Good sponsorship goes beyond approval: it includes changing how the sponsor's own decisions, reviews and reporting expectations work.; Related:Lean-Agile Center of Excellence (LACE)Agile transformation Pilot team
Failed deployment recovery time: A DORA throughput metric: the time it takes to recover from a deployment that fails and requires immediate intervention. It replaced the older MTTR measure in DORA's model.; Related:DORA metrics Change fail rate
Feature team: As LeSS defines it, "a long-lived, cross-functional, cross-component team that completes many end-to-end customer features—one by one." It is contrasted with a component team, which owns one part or layer of a system, so delivering a customer feature requires handoffs between several teams.; Related:LeSS (Large-Scale Scrum)Conway's Law Requirement Area
FITARA: The Federal Information Technology Acquisition Reform Act, federal IT acquisition reform legislation enacted in 2014. Among its provisions, it requires CIOs at covered agencies to certify that certain IT investments are adequately implementing incremental development as defined in OMB's capital planning guidance; GAO describes Agile as one approach to that kind of iterative and incremental development.; Related:GAO Agile Assessment Guide Modular contracting
Flow efficiency: As SAFe defines it, "the ratio of the total time spent in value-added work activities divided by the total flow time." A low figure means items spend most of their time waiting, for example in queues, handoffs or approvals, which points leaders toward system fixes rather than asking people to work harder.; Related:Flow metrics Value stream
Flow metrics: Measures of how work moves through a system rather than how busy people are. SAFe uses six: flow distribution, flow velocity, flow time, flow load, flow efficiency and flow predictability; the Kanban Guide's minimum set is work in progress, throughput, work item age and cycle time.; Related:Flow efficiency Kanban DORA metrics
GAO Agile Assessment Guide: GAO-24-105506, the U.S. Government Accountability Office's guide to best practices for adopting and implementing Agile, published November 28, 2023 and reissued with revisions December 15, 2023. Written primarily for federal auditors, it covers Agile adoption, execution, and program monitoring and control, and GAO says organizations planning or in the middle of an adoption can also use it to inform their transitions.; Related:FITARA Agile readiness assessment TechFAR Handbook
Goodhart's law: The observation, named after economist Charles Goodhart, that a measure tends to stop being useful once people are pressured to hit it as a target. DORA lists ignoring it, for example by mandating that every application deploy multiple times per day by year's end, as a common pitfall with its metrics.; Related:DORA metrics Flow metrics Agile anti-pattern
Kanban: Defined in the Kanban Guide as "a strategy for optimizing the flow of value through a process," built on three practices: defining and visualizing a workflow, actively managing the items in it, and improving it. Leaders often meet it at portfolio level, where the same ideas are used to manage large initiatives.; Related:Portfolio Kanban Flow metrics
Lean budget guardrails: In SAFe, the policies and practices for budgeting, spending and governance for a specific portfolio. Together with value stream budgets, they are how portfolio leaders keep appropriate oversight of spending without returning to traditional project-based funding.; Related:Lean Budgets Lean Portfolio Management (LPM)
Lean Budgets: SAFe's financial governance approach that "funds value streams instead of projects," aiming to speed value delivery and cut the overhead of traditional project cost accounting. In SAFe, the portfolio budget is allocated across value streams through Strategic Investment Planning (formerly called Participatory Budgeting).; Related:Product-based funding Lean budget guardrails Lean Portfolio Management (LPM)
Lean Portfolio Management (LPM): In SAFe, the function that "aligns strategy and execution by applying Lean and systems thinking approaches to strategy and investment funding, Agile portfolio operations, and governance." It replaces project-by-project portfolio control with funding value streams and managing a flow of epics.; Related:Lean Budgets Portfolio Kanban Value Management Office (VMO)
Lean-Agile Center of Excellence (LACE): In SAFe, "a small Agile team dedicated to implementing the SAFe Lean-Agile way of working." Organizations using other approaches often set up a similar small, dedicated transformation team, sometimes called a transformation office.; Related:Executive sponsor Value Management Office (VMO)SAFe (Scaled Agile Framework)
LeSS (Large-Scale Scrum): Described on its official site as "Scrum applied to many teams working together on one product." All teams share one Product Owner, one Product Backlog, one common Sprint and one shippable product increment; there are two frameworks, LeSS for 2 to 8 teams and LeSS Huge for more than that.; Related:Requirement Area Feature team Scaling framework
Modular contracting: A Federal Acquisition Regulation approach (FAR 39.103, implementing 41 U.S.C. 2308; section 39.102 in the overhauled Part 39 under the ongoing Revolutionary FAR Overhaul) in which an IT system is bought in several smaller acquisition increments rather than one comprehensive contract. The FAR says it is intended to reduce program risk and incentivize contractor performance while giving the government timely access to rapidly changing technology.; Related:TechFAR Handbook FITARA Performance-based acquisition
Nexus: A scaling framework in which "a group of approximately three to nine Scrum Teams" work together on a single product, with one Product Owner and one Product Backlog. It extends Scrum "only where absolutely necessary" to manage dependencies, adding a Nexus Integration Team that ensures the group delivers an Integrated Increment at least once every Sprint.; Related:Scrum Scaling framework LeSS (Large-Scale Scrum)
Performance-based acquisition: Defined in the FAR as "an acquisition structured around the results to be achieved as opposed to the manner by which the work is to be performed." The TechFAR Hub notes that describing results rather than methods closely mirrors agile values and gives the contractor flexibility in how to deliver.; Related:Statement of objectives (SOO)Modular contracting TechFAR Handbook
PI Planning: SAFe's cadence-based planning event for an entire Agile Release Train, which aligns teams and stakeholders to a shared mission and vision. SAFe describes it as typically a two-day event held every 8 to 12 weeks to plan the next Planning Interval (PI), and its outputs include committed PI objectives and a board showing feature delivery dates and dependencies.; Related:Agile Release Train (ART)Release Train Engineer (RTE)
Pilot team: One or a few teams that adopt new agile practices first, so the organization can learn what works in its own context before expanding. A useful pilot works on real, valuable work, has an engaged sponsor and enough freedom to change how it operates, and its lessons feed the transformation roadmap.; Related:Agile readiness assessment Transformation roadmap Executive sponsor
Portfolio Kanban: In SAFe, "a method to visualize and manage the flow of portfolio epics, from ideation through analysis and implementation." Because each step to the right takes more effort, portfolio leaders decide which epics move forward and which are dropped, which makes all large initiatives visible in one place.; Related:Epic Kanban Lean Portfolio Management (LPM)
Product Owner: The Scrum accountability for "maximizing the value of the product resulting from the work of the Scrum Team," including managing the Product Backlog. The Scrum Guide adds that "the entire organization must respect their decisions," which is why leaders need to give the role real decision authority rather than make it a go-between.; Related:Scrum Agile anti-pattern Requirement Area
Product-based funding: Funding long-lived teams, products or value streams for a period of time instead of funding individual projects with fixed scope that start and stop. Leaders steer by adjusting priorities and investment levels at regular reviews rather than re-approving each project. SAFe's version is called Lean Budgets.; Related:Lean Budgets Value stream Lean Portfolio Management (LPM)
Psychological safety: Defined by Amy Edmondson in a 1999 Administrative Science Quarterly paper as "a shared belief held by members of a team that the team is safe for interpersonal risk taking." Her study linked it to team learning behavior, which matters in agile work because inspecting and adapting depends on people raising problems early.; Related:Executive sponsor Agile anti-pattern
Release Train Engineer (RTE): In SAFe, "a servant leader and ART coach who facilitates ART events and processes, and supports teams in delivering value." The RTE also helps manage risks and impediments and, beyond the ART, coaches leaders and teams in the wider transformation.; Related:Agile Release Train (ART)PI Planning
Requirement Area: In LeSS Huge, a major area of customer concern used to divide a very large product once it grows beyond about eight teams. A Requirement Area normally has four to eight teams and its own Area Product Owner, who focuses on that area's Area Product Backlog, while the product still has one overall Product Owner.; Related:LeSS (Large-Scale Scrum)Product Owner Feature team
SAFe (Scaled Agile Framework): SAFe® describes itself as a knowledge base of integrated principles, practices and competencies for achieving business agility using Lean, Agile and DevOps. It comes in configurations ranging from Essential SAFe, which it calls "the simplest starting point for implementation," to Full SAFe for enterprises with portfolios of large, complex solutions.; Related:Agile Release Train (ART)Lean Portfolio Management (LPM)Scaling framework
Scaling framework: A published model for coordinating many agile teams that work on the same product or portfolio. Examples include SAFe, LeSS, Scrum@Scale and Nexus, which differ considerably in how much structure, how many roles and how many events they add on top of team-level practices.; Related:SAFe (Scaled Agile Framework)LeSS (Large-Scale Scrum)Scrum@Scale
Scrum: A framework that, in the words of the Scrum Guide, "helps people, teams and organizations generate value through adaptive solutions for complex problems." It is founded on empiricism and lean thinking, and a small, cross-functional, self-managing Scrum Team works in fixed-length Sprints of one month or less.; Related:Product Owner Agile Manifesto Nexus
Scrum of Scrums: In Scrum@Scale, a group of teams that "operates as if it were a Scrum Team," with scaled versions of Scrum's accountabilities, events and artifacts and a Scrum of Scrums Master who keeps the scaled events productive and within their time-box. The phrase is also used more loosely for any regular coordination meeting of team representatives.; Related:Scrum@Scale Executive Action Team (EAT)
Scrum@Scale: Described in the Scrum@Scale Guide (version 2.1, February 2022) as "a lightweight organizational framework in which a network of teams operating consistently with the Scrum Guide can address complex adaptive problems." It coordinates the "how" through a Scrum Master Cycle and the "what" through a Product Owner Cycle, supported by a "minimum viable bureaucracy" of two leadership groups.; Related:Scrum of Scrums Executive Action Team (EAT)Executive MetaScrum (EMS)
Statement of objectives (SOO): A government-prepared document used in performance-based acquisition: under FAR 37.602 (section 37.102-1 in the overhauled Part 37 under the ongoing Revolutionary FAR Overhaul), the government can issue a statement of objectives and have offerors propose the performance work statement (PWS), which describes the required results in measurable terms. Stating objectives and letting offerors propose the approach fits agile delivery, where detailed requirements emerge over time.; Related:Performance-based acquisition Digital Services Playbook
TechFAR Handbook: Guidance launched with the Digital Services Playbook in August 2014 to show how to carry out its play "Structure budgets and contracts to support delivery." It describes flexibilities already available in acquisition regulations and laws for buying digital services through contracts, and it was later expanded into the TechFAR Hub, published by the U.S. DOGE Service as a resource for acquisition and program staff buying agile services.; Related:Digital Services Playbook Modular contracting Performance-based acquisition
Technical debt: The future cost of rework created when teams take shortcuts or let design and code quality slip to deliver sooner. Like financial debt it carries interest, because each later change gets slower and riskier, so leaders need to leave capacity to pay it down rather than filling every iteration with new features.; Related:Deployment rework rate Change fail rate
Transformation roadmap: A plan for the order in which an organization adopts new ways of working: which teams or value streams go first, what training and role changes are needed, and how progress will be reviewed. It should be revisited as the organization learns. Some frameworks publish their own; the SAFe Implementation Roadmap, for example, describes "an ordered set of activities" for implementing SAFe.; Related:Pilot team Agile transformation Value stream
Value Management Office (VMO): SAFe's term for the function that facilitates Lean Portfolio Management and fosters operational excellence and lean governance. SAFe uses the label to mark a shift from a traditional project or program management office (PMO) that tracks projects toward long-lived products and flow-based delivery.; Related:Lean Portfolio Management (LPM)Lean-Agile Center of Excellence (LACE)
Value stream: In SAFe's words, "the sequence of activities that contains all the people, systems, information, and materials needed to deliver value to a customer." SAFe separates operational value streams, such as fulfilling an order, from the development value streams that build the solutions they use. Organizing teams and funding around value streams instead of departments or projects is a common step in a transformation.; Related:Agile Release Train (ART)Lean Budgets Conway's Law
Water-Scrum-Fall: An anti-pattern in which teams run Sprints in the middle, while requirements, budgeting and approvals up front, and testing, release and sign-off at the end, still follow a traditional sequential process. Teams look agile, but the organization still gets feedback late.; Related:Agile anti-pattern Modular contracting
Weighted Shortest Job First (WSJF): A SAFe prioritization model "used to sequence work for maximum economic benefit," estimated as relative cost of delay divided by relative job duration. SAFe builds it from relative user and business value, time criticality, risk reduction and/or opportunity enablement, and job size, and notes that it ignores sunk costs.; Related:Cost of Delay Portfolio Kanban Epic