EXIN Agile Scrum Product Owner Bridge flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Agile Manifesto

A statement of four values and twelve principles for software development that emphasizes individuals, working software, customer collaboration, and responding to change over rigid processes and documentation.

Empiricism

The Agile and Scrum principle that knowledge comes from experience and decisions are based on observation; it relies on transparency, inspection, and adaptation to manage complex work.

Scrum values

Commitment, courage, focus, openness, and respect; these five values guide the behavior of the Scrum Team and support the empirical pillars of transparency, inspection, and adaptation.

Sprint

A fixed-length iteration of one to four weeks in Scrum that contains all other events and produces a potentially releasable Increment; its length is decided by the Scrum Team.

Definition of Done

A formal description of the quality measures required for an Increment to be considered complete; it is created and used by the Scrum Team to ensure transparency.

Product Owner accountability

The Product Owner is accountable for maximizing product value by managing the Product Backlog, communicating the Product Goal, and ensuring backlog transparency and understanding.

One Product Owner

Scrum requires exactly one Product Owner per product; the person may delegate tasks but remains solely accountable for backlog ordering and value decisions.

Product Goal

A description of a future state of the product that serves as a target for the Scrum Team; it is part of the Product Backlog and guides ordering and planning.

PO and stakeholders

The Product Owner engages stakeholders to understand needs and priorities, but the Product Owner alone decides what enters the Product Backlog and in what order.

PO availability

The Product Owner should be available to Developers during the Sprint to clarify backlog items and answer questions; unavailability can threaten the Sprint Goal and value delivery.

Product Backlog

An emergent, ordered list of everything needed to improve the product; it is the single source of work for the Scrum Team and is never complete.

Backlog refinement

The ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items; it is not a formal Scrum event and can happen anytime.

Ordering techniques

Methods such as value-based ordering, MoSCoW, weighted shortest job first, and cost of delay that help the Product Owner order backlog items to maximize value.

Definition of Ready

A shared understanding that a Product Backlog item is clear, small, and testable enough for the Developers to estimate and complete it within a Sprint; it supports Sprint Planning.

Sprint Backlog

The set of Product Backlog items selected for the Sprint, the Sprint Goal, and the plan for delivering the Increment; it is owned by the Developers.

User story

A backlog item written from the user's perspective to express value, often with acceptance criteria; it helps the Product Owner communicate needs clearly to the Developers.

Emergent backlog

The Product Backlog changes as the product and environment change; new items are added and existing items are reordered or removed to reflect current understanding and value.

Cynefin framework

A sense-making model with clear, complicated, complex, chaotic, and disorder domains; Scrum is best suited to complex work where cause and effect are only clear in retrospect.

Complexity in Scrum

Complexity comes from unknowns, dependencies, and changing requirements; Scrum addresses it through empiricism, short Sprints, and frequent inspection and adaptation.

Sprint Goal

A single objective for the Sprint that provides focus and flexibility; it is created during Sprint Planning and may be adjusted as the team learns more.

Forecasting with velocity

Using historical velocity or throughput plus the remaining backlog size to forecast when work may be done; it is a forecast, not a commitment or guarantee.

Dependencies

Relationships where one backlog item or team must wait for another; they increase complexity, so the Product Owner should make them visible and order work to reduce them.

Empirical risk management

Managing risk through transparency, inspection, and adaptation; Sprint Reviews, Increments, and Retrospectives provide frequent opportunities to inspect and adapt.

Value vs output

Value is the outcome delivered to customers and the organization, while output is the amount of work produced; the Product Owner focuses on value, not feature counts.

Maximizing value

The Product Owner maximizes value by ordering the Product Backlog so the highest-value items are worked on first, considering outcomes, risk, and learning.

Value measures

Outcome-based indicators such as customer satisfaction, revenue, cost reduction, risk reduction, and learning; they show whether the product actually delivers value.

Sprint Review

A working session at the end of the Sprint where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog; it is a key value-inspection event.

Potentially releasable Increment

A usable and useful output that meets the Definition of Done and can be released; without it, value cannot be realized by customers or the organization.

Validating assumptions

Testing beliefs about users and value with real data and feedback; the Product Owner should avoid building features that nobody uses because they do not add value.

Cost of delay

The economic impact of not delivering a backlog item sooner; it helps the Product Owner compare items and prioritize work that loses the most value over time.

Early and frequent releases

Delivering Increments to users as early and often as possible so value is realized sooner and feedback can guide the next Product Backlog ordering decisions.

Product Owner and value

The Product Owner is accountable for maximizing product value; this includes ordering the backlog, defining a measurable Product Goal, and ensuring the Increment is valuable.