The Most Important Terms in the Agile and Hybrid World
Below are the most important terms used in the agile world that should definitely be known.
Acceptance Criteria
The specific requirements that must be met for a user story or task to be considered complete.
Agency Backlog
A list of tasks, projects, or initiatives that need to be addressed by an agency or a creative team.
Agency Retainer
A contractual arrangement where a client pays an agency a regular fee, often monthly, in exchange for continuous service or consultation.
Agile Coach
An expert in agile methodologies who helps teams and organizations effectively introduce and utilize agile practices.
Agile Creative Process
An approach to creative work that uses agile principles and practices to foster flexibility and rapid feedback.
Agile Manifesto
A document that defines the core principles and values of the agile approach.
Agile Metrics
Measures used to monitor and assess the progress, quality, and efficiency of agile projects.
Agile Metrics
Measures used to monitor and assess the progress, quality, and effectiveness of agile projects.
Agile Transformation
The process of transitioning an organization from traditional to agile ways of working.
Agility
An approach aimed at adaptability and flexibility in projects and organizations. It enables quick responses to changes and promotes continuous improvement.
Backlog
A prioritized list of tasks, features, or requirements to be implemented in a project or product.
Backlog Refinement
The process of reviewing, prioritizing, and refining backlog items to prepare them for future work.
Blocking
A state in Kanban where a task or work item cannot move forward, often due to dependencies or impediments.
Brand Sprint
A short, intense workshop aimed at quickly defining or refining a company's brand identity and strategy.
Burn-up Chart
A chart that shows the progress of a project over time by displaying the amount of work completed against the total work.
Burndown Chart
A chart that shows a team's progress during an iteration or sprint by plotting the remaining work against time.
Business Agility
The ability of a business to quickly adapt to market changes, seize opportunities, and respond to threats.
Campaign Kanban
A specific Kanban approach focused on marketing and advertising campaigns, tracking the progress of campaign elements.
Change Management
The process of planning, implementing, and managing changes within a company or project to achieve the desired state.
Chickens and Pigs
A term from Scrum describing the different levels of involvement of team members and other stakeholders in a project. "Chickens" are indirectly involved, while "Pigs" are directly involved and committed.
Chickens and Pigs
A term from Scrum describing the involvement of individuals in a project. "Pigs" are directly involved and "Chickens" are indirectly involved.
Client Onboarding
The process of integrating and introducing new clients to an agency's or company's services and processes.
Client Owner
The person or group defining the requirements and expectations for a project or product and responsible for its success.
Cone of Uncertainty
A concept that describes how the uncertainty of project estimates decreases over time.
Cone of Uncertainty
A model that illustrates uncertainty in estimates at the beginning of a project, with uncertainty decreasing over time.
Content Iteration
The process of repeatedly revising and improving content based on feedback and performance data.
Continuous Delivery
An approach where software is produced in short cycles to ensure it is always production-ready quality.
Continuous Deployment
A process where software changes are automatically and continuously deployed to production, often multiple times a day.
Continuous Deployment
A process where software changes are automatically and continuously rolled out to the production environment.
Continuous Improvement
An ongoing process of identifying and implementing improvements in products, services, or processes.
Continuous Integration
A software development practice where code changes are regularly integrated into the main codebase.
Creative Review
A process where creative work is reviewed and feedback is given, often in advertising or design agencies.
Critical-Path Method
A technique for planning and controlling projects, identifying critical tasks that determine the overall project schedule.
Cross-Functional Collaboration
The collaboration of teams or individuals from different departments or areas of expertise to achieve common goals.
Cross-functional Team
A team that includes members with diverse expertise and skills to cover all aspects of a project or product.
Cycle Time
The time it takes for a task or work item to move through a process from start to finish.
Daily Stand-up
A daily, short meeting where team members discuss their progress and impediments.
Dark Scrum
A term describing when Scrum practices are implemented in a way that does not adhere to Scrum's values and principles.
Dark Scrum
A term describing a distortion of Scrum practices, often caused by external factors, that impairs team effectiveness.
Definition of Done
A set of criteria that must be met for a task or user story to be considered complete.
Empirical Process Control
An approach to process control based on observation and experimentation, rather than detailed upfront planning.
Empowerment
The ability for employees to make decisions and take responsibility for their work.
Epic
A large work package or requirement that can be broken down into smaller user stories or tasks.
Expert Orbits
A concept where experts in specific areas collaborate to share knowledge and best practices.
Feature Creep
The continuous addition of new features to a product, often at the expense of original requirements and goals.
Feature Creep
The continuous addition of new features to a project, often without clear prioritization, leading to delays and increased costs.
Feature Team
A team focused on developing a specific feature or function.
Feature Toggle
A technique where specific software functionalities can be enabled or disabled without changing the code.
Feedback Loops
Mechanisms that allow for regular feedback from customers, team members, or other stakeholders to drive continuous improvements.
Flow Efficiency
A measure of how efficiently work flows through a process, often calculated as actual working time divided by total lead time.
Flowchart
A diagram that represents the flow of a process or system, often with decision points and various paths.
Gantt
A bar chart that visualizes a project's schedule, including start and end dates of tasks and their dependencies.
Gemba Walk
A concept from Lean Management where leaders visit the actual place of work (e.g., a production facility) to learn directly from employees and improve processes.
Grooming
A process in Scrum where the team reviews and refines the Product Backlog to ensure that items are clear and ready for development.
Hardening Sprint
A special sprint in Scrum focused on stabilizing and bug fixing before a product release.
Hardening Sprint
A special sprint in Scrum aimed at paying down technical debt, fixing bugs, and preparing the software for production.
Holacracy
An organizational model that replaces traditional hierarchies with a system of role-based circles that operate autonomously and self-organize.
Hybrid Agile
An approach that combines elements from agile and traditional project management methodologies.
Hybrid Agile
An approach that combines traditional and agile methods to meet the specific requirements of a project or organization.
Impediment
An obstacle or barrier that prevents a team from efficiently completing its work.
Information Radiator
A large, visible display used to show the status and progress of a project in real-time.
Information Radiator
A physical or electronic display that shows information about project status in a team room or other public location.
Increment
A usable partial product delivered at the end of a sprint or iteration.
Inspect and Adapt
A core principle of Scrum where teams regularly review their work and make adjustments to improve.
Iteration
A short, fixed period during which a team completes a specific amount of work.
Kaizen
A Japanese word meaning "continuous improvement" and describing an approach where all employees are involved in constantly improving processes.
Kanban
A visual management tool that illustrates the workflow and helps identify bottlenecks and increase efficiency.
Kanban Board
A visual tool that represents the flow of tasks through various phases or states, typically from "to do" to "done."
Kanban Card
A physical or digital tool in Kanban that represents a single task or work item and tracks its progress through the Kanban system.
Kanban Replenishment
The process of refilling or adding new tasks to a Kanban system, based on priority and capacity.
Kanban-Board
A visual tool for displaying and tracking tasks or work items, where cards are moved in columns or rows to indicate progress.
Last Responsible Moment
The concept of postponing decisions for as long as possible until they must be made, to maximize flexibility.
Last Responsible Moment
The concept of delaying decisions for as long as possible to make them based on the most current information.
Lead Time
The time required from the start to the completion of a task or process.
Lean
A production practice aimed at minimizing waste and maximizing value for the end customer.
Matrix Diagram
A diagram that shows relationships between two or more groups of information, often in the form of a matrix or table.
Minimum Viable Product (MVP)
The simplest version of a product that can be tested to maximize feedback and learning opportunities.
MLP (Minimum Lovable Product)
A version of a product that is not only minimally functional but also delightful to users.
Mood Board
A visual tool that uses images, colors, textures, and other design elements to convey the mood or atmosphere of a project or concept.
MoSCoW
A technique for prioritizing requirements, where M stands for "Must have," S for "Should have," C for "Could have," and W for "Won't have."
Network Diagram
A graphical tool for representing the relationships between different elements or tasks in a project.
Niko-Niko Calendar
A tool for tracking team members' mood and well-being, often in the form of a calendar with facial expressions.
Niko-Niko Calendar
A mood tracker where team members mark their mood daily on a calendar to follow team sentiment over time.
OKRs (Objectives and Key Results)
A goal-setting framework where teams and individuals define clear, measurable goals (Objectives) and the key results (Key Results) that show how these goals will be achieved.
Organizational Culture
The values, beliefs, behaviors, and norms shared within an organization that influence how people work and interact.
Pair Programming
A technique where two developers work together at one computer, with one writing the code and the other reviewing it.
Pareto Chart
A bar chart that shows the causes of problems in decreasing order of their importance or frequency, based on the Pareto Principle (80/20 rule).
Persona Development
The process of creating fictional characters that represent the main target groups of a product or service to inform design and development.
PERT Diagram (Program Evaluation and Review Technique)
A network diagram used to analyze and represent the temporal sequence of tasks in a project.
Planning Poker
A technique for estimating tasks in Scrum, where team members use cards with numbers on them to give their estimates.
Potentially Shippable Product Increment
A central concept in Scrum, which states that the result of each sprint should be a product increment that could potentially be delivered.
Potentially Shippable Product Increment
A central concept in Scrum, which states that at the end of each sprint, a product increment should be created that is potentially deliverable.
Product Backlog
A prioritized list of requirements or work orders to be implemented in a product.
Product Backlog Item (PBI)
A single entry in a Product Backlog representing a requirement or feature for the product.
Product Owner
The person responsible for defining and prioritizing requirements in the backlog and ensuring that the team implements the right things in the right order.
Product Vision
A clear and inspiring statement that describes the purpose and direction of a product.
Product Vision
A clear and inspiring statement about the long-term direction and purpose of a product.
Work Breakdown Structure (WBS)
A hierarchical diagram representing the structure and various elements of a project.
Pull System
A concept in Kanban where work is only started when capacity is available, as opposed to a push system where work is assigned based on predictions.
RACI (Responsible
A matrix tool for clarifying roles and responsibilities in a project or process, where RACI stands for Responsible, Accountable, Consulted, and Informed.
Refactoring
The process of restructuring existing code without changing its external behavior to improve readability or efficiency.
Release
The introduction of a new product or a new version of a product to the market.
Release Planning
A process in Scrum where the team plans which features or user stories will be included in a specific release.
Retrospective
A meeting at the end of an iteration where the team reflects on what went well and what could be improved.
Roadmap
A visual document that outlines the planned development and strategic direction of a product over a longer period.
Roadmap
A visual document showing the strategic direction and planned milestones for a product or project.
Rolling Wave Planning
A project planning approach where planning occurs in waves, with only the next wave planned in detail.
Rolling Wave Planning
A project planning approach where planning occurs in waves, with only the next section planned in detail each time.
SAFe (Scaled Agile Framework)
A framework for scaling agile practices across large organizations or multiple teams.
SAFe (Scaled Agile Framework)
A framework for scaling agile practices for large organizations with multiple teams and projects.
Scrum
An agile framework organized into iterations and defining clear roles, events, and artifacts.
Scrum Master
A role in the Scrum framework responsible for removing impediments for the team and ensuring that Scrum practices are applied correctly.
Scrum of Scrums
A meeting in large Scrum projects where representatives from multiple Scrum teams gather to coordinate progress and dependencies.
Scrum of Scrums
A meeting designed to facilitate coordination and communication between multiple Scrum teams.
Scrum of Scrums
A meeting designed to facilitate coordination and communication between multiple Scrum teams.
Servant Leadership
A leadership approach where the leader primarily acts as a servant to their team or organization by putting the needs of others before their own.
Service Level Agreement (SLA)
A contract between a service provider and a customer, defining the expected service levels and performance standards.
Service Level Agreement (SLA)
A contract between a service provider and a customer, specifying expected performance standards and metrics.
Service Level Agreement (SLA)
A contract between a service provider and a customer, specifying expected performance standards and metrics.
Spike
A short, time-boxed investigation or experiment to gain knowledge or skills in a specific area.
Sprint
Another term for iteration, used specifically in the Scrum framework.
Sprint Goal
A short, clear statement describing the focus and objective of a sprint in Scrum.
Sprint Review
A meeting at the end of a sprint where the team presents the work accomplished during the sprint and receives feedback.
Sprint Zero
A preparatory sprint where the team takes the necessary steps to begin the actual work, such as setting up tools or clarifying requirements.
Stakeholder
Any person or group who has an interest in the outcome of a project or product.
Stakeholder Feedback Loop
A continuous process of communication and feedback between a project team and its stakeholders.
Story Points
A unit for estimating the size or effort of a user story or task.
Swimlane
A horizontal or vertical section on a Kanban board or taskboard used to organize different categories or types of tasks.
Takt Time
The rate at which a product or service must be produced to meet customer demand.
Taskboard
A physical or digital board that shows the progress of tasks or user stories during a sprint or iteration.
Technical Debt
The additional cost incurred when choosing a quick but not optimal solution that needs to be corrected later.
Test-Driven Development (TDD)
A software development technique where tests are written first before the actual code is developed.
Throughput
The amount of work that a system or process can complete in a specific period.
Timebox
A fixed period during which an activity or event must be completed.
Tracer Bullet
An approach to software development where a simple end-to-end pass is built to validate the architecture and main path.
Tracer Bullet
A development approach where a prototype or initial version of a system is created to validate the architecture and design.
Transformation Roadmap
A plan or visual representation of the steps and milestones required to execute an organizational change or transformation.
Cause-and-Effect Diagram
A diagram used to identify and analyze the potential causes of a particular problem or outcome.
User Acceptance Testing (UAT)
A testing process where end-users test the software in a real environment to ensure it meets business requirements.
User Acceptance Testing (UAT)
A testing process where end-users test the software in a real environment to ensure it meets business requirements.
User Story
A short, simple description of a requirement from the perspective of a user or customer.
Value Proposition Canvas
A tool for visualizing and defining the value proposition of a product or service and the needs of target customers.
Value Stream
The sequence of activities required to bring a product or service from concept to customer.
Value Stream Mapping
A technique for visualizing and analyzing the steps required in a process or value chain.
Velocity
A measure of how much work a team can complete in an iteration or sprint. It is often used to predict future performance.
Vertical Slice
A piece of functionality that cuts through all layers of an application, often used to demonstrate incremental delivery and continuous progress.
Vertical Slice
A software development approach where features are developed in small, complete sections or "slices" that traverse all layers of the application.
Waterfall
A traditional approach to software development where phases are executed sequentially, from requirements analysis to maintenance.
WIP (Work In Progress)
The amount of work currently being processed and not yet completed.
WIP Limit
A restriction on the amount of work that can be simultaneously in progress at a specific stage or process step in Kanban.
Work Breakdown Structure (WBS)
A hierarchical diagram showing the individual tasks or activities of a project and how they relate to each other.
Mario Lohe
General Manager with 15+ years of experience in business operations, agile transformation, and AI enablement. Former Director of Operations at Havas Creative Group, Head of Operations at Audiencly. Certified: CSPO, CSM, ISO 31000, Systemic Coach (DCA).