Glossary of Terms used throughout the Course
The Beyond Agile Reference of Terms is a glossary of concepts and terminology used throughout the Beyond Agile course.
The glossary brings together terms from product and delivery leadership, Agile, team development, use cases, data modelling, the Dreyfus model, Team Topologies and Belbin team roles. Each entry consists of a term accompanied by a short description explaining how the concept is used or understood in the context of the course.
As an example, here is a randomly selected term:
Beyond Agile Glossary of Terms
Er staan momenteel 196 Beyond Agile terms in deze lijst.
A
Acceptance
The decision that a delivered change is suitable for its intended use and meets the product need, not merely that specified checks have passed.
Acceptance Criteria
Conditions used to clarify what a piece of work must satisfy. They support shared understanding and testing but do not replace judgement about the overall product.
Acceptance Testing
Testing from the perspective of the user, customer or product to determine whether the delivered result is fit for its intended use.
Accountability
Being answerable for a result or decision. Accountability can be assigned, while effective ownership also depends on engagement and judgement.
Advanced Beginner
In the Dreyfus model, a learner who starts to recognize recurring situational aspects but still needs guidance in deciding what matters most.
Agile
An approach to product development that emphasizes learning, adaptation, collaboration and frequent delivery of value. Agile is broader than a single framework or set of ceremonies.
Agile Manifesto
The 2001 statement of values and principles that helped shape modern Agile software development, emphasizing people, working software, customer collaboration and responsiveness to change.
Alignment
A shared understanding of goals, priorities, constraints and direction that allows people to make compatible decisions without constant coordination.
Allowable Weakness
In the Belbin model, a characteristic downside that can accompany the strength of a team role and may be acceptable when understood and managed.
Alternative Flow
A valid variation from the main success scenario that still leads to a meaningful result.
Ambition
The level of product impact or completeness being pursued. Beyond Agile encourages protecting meaningful product ambition while reducing lower-value detail when necessary.
Autonomy
The freedom for a team or individual to make decisions within clear boundaries. Useful autonomy requires sufficient context, competence and responsibility.
B
Backlog
An ordered collection of possible work for a product. It is a planning aid, not a complete description of the product or its vision.
Backlog Refinement
The ongoing activity of clarifying, splitting, ordering and preparing potential work so that the team can make informed delivery decisions.
Batch Size
The amount of work handled as one unit before feedback or delivery occurs. Smaller batches usually make learning and correction faster.
Belbin Team Roles
A model developed by Meredith Belbin describing nine complementary patterns of contribution and behavior that people can bring to team work. The roles describe tendencies, not fixed personality types or job titles.
Beyond Agile
A product and delivery perspective in which Agile practices are useful tools, but not the goal. Effective delivery also requires vision, leadership, judgement, quality, proficiency and responsibility for the whole result.
Bottleneck
The part of a delivery system that limits overall flow or throughput. Improving work elsewhere may have little effect until the bottleneck is addressed.
Build–Measure–Learn
A feedback cycle in which an idea is built, its effect is observed and the result is used to improve the next decision.
Built-in Quality
The principle that quality is created throughout design, development, integration and testing rather than inspected into the product afterwards.
Business Rule
A rule, policy or condition from the domain that affects decisions or behavior in the product.
C
Capability
Something a product or team is able to do. A capability is broader and more enduring than an individual task or user story.
Cardinality
The allowed number of instances participating in a relationship, such as one-to-one, one-to-many or many-to-many.
Ceremony
An informal term for a recurring Agile event such as a stand-up, review or retrospective. The event only has value when it helps the team achieve a useful outcome.
Co-creation
Developing understanding and solutions together with people who hold relevant product, user, business or technical knowledge.
Coaching
Helping someone improve by providing context, questions, feedback and guided experience rather than only giving instructions.
Cognitive Load
The amount and complexity of information a team must understand and keep in mind to perform effectively. Excessive cognitive load slows learning and delivery.
Collaboration
Working together to create a shared result rather than dividing work into isolated responsibilities and handing it from one role to another.
Collaboration Mode
A temporary, close working relationship between teams used when high interaction is needed to discover or create something new.
Competence
The ability to perform a task to an adequate standard. Competence is not identical to proficiency or expertise.
Competent Performer
In the Dreyfus model, a practitioner who can plan, prioritize and choose among alternatives deliberately, accepting responsibility for the chosen approach.
Completer Finisher
A Belbin action role focused on detail, quality and follow-through, helping the team find errors and ensure that work is genuinely finished.
Complexity
The degree to which a situation contains interacting elements, uncertainty and effects that cannot be fully predicted in advance.
Complicated-subsystem Team
A team responsible for a part of the system requiring specialist knowledge that would otherwise impose excessive cognitive load on other teams.
Conceptual Data Model
A high-level model of the important business concepts and their relationships, independent of technical implementation details.
Constraint
A limitation or condition that shapes possible product or delivery choices, such as legislation, technology, time, budget or organizational boundaries.
Context
The information and understanding needed to make a sound decision. Giving teams context often enables better autonomy than prescribing detailed instructions.
Continuous Delivery
The capability to keep software in a releasable state and deliver changes frequently and reliably through a repeatable process.
Continuous Improvement
The habit of repeatedly examining how the product and delivery system work and making practical changes based on what is learned.
Continuous Team Evolution
The idea that team boundaries, responsibilities and interactions should evolve as products, architecture and organizational needs change.
Conway's Law
The observation that system designs tend to reflect the communication structures of the organizations that create them.
Coordinator
A Belbin social role focused on clarifying goals, drawing out contributions and delegating effectively so that the team can use its strengths.
Cross-functional Team
A team containing enough complementary knowledge and skills to create a meaningful product result without relying on a chain of specialist hand-offs.
Customer
The person or organization for whom value is created or who commissions or pays for the product. The customer may differ from the end user.
D
Data Lifecycle
The stages data passes through from creation and use to retention, archival or deletion.
Data Model
A structured representation of the information a product needs, including entities, attributes, relationships and rules. It helps make product concepts explicit and consistent.
Data Ownership
Clear responsibility for the meaning, quality, lifecycle and appropriate use of particular data.
Data Quality
The degree to which data is accurate, complete, consistent, timely and fit for its intended use.
Decision Maker
A person with the authority or responsibility to make or confirm a decision that affects the product.
Definition of Done
A shared minimum standard that work must meet before it is considered complete. It supports consistency but does not by itself guarantee that the product is good.
Deliberate Practice
Focused practice aimed at improving specific skills through challenge, feedback and correction rather than simple repetition.
Delivery
Turning product direction into a coherent, usable and sufficiently high-quality result that reaches the people who need it. Delivery is more than completing backlog items.
Delivery Leadership
Creating the conditions in which a team can turn product direction into a coherent, usable and high-quality result.
Denormalization
Deliberately combining or duplicating data to improve performance or usability when the trade-off is justified.
Dependency
A relationship in which progress or completion relies on another person, team, system, decision or piece of work.
Developer
A team member who contributes to creating the product. In a mature product team, developers also contribute judgement, design ideas and product understanding.
Domain Model
A representation of the important concepts, rules and relationships in the problem domain, used to create a shared language between product and technical participants.
Dreyfus Model of Skill Acquisition
A model describing progression from novice toward expert performance, with increasing reliance on experience, context and situational judgement rather than explicit rules.
E
Edge Case
A less common but plausible condition near the limits or boundaries of expected product behavior.
Effectiveness
The degree to which an action or product achieves the intended result. Doing the right thing matters as much as doing things efficiently.
Efficiency
How economically work is performed in terms of time, effort and resources. Efficient work is not automatically effective or high quality.
Empiricism
Making decisions based on observation, evidence and experience rather than relying only on prediction or theory.
Enabling Team
A team that helps other teams develop missing capabilities, learn new approaches or overcome technical and organizational obstacles.
End-to-End Responsibility
Taking responsibility for the complete result experienced by the user, including integration, quality and usability, rather than only for an assigned component.
Entity
A distinct business concept or thing about which the product needs to store information, such as a Person, Order, Property or Application.
Exception Flow
A path describing what happens when the normal interaction cannot continue because an error, rule or unusual condition occurs.
Experience
Exposure to varied real situations that develops a richer repertoire of patterns and judgement. Time served alone does not guarantee expertise.
Experiment
A deliberate test designed to reduce uncertainty by observing what happens under real or representative conditions.
Expert
In the Dreyfus model, a highly experienced practitioner who often recognizes appropriate action intuitively through deep pattern recognition while remaining able to reflect when necessary.
Expert Judgement
Decision-making that draws on deep experience, pattern recognition and contextual understanding rather than only explicit procedures.
Extend Relationship
A use case relationship indicating optional or conditional behavior added to another use case at a defined point.
Extraneous Cognitive Load
Mental effort created by unnecessary complexity in tools, processes, architecture or organization rather than by the underlying problem.
F
Facilitating Mode
An interaction mode in which one team helps another acquire skills, knowledge or capability rather than taking over the work permanently.
Fast Flow
The ability for valuable changes to move quickly and safely from idea to users, supported by suitable team boundaries, architecture and interactions.
Feature
A meaningful product capability that provides recognizable behavior or value. A feature may require multiple stories and technical changes.
Feedback
Information about the effect of a product, decision or way of working that can be used to adjust what happens next.
Feedback Loop
A recurring cycle in which an action produces information that influences the next action. Shorter feedback loops generally make adaptation faster.
Flow
The movement of work through the delivery system from idea toward a usable result, with as little waiting, rework and unnecessary interruption as practical.
Focus Group
A recurring working group of key stakeholders, knowledge holders and decision makers used to shape, challenge and prioritize product direction.
Foreign Key
A stored reference that links one record to another and helps enforce a relationship between data structures.
Framework
A structured set of roles, events, artifacts or practices intended to help organize work. A framework supports delivery but should not become the purpose of the work.
Functional Maintenance
The ongoing responsibility for ensuring that a product continues to support its users and business processes correctly after initial delivery.
G
Germane Cognitive Load
Mental effort used to learn, build expertise and develop useful mental models for the work.
H
Hand-off
The transfer of work or responsibility from one person or team to another. Frequent hand-offs can reduce context and slow feedback.
Happy Path
The straightforward scenario in which the intended interaction succeeds without exceptions.
I
Identifier
A value or combination of values used to distinguish one instance of an entity from another.
Implementer
A Belbin action role that turns ideas and decisions into practical, organized work. Implementers value reliability, structure and workable plans.
Include Relationship
A use case relationship indicating that one use case always incorporates behavior defined by another reusable use case.
Independent Flow
A condition in which a team can make and deliver useful changes without repeatedly waiting for other teams.
Information Product
A product or output whose value depends on structured information. Capturing the underlying data in the product usually enables more sustainable reuse than creating the output manually outside it.
Integration
Combining parts of a product so they work together as one coherent whole. Local success is insufficient when the integrated product does not work.
Intent
The purpose behind a requirement, feature or decision. Understanding intent allows the team to propose better solutions than simply following instructions.
Intrinsic Cognitive Load
Mental effort inherent in the problem itself and difficult to remove without changing the nature of the work.
Intuition
Rapid judgement grounded in accumulated experience and pattern recognition. In expertise, intuition is not the same as guessing.
Inverse Conway Maneuver
Deliberately shaping team and communication structures so that they encourage the desired architecture and flow of the product.
Iteration
A repeated development cycle in which a product or solution is refined using what was learned previously.
J
Judgement
The ability to choose an appropriate course of action in context, especially when rules or predefined procedures are insufficient.
K
Knowledge Holder
A person who possesses relevant domain, technical, operational or user knowledge needed to make sound product decisions.
L
Lead Engineer
A technical leader who helps the team translate product intent into coherent implementation and guides technical delivery beyond individual tasks.
Lead Time
The elapsed time from a request or idea entering the system until the resulting value is delivered.
Leadership
Helping people move toward a worthwhile result through direction, judgement, support and influence. Leadership is not limited to formal management roles.
Logical Data Model
A more detailed representation of entities, attributes, identifiers and relationships while remaining largely independent of a specific database technology.
M
Main Success Scenario
The normal sequence of interactions through which the actor successfully achieves the use case goal.
Management
The coordination of people, resources, responsibilities and constraints. Management and leadership overlap, but they are not the same thing.
Master Data
Core information about important business entities that is shared and reused across processes or systems.
Mentoring
Supporting a less experienced person through the experience, perspective and advice of a more experienced practitioner.
Method
A defined way of working. Methods can help teams coordinate and learn, but should remain subordinate to the product and its goals.
Minimum Viable Product
The smallest product or product version that can produce meaningful learning or value. It should be viable as a product, not merely small.
Monitor Evaluator
A Belbin thinking role characterized by sober analysis, strategic judgement and the ability to weigh options objectively before deciding.
N
Non-functional Requirement
A requirement concerning qualities or constraints such as performance, security, accessibility, reliability or maintainability.
Normalization
Organizing data to reduce unnecessary duplication and improve consistency by separating distinct concepts into appropriate structures.
Novice
In the Dreyfus model, a beginner who relies heavily on context-free rules and clear instructions because experience is still limited.
O
Outcome
The effect or change created by the product, such as improved user success, reduced effort or better organizational performance.
Output
Something produced by the team, such as a feature, release, document or story. Output is useful only insofar as it contributes to the desired outcome.
Ownership
A sense of responsibility for the quality and outcome of the work, including acting on issues rather than merely identifying them.
P
Pattern Recognition
The ability to recognize familiar structures or situations based on experience, enabling faster and more nuanced judgement.
Physical Data Model
A technical representation of how data is actually stored, including tables, columns, keys, indexes and implementation-specific choices.
Plant
A Belbin thinking role characterized by creativity, imagination and unconventional ideas. Plants often help solve difficult problems but may pay less attention to practical detail or communication.
Platform as a Product
Treating an internal platform as a product with users, needs, usability, feedback and a clear value proposition rather than merely as shared infrastructure.
Platform Team
A team that provides internal services or capabilities that allow stream-aligned teams to deliver with greater autonomy and lower cognitive load.
Postcondition
A condition that should be true after a use case has completed successfully, or after a defined alternative outcome.
Primary Actor
The actor whose goal is achieved by the use case and who normally initiates the interaction.
Priority
The relative importance or urgency of work when compared with other possibilities. Priority should reflect product direction rather than only stakeholder pressure.
Process
The sequence of activities used to achieve a result. Beyond Agile distinguishes the process of working from the product that the process is intended to create.
Product
The thing that is created, used and evolved to produce value. A product is more than the project, backlog or process used to build it.
Product Leadership
Providing direction about the product, including its purpose, priorities, coherence, value and future development.
Product Owner
The person accountable for product direction and product decisions, working closely with stakeholders and the people who build the product.
Product Strategy
The set of choices about where and how a product will create value and how the vision will be pursued over time.
Product Vision
A shared understanding of what the product should become, for whom, why it matters and what direction should guide decisions.
Productivity
The relationship between useful results and the resources used to achieve them. Activity alone is not productivity.
Proficiency
The ability to perform work well using knowledge, experience and situational judgement, rather than merely following a procedure.
Proficient Performer
In the Dreyfus model, a practitioner who perceives situations more holistically and can recognize what is important based on accumulated experience.
Q
Quality
A characteristic of the delivered product and therefore part of delivery, not something that can be added only at the end.
R
Reference Data
Relatively stable values used to classify or constrain other data, such as categories, countries, statuses or standardized codes.
Referential Integrity
The assurance that references between related data remain valid and do not point to missing or inappropriate records.
Relationship
An association between entities that expresses how instances of one concept relate to instances of another.
Release
A version or set of changes made available for use. A release can contain one or more increments or features.
Requirement
A need, constraint or capability that the product must address. A requirement describes something important, but not necessarily the best implementation.
Resource Investigator
A Belbin social role characterized by curiosity, enthusiasm and exploration of opportunities, contacts and ideas outside the team.
Rework
Work that must be repeated or corrected because the earlier result was incomplete, misunderstood or insufficiently integrated.
Rule-based Learning
Learning or working primarily through explicit instructions and procedures. It is especially useful for novices but becomes limiting when applied rigidly to complex work.
S
Scenario
A concrete example of how a use case or product behavior unfolds under particular conditions.
Scope
The set of capabilities, changes or work included within a particular effort, release or product boundary.
Scope Boundary
A deliberate statement of what is and is not part of the product or a particular use case.
Shaper
A Belbin action role that brings drive, challenge and momentum, especially under pressure. Shapers push the team toward action but can sometimes be provocative.
Shared Understanding
A sufficiently common mental model of the product, users, problem, priorities and constraints that enables coordinated decisions.
Situational Awareness
The ability to notice which aspects of a situation are relevant and understand how they affect the choice of action.
Skill Acquisition
The process by which a person develops from rule-based beginner performance toward increasingly contextual, fluent and intuitive performance.
Source of Truth
The authoritative place from which a particular piece of information should be obtained when multiple copies or representations exist.
Specialist
A Belbin thinking role that contributes deep knowledge or skill in a particular area. Specialists add expertise but may focus primarily on their own domain.
Stakeholder
A person or group with an interest in, influence on or responsibility for the product or its outcomes.
Story Point
A relative estimate sometimes used by Agile teams to compare effort, complexity or uncertainty. It is a planning aid, not a measure of value or individual productivity.
Stream-aligned Team
A team aligned to a flow of work that delivers value to a customer or user, with responsibility for a meaningful slice of the product or service.
System Boundary
The conceptual boundary that separates what the system is responsible for from actors and services outside it.
T
Tacit Knowledge
Knowledge gained through experience that may be difficult to fully express as explicit rules or documentation.
Team API
A clear description of how a team can be approached and worked with, including responsibilities, services, communication preferences and interaction expectations.
Team Boundary
A deliberately chosen area of responsibility that gives a team enough coherence and autonomy to deliver meaningful results.
Team Coupling
The degree to which teams depend on frequent coordination with one another. High coupling can slow decisions, learning and delivery.
Team Interaction Mode
A defined way in which teams work together. Team Topologies distinguishes collaboration, X-as-a-Service and facilitating.
Team Responsibility
The expectation that the team collectively cares about the complete product result, not only the completion of individual assigned tasks.
Team Role Balance
The idea that teams benefit from having access to a complementary range of contributions rather than expecting every person to behave in the same way.
Team Topologies
An approach described by Matthew Skelton and Manuel Pais for organizing business and technology teams for fast flow, with particular attention to team responsibilities, cognitive load and interaction patterns.
Team-first Thinking
Designing organizational structures around the needs and limitations of real teams rather than treating people as interchangeable resources.
Teamworker
A Belbin social role focused on cooperation, listening, diplomacy and helping the team maintain constructive relationships.
Technical Debt
A future cost created by technical choices that make later change, maintenance or reliability harder. Some debt is deliberate; unmanaged debt reduces delivery capability.
Test Data
Data prepared to exercise realistic product behavior, edge cases and business rules during testing.
Test Scenario
A realistic situation or sequence of actions used to examine whether the product behaves as intended.
Thinnest Viable Platform
The smallest useful platform capability that reduces friction for consuming teams without becoming an unnecessarily large centralized product.
Throughput
The amount of work completed over a given period. Throughput describes output, not necessarily value or quality.
Traceability
The ability to connect product decisions, requirements, data and delivered behavior back to their origin and forward to their implementation or outcome.
Trade-off
A decision in which improving one desirable quality requires accepting a cost or reduction elsewhere.
Transactional Data
Data created as events or activities occur, such as requests, payments, decisions or status changes.
U
Ubiquitous Language
A shared vocabulary used consistently by domain experts and product or technical teams so that important concepts have the same meaning across discussion, models and implementation.
Ultimate Client Perspective
A delivery mindset in which someone works with the team as if personally responsible for the experience of the final customer, continually checking whether design and implementation serve the intended product.
Uncertainty
A lack of reliable knowledge about what will happen, what users need or how a solution will behave. Product work reduces uncertainty through learning and feedback.
Use Case
A description of how an actor interacts with a system to achieve a meaningful goal, including the normal flow and relevant alternatives or exceptions.
Use Case Diagram
A visual overview of actors, use cases and their relationships, used to discuss system scope and user goals.
User Story
A lightweight way to express a user-oriented need or piece of work. A user story is a conversation aid, not the product requirement itself.
V
Value
The benefit created for users, customers or the organization relative to the effort, cost and consequences involved.
Vertical Slice
A thin piece of functionality that crosses the necessary layers of the product and can be evaluated as working behavior.
W
Work in Progress
Work that has been started but is not yet completed. Excessive work in progress increases waiting, switching and delivery time.
X