EXIN Agile Scrum Product Owner Bridge cheat sheet

Agile Manifesto (Kanban/Scrum history): values are Individuals and interactions over processes and tools; Working software over comprehensive documentation; Customer collaboration over contract negotiation; Responding to change over following a plan.

Agile is iterative, incremental, and adaptive; empiricism rests on transparency, inspection, and adaptation.

Scrum pillars: transparency, inspection, adaptation; the five Scrum values are commitment, courage, focus, openness, and respect.

Scrum is a lightweight framework for complex product delivery; it is not a methodology or a process.

The three Scrum accountabilities are Product Owner, Scrum Master, and Developers; the Scrum Team is self-managing and cross-functional.

Sprint length is fixed at 1–4 weeks; shorter sprints increase feedback frequency and reduce risk.

The Sprint is the container for all other events: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product; it is created by the Scrum Team.

Product Owner is accountable for maximizing product value; Scrum Master is accountable for the Scrum Team's effectiveness; Developers are accountable for creating the Increment.

The Product Owner is one person, not a committee; the PO may delegate work but remains accountable.

PO accountability includes: developing and explicitly communicating the Product Goal; creating and clearly communicating Product Backlog items; ordering the Product Backlog; and ensuring the Product Backlog is transparent, visible, and understood.

The PO is the sole person accountable for Product Backlog management; others may influence the backlog but the PO decides ordering.

The PO must be empowered to make decisions; lack of authority is a common anti-pattern that blocks value delivery.

The PO participates in Sprint Planning, Sprint Review, and refinement; the PO need not attend the Daily Scrum unless needed by Developers.

The PO is not a project manager, team lead, or business analyst by default; the role focuses on value and backlog decisions.

Stakeholder management: the PO engages stakeholders to understand needs, but the PO alone decides what enters the Product Backlog and in what order.

The PO should be available to the Developers during the Sprint to clarify items and answer questions; unavailability is a risk to the Sprint Goal.

In scaled settings, the PO may work with other POs or stakeholders, but each product has one accountable PO for backlog ordering.

The Product Backlog is an emergent, ordered list of what is needed to improve the product; it is the single source of work for the Scrum Team.

Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller, more precise items; it is an ongoing activity, not a formal Scrum event.

The Product Goal describes a future state of the product that can serve as a target for the Scrum Team to plan against; it is in the Product Backlog.

Ordering techniques include value-based ordering, MoSCoW, weighted shortest job first (WSJF), and cost of delay; the PO decides the ordering.

A Product Backlog item is ready for Sprint Planning when it is small enough and clear enough for the Developers to estimate and complete within a Sprint; this is often called Definition of Ready.

The PO orders the backlog to maximize value; ordering may consider risk, dependencies, learning, and stakeholder needs, not only financial value.

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

Backlog items should be written to express user or customer value, often as user stories with acceptance criteria; the PO ensures clarity.

The Product Backlog is never complete; it evolves as the product and environment change.

Complexity arises from unknowns, dependencies, and changing requirements; Scrum addresses complexity through empiricism and short feedback loops.

Cynefin framework domains: clear, complicated, complex, chaotic, and disorder; Scrum is best suited to the complex domain.

In complex work, cause and effect are only visible in retrospect; therefore, plan in small increments and inspect frequently.

Sprint Goal provides focus and flexibility; it is a single objective for the Sprint and may be adjusted as more is learned.

Emergent work is expected; the PO may refine and reorder the Product Backlog as new information appears, but scope changes within a Sprint are negotiated with the Developers.

Dependencies across teams or components increase complexity; the PO should make them visible and order work to reduce them.

Risk management in Scrum is empirical: use Sprint Reviews, Increments, and Retrospectives to inspect and adapt.

Forecasting uses velocity or throughput history plus remaining backlog size; it is a forecast, not a commitment.

The PO should avoid prescribing detailed solutions; the Developers decide how to build the Increment.

Value is the outcome delivered to customers and the organization; it is not the same as output or number of features.

The PO maximizes value by ordering the Product Backlog and ensuring the team works on the highest-value items first.

Value can be measured with outcomes such as customer satisfaction, revenue, cost reduction, risk reduction, and learning.

The Product Goal aligns the team and stakeholders on the value to be delivered; it should be measurable and time-bound where possible.

The Sprint Review is a working session to inspect the Increment and adapt the Product Backlog; it is a key value-inspection event.

Definition of Done ensures the Increment is potentially releasable; without it, value cannot be realized.

The PO should validate assumptions with real users and data; building features nobody uses does not add value.

Prioritization should consider cost of delay and opportunity cost; the highest value may be learning or risk reduction.

Value delivery is continuous; the PO should seek early and frequent releases to realize value sooner.