EXIN Agile Business Professional key terms

A way of thinking that values people, collaboration, adaptation and early delivery of value over rigid plans and documentation. It shapes how decisions are made daily, not just which ceremonies are run.

The four preference statements from the Agile Manifesto: individuals and interactions, working software, customer collaboration and responding to change. They describe priorities when trade-offs arise, not absolute rules.

Twelve guiding statements that translate Agile values into behaviour, such as delivering frequently, welcoming changing requirements, self-organizing teams and reflecting regularly. They inform practices but do not prescribe a specific method.

A management approach for complex work based on transparency, inspection and adaptation. Decisions rely on observed results rather than prediction, because too many variables exist to plan everything upfront.

A recurring cycle in which a team reviews its product, process and collaboration, then changes something based on what it learned. Without adaptation, inspection adds no value.

The belief that ability and intelligence can be developed through effort, feedback and practice. In Agile settings it supports experimentation, honest retrospectives and treating failure as learning data.

A situation where cause and effect are only clear in hindsight and many independent factors interact. Agile approaches suit complex work because they shorten feedback loops instead of attempting full prediction.

A sense-making model that distinguishes clear, complicated, complex and chaotic situations, each needing a different response. It helps leaders avoid applying plan-driven methods to genuinely complex problems.

A fixed, short timebox in which a team delivers a usable increment of value and then reviews it. Iterations create rhythm and limit work in progress so learning happens frequently.

The tangible, potentially releasable output produced during an iteration. Each increment should add value on its own and be complete enough to gather real feedback.

A leadership style in which the leader's primary aim is to remove obstacles and develop people, rather than to direct tasks. Authority is used to enable the team's autonomy and growth.

A manager who shapes environment, boundaries and purpose instead of assigning detailed work. This person protects the team, connects it to business strategy and models the behaviours the organization wants to spread.

Shared norms and habits in which transparency, collaboration, experimentation and customer focus are normal practice. Culture is visible in what people are rewarded, tolerated and punished for, not in slogans.

A team climate in which people can raise problems, admit mistakes and challenge decisions without fear of humiliation. It is a precondition for honest retrospectives and fast learning.

A group that decides for itself how to divide and sequence its work within agreed boundaries. Management sets goals and constraints; the team chooses the approach.

A team holding all the skills needed to deliver an increment without depending on outside hand-offs. This shortens feedback loops and reduces waiting time.

A person with deep expertise in one discipline plus broad, working knowledge of adjacent disciplines. Such breadth lets teams cover gaps and collaborate across roles.

Giving people real authority to make decisions about their work, together with the information and skills to decide well. Empowerment without clear boundaries becomes confusion.

Designing and guiding a group process so participants reach their own outcomes. The facilitator manages the how of the conversation and stays neutral on the content.

A recurring team meeting to inspect how work was done and agree on concrete improvements. Its output is a small number of owned actions, not a list of complaints.

A set of simple group formats, such as 1-2-4-All or What-So-What-Now-What, that include everyone in shaping decisions. They are used to make meetings more participative and less dominated by senior voices.

The worth an outcome delivers to the organization and its customers, expressed through revenue, cost, risk reduction, compliance or satisfaction. It is judged by results, not by volume of delivered features.

The sequence of activities from a customer need to delivered value, including waiting time and hand-offs. Mapping it reveals delays and waste that local team optimization hides.

Deciding what to do first based on expected value, risk, effort and dependencies. Good prioritization makes trade-offs explicit and is revisited as new information arrives.

A prioritization technique sorting requirements into Must have, Should have, Could have and Will not have this time. The Must category is kept deliberately small to protect delivery options.

A sequencing rule that ranks work by cost of delay divided by job duration, so short high-value items go first. It maximizes economic return rather than pleasing the loudest stakeholder.

The economic loss caused by not delivering something sooner, expressed as money per unit of time. Making it visible turns scheduling debates into business discussions.

The smallest version of a product that allows a real test of the core hypothesis with real users. Its purpose is validated learning, not a cheap release.

A learning loop in which a team builds something small, measures actual user response and decides whether to persevere or pivot. The loop is run as fast as possible.

A structured change of strategy based on evidence, while keeping what has been learned. It differs from abandoning a product or repeating the same approach.

A shared checklist describing what complete means for an increment, such as tested, documented and integrated. It prevents hidden work and makes quality transparent.

The future cost of shortcuts taken in design or code that make later change slower. It is a business concern because it erodes the ability to respond to new opportunities.

The smooth movement of work through a system with minimal waiting, rework and hand-offs. Flow is measured with cycle time and work in progress rather than utilization.

Activity that consumes effort or time without adding customer value, such as waiting, rework, overproduction or unnecessary hand-offs. Lean thinking targets waste before adding capacity.

A method for visualizing work, limiting work in progress and managing flow on a board with explicit policies. It supports continuous change without requiring fixed iterations.

A cap on how many items may be in a given stage at once. It exposes bottlenecks, reduces multitasking and shortens cycle time.

Extending Agile practices and mindset across multiple teams or the whole enterprise while keeping local autonomy. It addresses coordination, architecture and funding rather than merely copying ceremonies.

A deliberate, long-term shift in structure, processes, metrics and behaviour toward customer-focused, adaptive working. It is a change programme with risks and resistance, not a one-off training event.

The structured work of preparing, supporting and embedding organizational change, including stakeholder engagement and resistance handling. In Agile contexts it emphasizes participation over top-down rollout.

A change model moving from urgency and coalition building through vision, short-term wins and anchoring new approaches in culture. It is often used to structure Agile adoption programmes.

Voluntary groups of practitioners who share knowledge across team boundaries, for example testers or Scrum Masters. They spread standards and support without adding reporting lines.

Managing investment across initiatives using light business cases, continuous funding and regular review of value. It replaces annual fixed budgets that lock priorities in place.

An ongoing habit of acquiring and sharing knowledge through practice, feedback and reflection. It sustains Agile capability after initial training fades.

Working at a level of intensity that can be maintained indefinitely without burnout or quality loss. It treats long-term capability as more valuable than short bursts of overtime.

Leaders demonstrating the behaviours they expect, such as transparency, admitting error and respecting team decisions. Visible inconsistency between words and actions stalls adoption.

A facilitated technique in which a group agrees the level of authority for specific decisions, from telling to full delegation. It makes expectations explicit and reduces later friction.