Product ownership: responsibilities and practical exercise
The Product Owner clarifies intended value and the ordering of work. In Scrum, this role is accountable for maximising product value and effective Product Backlog management. Decisions stay tied to an explicit goal and available feedback rather than the number of requested features.
These sheets describe activities and teaching exercises. They do not constitute job offers, certifying courses or recruitment promises.
Clarify the product goal and order work by expected value. In Scrum, the Product Owner is accountable for maximising product value and effective Product Backlog management.
Typical activities
Formulate a product goal and understandable backlog items.
Order needs with constraints, impact and outcome criteria.
Use feedback on increments to adjust decisions.
Responsibilities to agree with the team
The Product Owner is not a committee or merely a ticket writer. Organisational obligations remain with their owners; developers organise implementation within the agreed framework.
A first piece of work to demonstrate
Present a short backlog whose order follows a goal, observations and explicit pending decisions.
This is an editorial description of common activities. Job titles and scope vary across teams; it is not a certification framework.
Prioritize a catalog evolution between search, filters and comparison.
Work on a copy or demo environment. Define the data used and the expected result before you begin. Keep your decisions and the difficulties encountered in order to be able to explain the process.
Describe the problem and the expected value of each request.
Cut into usable and testable elements.
Explain the acceptance criteria with the team.
Revise the order after return of use and explain the arbitrations.
Deliverable and checks
Present the catalogue goal, needs behind search, filters and comparison, and their reasoned order. For one initial item, provide scope and observable criteria. Also retain a deferred need with its rationale and evidence that could trigger reconsideration.
The team should explain the need served by the first item and check its criteria without guessing a rule. Test the response to a new constraint or contradictory feedback. Ordering may change, but its rationale and the goal should remain understandable.
A feature list is not a product policy. Priorities should be related to explicit needs and constraints.
Collaboration to explore: product design.
Fictional deliverable excerpt : A slot request is prioritised before instant confirmation because actual availability still needs to be established with the people concerned.
What passes between the roles : Product choices and delivery constraints are discussed with the team. In this example, priority and dependency are separate pieces of information; neither supports promising an unconfirmed date or feature.
Fictional teaching material: this excerpt illustrates part of a deliverable. It is not a client reference, a complete specification or evidence of professional qualification.
Sample excerpt
Need: restore the complete list after filtering.
Given: a list displaying a subset.
When: the person activates “Clear filter”.
Then: the field is empty and all items are visible.
And: the result count matches the complete list.
What the author should be able to explain
The criterion describes an observable outcome rather than prescribing technology.
The starting state and action leave no missing step to guess.
Additional cases, including no results, still need specification.
Does this criterion describe the entire search function?
It covers only restoration of the complete list. Initial search, special characters, empty results and possible errors need their own criteria. One successful example does not complete the whole function.
Assess the quality of the work
Within Scrum, examine how the Product Owner makes the objective and Product Backlog ordering understandable. For the exercise, an urgent request competes with an already prioritized item. The deliverable should explain expected value and missing information without turning that accountability into detailed instructions for how Developers perform the work.
Scroll the table horizontally to read every column. With a keyboard, focus the table area and use the arrow keys.
Assess the quality of the work
Skill
Evidence to examine
Failure to spot
Product Goal and choices
Connect possible items with an explicit product objective. Identify the expected outcome, need addressed and remaining learning before committing more work.
A wish list substitutes for an objective, or every request is called essential without explaining its contribution to the product.
Ordered backlog
Present understandable ordering and its rationale: expected value, dependencies or uncertainty. Make items sufficiently transparent for discussion.
Every item has the same priority, or the accountable person prescribes a detailed solution without letting Developers organize implementation.
Transparency
Items are visible and understood enough to discuss the work.
The team discovers expectations only after implementation.
Ordering work
Explain expected value, dependencies and observable outcome for a priority item.
The team can understand why it comes before another; criteria describe the need without unnecessarily prescribing the solution.
A focused next step
Compare two fictional items, one addressing urgency and another the existing objective. Explain the consequences of their order and information that might change it. Distinguish that decision from implementation methods; outside Scrum, specify the role’s actual responsibilities rather than relying on its title.
A WordPress content export can include posts, pages, post types, comments, custom fields and taxonomies. Its scope depends on selected filters. Check media files, theme, plugins and configuration separately before treating it as a complete migration.
Dates indicate when references were consulted. These facts are neither a site audit nor an overall compliance statement.
A review case to reproduce
Done without an examinable outcome
Situation to examine
A backlog item is marked done but describes only a feature. The team cannot connect it to an expected result or product decision.
Proposed check
Clarify objective, scope and evidence used to examine results. Distinguish item conditions from the Scrum team’s Definition of Done. Discuss findings without inventing unobserved usage success.
Evidence to retain
The item connects need, expected outcome, delivered work and limitations. Priority decisions can be explained using available information.
Fictional finding example
Item DEMO-P1 says “Add a filter”. Code is delivered, but no expected visitor outcome or usability check is described.
Interpret this outcome
Specify the task it should support and possible checks. Separate the Definition of Done from evidence of an observed benefit; the Product Owner cannot invent that evidence.
Three complementary checks
Fictional cases: adapt these expectations to your test contract and retain the limits of the check.
1Explicit expectation
2Examined quality
3Distinct benefit
Scroll the table horizontally if needed; with a keyboard, focus it and use the arrow keys.
Scenario variations and expected evidence
Variation to test
Expected result in this case
Evidence to hand over
A criterion passes but the Definition of Done fails
Do not count this work in the Scrum Increment
Tested criterion and unmet quality requirement
The Definition of Done is met
Distinguish completion from observed user benefit
Quality evidence and still-missing measurement
A new expectation appears
Clarify and prioritise the additional need
New request and backlog decision
Decision to hand over : Record test result, Definition of Done compliance and actually observed benefit separately.
Extended exercise: Prepare a backlog to improve research in a demo directory. Describe uses before cutting tasks. Compare an improvement in labels, a correction of an empty state and a new filter option. Prioritize with explicit assumptions about utility and effort. Each element selected must be clear enough for the team to discuss its expected result without having to invent the context.
What to deliver with your work
Problem and users concerned
Backlog elements with context and expectations
Prioritization with hypotheses and dependencies
Demonstration scenarios and acceptance criteria
Acceptance criteria
These criteria are a working basis to adapt to the context. For each, note the action taken, the expected result, the observed result and the information remaining to be confirmed.
An element describes an observable result in the course.
The criteria also specify empty states or relevant errors.
Priority has a justification the team can discuss.
The demonstration resumes the expectations defined before completion.
Transmit the selected elements with their reasons and dependencies. Keep unresolved questions so that they do not become implicit decisions during completion. Re-examine the priority when a hypothesis changes or a significant defect appears. Closing an item should be based on a result check, not just that its technical tasks are complete.
A priority connects a need to an expected result. Compare a requested feature with a problem described by its consequences before choosing the next work.
Clarification of a request
When to choose it
Useful when a stakeholder already proposes a solution. Identify the task, audience and constraint behind the request.
What to plan for
Compare alternatives. Frequent requests in discussions do not necessarily represent the whole audience.
Prioritisation of an observed problem
When to choose it
Suitable when observations show concrete impact. Define a verifiable outcome and a scope that supports learning.
What to plan for
Specify acceptance criteria and risks. Interpret indicators alongside potential effects on other workflows.
A risk to anticipate
Adding items to a list does not make them ready for implementation. Keep missing information and dependencies visible before committing.
How to decide
Explain priority decisions and postponements. The expected result supports later discussion of the effect achieved, even if the solution changes.
Compare covered problems, acceptance criteria and dependencies. A backlog of titles differs from understandable, testable and ordered work items.
Recurring operation
Specify priority upkeep and feedback handling. Separate decisions from implementation; adding a request guarantees neither delivery nor acceptance.
Exit and handover
Request choice rationale, criteria and unresolved issues. The next team should change priorities with dependency knowledge, not treat a list as an automatic commitment.
How can a backlog item support a useful discussion?
Describe the person concerned, the need and an observable result. Add constraints and open questions, then discuss them with the people building and checking the outcome. A list of screens or technical title alone does not explain why the item deserves priority.
How can two priorities be compared without false scoring precision?
Explain the need addressed, available evidence, dependencies and consequences of delay. Distinguish estimates from established facts. A score may support discussion, but keep the rationale and decision explicit so they can be revisited when context changes.
What if two priorities seem equally important?
Compare audiences, consequences of postponement, dependencies and available evidence. If uncertainty remains high, choose a limited investigation. Document the compromise so priorities can be reconsidered when new information appears.