Career studio / Scrum
Build evidence for the Associate Product Owner role
A library app receives requests from staff, readers and the sponsor. The team can deliver only three small increments before a community event. Build a backlog tied to user value and acceptance evidence.
Your outcome: Outcome-led backlog, release slice and acceptance examples.
Table of Contents
Start with the right expectations
Who this is for
Basic delivery-team experience and the ability to interview a stakeholder.
This path develops a demonstrable work sample for the named role. It does not replace employer-specific experience, professional qualifications or supervised practice.
Plan your study time
Use a flexible six-week project schedule: one week for each of the first four stages and two weeks for the portfolio and review. Allow roughly 3–5 hours per week for the case work, in addition to course study. This is a planning suggestion, not a measured course duration or a promise of job readiness.
Read the course access notes before starting. Free viewing or reading does not automatically include certificates, graded assessments, software licences or paid cloud resources. Core case work can be documented with a free editor and spreadsheet; optional implementation tools may have additional requirements.
Your course sequence
Start in the order below. Use the course outline to select the sections relevant to the stage tasks, and complete foundation exercises before moving on. Full provider courses can be substantially longer than this project schedule. These are course resources, not a claimed count of individual lessons.
Resource 01 / Google
Free Project Management Course by Google
Purpose: Build the foundations. Connect your notes to the case tasks below rather than only collecting completion marks.
Access: Free Video
Certificate: Free video viewing; a Google certificate is not included
Resource 02 / Scrum.org
Definition of Done in Scrum: Free Course
Purpose: Develop the role-specific method. Connect your notes to the case tasks below rather than only collecting completion marks.
- Explain how a Definition of Done makes the quality and completeness of an Increment transparent, so that a team can discuss finished work using shared expectations.
- Distinguish the product-wide Definition of Done from acceptance criteria for an individual Product Backlog item, and recognise why satisfying one does not automatically satisfy the other.
- Examine the difference between technical debt and work that does not meet the Definition of Done, rather than treating every unfinished quality activity as the same problem.
Access: Free Video
Certificate: Free video viewing; certificate not included
Resource 03 / Simplilearn
Free Simplilearn Course: Business Analysis and CBAP Concepts
Purpose: Strengthen practical application. Connect your notes to the case tasks below rather than only collecting completion marks.
- Explore business-analysis concepts, planning the analysis approach and selected BABOK/CBAP-related explanations.
- Follow the selected explanations of Analysis Planning, Requirements and Stakeholders.
- Connect concepts to lessons such as An Introduction to CBAP — CBAP Based on BABOK Guide — CBAP Training Online.
Access: Free Video
Certificate: Free video viewing; Simplilearn certificate not included
Learn, make, check
Keep a decision log as you work. For each stage, capture the assumption, your work product, a check and the change you made after that check. The acceptance criterion is the stopping condition for the stage.
Stage 1 / suggested project week 1
Discover the outcome
Understand: A feature request is a hypothesis about value.
Make: Write three user problems and the evidence you would collect before committing to a solution.
Check before moving on: Separate observed problems from stakeholder preferences.
Study companion: Free Project Management Course by Google. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 2 / suggested project week 2
Slice the backlog
Understand: A small vertical slice delivers a usable result.
Make: Rewrite six requests as small backlog items with acceptance examples and dependencies.
Check before moving on: Each selected item can be demonstrated to a user.
Study companion: Definition of Done in Scrum: Free Course. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 3 / suggested project week 3
Order transparently
Understand: Priority is a decision under constraints.
Make: Order the first release using value, uncertainty, effort and dependencies; explain why two items wait.
Check before moving on: Do not treat a numerical score as an automatic decision.
Study companion: Free Simplilearn Course: Business Analysis and CBAP Concepts. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 4 / suggested project week 4
Review and adapt
Understand: A review tests outcomes as well as implementation.
Make: Design a demonstration and feedback plan; record what feedback would change the next backlog order.
Check before moving on: Define who accepts the result and how unmet criteria are handled.
Study companion: Free Simplilearn Course: Business Analysis and CBAP Concepts. Use its relevant lessons and examples; the independent Coursya task is not a provider assessment.
Save as evidence: a dated work product and a short note explaining one choice, one alternative and one remaining uncertainty.
Stage 5 / suggested project weeks 5–6
Present your portfolio
Assemble the four work products into Outcome-led backlog, release slice and acceptance examples. Write a README explaining the problem, your assumptions, the decisions you made, tests actually performed and what remains incomplete.
Give a five-minute walkthrough: one minute for the problem, two for the work and evidence, one for trade-offs and one for the next improvement. If you have not implemented a proposed system, label it a design or prototype rather than a deployed solution.
Acceptance: a reviewer can locate each work product, reproduce the key reasoning and identify the limits without a private explanation from you.

The portfolio brief
A library app receives requests from staff, readers and the sponsor. The team can deliver only three small increments before a community event. Build a backlog tied to user value and acceptance evidence.
Deliver: Outcome-led backlog, release slice and acceptance examples.
| request | value 1 to 5 | effort points | dependency |
|---|---|---|---|
| Search books | 5 | 3 | |
| Reserve available book | 5 | 5 | Reader identity |
| Reader identity | 3 | 3 | |
| Color themes | 1 | 2 | |
| Reservation status | 4 | 3 | Reserve available book |
| Staff export | 2 | 5 | Reservation status |
Use these small inputs to make the reasoning visible. They are not a representative dataset, a real client engagement or evidence of production performance. Where the brief requires additional sample records, create them yourself, label them synthetic and explain why you added them.
The ZIP includes the case CSV, four stage worksheets, course sequence, decision log, test log, portfolio README template, review rubric and reference reasoning. It is a starter kit for your work, not a completed application, professional report or proprietary project file.
Check your reasoning
A highly scored item depends on an unfinished identity step. Should its score override the dependency?
Write your answer and assumptions before opening the reference.
Read the reference reasoning
No. Re-slice the item, deliver the dependency, or defer it. Record why the score alone does not make the item immediately deliverable.
Portfolio review rubric
| Criterion | Points | Evidence required |
|---|---|---|
| Problem and scope | 4 | A clear user, need, boundary and assumptions |
| Role-specific work | 8 | 2 points for each of the four stage acceptance checks |
| Reasoning and validation | 4 | Independent checks, actual results and uncertainty |
| Communication and reproducibility | 4 | A usable README, source links and reviewable work products |
Aim for at least 16/20 as a self-review target, with no missing stage acceptance check. This is a Coursya practice rubric, not an industry credential or a hiring assessment.
Interview practice
Explain one feature you deliberately left out and the user outcome you protected.
Answer using the case: context, your action, evidence and limitation. Describe this honestly as a self-directed project. Do not present fictional organizations, invented interviews or practice results as paid work experience.
Your progress
Use this checklist as a personal study aid. Progress is stored in this browser when local storage is available; it is not an account record or a certificate.
0 of 5 milestones complete
The lessons and projects remain readable without JavaScript. Automatic progress saving requires JavaScript.
Questions before you start
Will this path qualify me for a job?
It helps you study relevant foundations and produce a work sample. Employers may require additional skills, qualifications and experience. Review actual role requirements before applying; no job or certification is guaranteed.
Are all tools and certificates free?
The linked learning routes were selected for free viewing or reading. Follow the separate access and certificate notes on each course. Paid tools and cloud deployment are optional; document a local design when implementation resources are unavailable.
Can I follow this on a phone?
You can read the path and many learning resources on a phone. Coding, detailed spreadsheet work, design tools and mobile-app development are easier or require a suitable computer. The page is designed to reflow; that is not a claim that every physical device has been tested.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.