THE LEARNING NOTEBOOK / AGILE & SCRUM
Learn the framework.
Practice the judgment.
Product Owner Academy
A guided path from the first principles of Agile to the everyday decisions of a Product Owner. Learn by building a case, one useful piece at a time.
A PRACTICAL RHYTHM
Read. Decide. Reflect.
Plan for 45–60 minutes per study day: 10–15 minutes reading and exploring the source, 20–30 minutes on the assignment, and 10–15 minutes checking and revising. Move at your own pace.
ONE CASE, FROM START TO FINISH
The Claim Status Tracker
Practice with a fictional FAMLI benefits-service tracker that helps people understand their claim status and next action. Build a brief, backlog, stories, acceptance criteria, roadmap, and final simulation.
Independent training. All scenarios and numbers are fictional—not actual FAMLI policy, an agency backlog, or official training. No certification or employment guarantee.
Progress and answers save automatically in this browser on this device. They are not sent to a server or synced. Clearing browser data removes them. Export a copy regularly. Use fictional information only.
This removes all 30 lessons' saved work from this browser. Export first if you want a copy.
WEEK 1 / LESSON 01
Agile is a way of learning
Agile favors close human collaboration, useful working results, customer involvement, and adapting plans as evidence changes. Processes, documentation, contracts, and plans still matter. Waterfall organizes work into successive phases; it can fit stable, well-understood work. Agile is useful when feedback may change what you should build. Neither approach excuses skipping security or compliance.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a two-paragraph response to a stakeholder requesting a new verification feature mid-project. Explain what you need to learn before deciding.
Review your work against the rubric
Identify user value; ask about urgency and risk; consult the team; explain the tradeoff and next review point.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 1 / LESSON 02
From output to outcome
An output is something delivered; an outcome is a change in people's experience or behavior. A dashboard can ship without making anyone's life easier. Begin with the problem, the people affected, and a measurable sign of improvement. A target is a hypothesis until evidence supports it. Avoid presenting invented baseline numbers as facts.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Create a problem statement, one outcome measure, and one guardrail measure. Label all assumed numbers.
Review your work against the rubric
Name the affected user; describe their difficulty; choose a baseline collection method; include a guardrail such as comprehension.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 1 / LESSON 03
Scrum in one picture
Scrum supplies a framework for learning through short cycles of work. A Product Owner, Scrum Master, and Developers work toward goals, make usable increments, and inspect results. Scrum is one approach within Agile thinking, not a synonym for Agile. A board, daily meeting, or two-week schedule alone does not establish Scrum.
Keep three artifacts straight: the Product Backlog holds the evolving product work, with the Product Goal as its commitment. The Sprint Backlog holds the Sprint Goal, selected items, and the Developers’ plan. The Increment is the usable result, measured against the Definition of Done. These commitments provide a reference point for judging progress and quality.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Sketch a cycle in words: goal → selected work → usable result → feedback → next decision. Give each step a tracker example.
Review your work against the rubric
Include a usable result and a change based on evidence, rather than just repeating meetings.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 1 / LESSON 04
Empiricism and trust
Empiricism means making decisions from observed evidence. Transparency makes the real situation visible, inspection checks it, and adaptation changes the response. The Scrum values—commitment, focus, openness, respect, and courage—help a team surface problems early. Hiding unfinished work makes future decisions less reliable.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write an honest update for a failed accessibility check. Include impact, next action, and what remains uncertain.
Review your work against the rubric
State the issue without blaming; distinguish done from unfinished; identify the decision needed.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 1 / LESSON 05
Your first product brief
A brief aligns people around a problem without prescribing every solution. Include users, their need, the intended outcome, constraints, assumptions, and exclusions. Keep the first version short enough to discuss. An assumption is something to test, not a disguised fact. Scope boundaries prevent a useful experiment from becoming an entire benefits platform.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Draft a one-page brief for the tracker. Include three assumptions and two things outside scope.
Review your work against the rubric
Connect every feature to the problem; mark assumptions; retain human support; avoid inventing real program rules.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 2 / LESSON 06
The Product Owner's decisions
Product ownership concerns value, goals, and the ordering and clarity of work. One person holds the accountability while collaborating widely. It is not a committee vote on every decision, nor permission to ignore expertise. Specialists can help write items or research needs; delegating work does not erase accountability.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a decision note choosing between clearer status wording and a new notification channel.
Review your work against the rubric
State expected value; include evidence and uncertainty; explain who you consulted and when you will revisit.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 2 / LESSON 07
Work with the whole team
The Scrum Master helps the team and organization use Scrum effectively. Developers create the usable product and determine their working plan. In Scrum, “Developers” includes the people doing the work, not only programmers. A Product Owner needs to explain needs and make tradeoffs, not learn to code or assign every technical task.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Map five decisions to Product Owner, Developers, or Scrum Master. Include ordering, technical approach, and improving team effectiveness.
Review your work against the rubric
Distinguish value decisions from implementation planning; include collaboration where useful.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 2 / LESSON 08
Listen before specifying
Discovery reduces uncertainty about the problem and possible solutions. Ask about recent behavior rather than requesting predictions about a hypothetical feature. A leading question tells people the answer you want. Include users with different access needs and those who rely on assisted service. Do not collect real claim identifiers for this exercise.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write five neutral interview questions and a short consent and privacy introduction.
Review your work against the rubric
Ask about actual experience; avoid leading phrasing; include accessibility and assisted-service needs; collect no sensitive claim data.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 2 / LESSON 09
Map the service journey
A journey map follows a person's goal through steps, touchpoints, emotions, and obstacles. It is a model to validate, not a universal story. Separate what the user sees from the internal processing behind it. This helps reveal why a technically accurate status may still leave someone stuck.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Map five journey steps with a user question and a possible failure at each.
Review your work against the rubric
Include uncertainty and recovery; avoid claiming fictional steps are actual policy; identify one research gap.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 2 / LESSON 10
Set a Product Goal
A Product Goal describes a future condition worth pursuing. It supplies direction for ordering work and judging progress. It is broader than one Sprint but specific enough to guide choices. A goal should not simply enumerate features. Avoid incompatible goals competing for the same team's attention.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write the goal, three signals of progress, and one condition that would make you reconsider it.
Review your work against the rubric
Describe a user benefit; make signals observable; include a learning checkpoint.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 3 / LESSON 11
Build a useful backlog
A Product Backlog is an evolving ordered set of work needed for the product. It can contain improvements, defects, learning work, and risk reduction. Higher items deserve enough detail to discuss soon; distant ideas need less detail. A backlog is not a promise that every request will be built.
Refinement is ongoing work to clarify and break down items; it is not a separate formal Scrum event or an approval gate. Discuss examples, dependencies, risk, and size with the people who will do the work. Developers are responsible for sizing. A local readiness checklist may help, but Scrum does not require a Definition of Ready.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Create six backlog items with user benefit, uncertainty, and evidence needed. Order them and explain the first two.
Review your work against the rubric
Include risk or quality work; avoid a list of solutions without benefits; justify the ordering.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 3 / LESSON 12
Write stories that invite discussion
A user story is a common technique, not a Scrum requirement. A helpful pattern identifies a user, a capability, and a reason. The sentence is a starting point for conversation and examples. Avoid pretending an internal database field is itself user value. A small story should produce something observable.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write three stories: status, missing documents, and notifications. For each, add a question for the team.
Review your work against the rubric
Identify a specific user and benefit; avoid implementation prescriptions; surface uncertainty.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 3 / LESSON 13
Make acceptance criteria testable
Acceptance criteria describe expected behavior for an item. They should be observable, including relevant error and edge cases. Given/When/Then is one useful format, not mandatory Scrum syntax. Criteria help a conversation; they do not replace testing, research, or the shared quality standard.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write four criteria for missing-document explanations: normal, no-action, error, and accessibility cases.
Review your work against the rubric
Make each verifiable; specify behavior rather than vague adjectives; do not invent a legal deadline.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 3 / LESSON 14
Slice value into small pieces
A vertical slice crosses the layers needed for a useful result. Splitting work into “all screens” then “all data” can delay feedback because neither slice works on its own. Reduce the range of users or scenarios while retaining end-to-end usefulness and essential safeguards. Small does not mean unsafe.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Split a large tracker feature into three usable slices. State what each excludes and what quality checks remain.
Review your work against the rubric
Each slice must help a user; preserve privacy and accessibility; identify dependencies.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 3 / LESSON 15
Order work with evidence
Prioritization considers expected benefit, urgency, effort, uncertainty, risk, and dependencies. A scoring method can reveal assumptions but cannot make the decision for you. Estimate inputs honestly and revisit them. Urgent safety or legal concerns may outweigh a simple value-to-effort ranking.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Rank status clarity, document explanations, notifications, and estimates. Explain your assumptions, one dependency, and one item you would postpone.
Review your work against the rubric
Use more than popularity; acknowledge uncertainty; explain the opportunity cost.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 4 / LESSON 16
Plan toward a Sprint Goal
Sprint Planning connects a valuable objective, selected work, and a plan to create it. The team develops the Sprint Goal; Developers select what they can accomplish through discussion with the Product Owner. Historical evidence and available capacity inform a forecast. A goal offers coherence beyond completing an arbitrary pile of tickets.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Propose a Sprint Goal, three supporting items, and a capacity assumption. Explain the item you leave out.
Review your work against the rubric
Describe a coherent benefit; allow room for uncertainty; avoid imposing a workload on the team.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 4 / LESSON 17
Handle change during a Sprint
A Sprint is a timeboxed cycle of one month or less. Learning can change the plan, but changes should not endanger the Sprint Goal and quality should not decrease. The Product Owner and Developers discuss scope as more is learned. Only the Product Owner can cancel a Sprint if its goal becomes obsolete.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a response to the SMS request with a question, a tradeoff, and a decision path. Add what you would do if the goal became obsolete.
Review your work against the rubric
Protect the goal and quality; collaborate on scope; distinguish a request from an emergency.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 4 / LESSON 18
Use the Daily Scrum well
The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan. It is not a status presentation to a manager. There is no mandatory three-question script. Other detailed discussions can happen afterward. A Product Owner participates as a Developer when actively working on Sprint Backlog items.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Turn a status update into a planning conversation: risk to goal, next action, and needed collaboration.
Review your work against the rubric
Focus on the shared goal; make the plan actionable; move detailed problem-solving into follow-up.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 4 / LESSON 19
Know what Done means
The Definition of Done is the shared quality standard for an Increment. Acceptance criteria apply to a particular item; Done describes the quality required across the work. An item that fails Done is unfinished, even if its happy-path demo works. A usable Increment can be delivered before the Sprint ends; the Review is not a release gate.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Draft a five-point quality checklist and contrast it with two item-specific acceptance criteria.
Review your work against the rubric
Include appropriate testing, accessibility, privacy, and operational readiness; distinguish shared quality from feature behavior.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 4 / LESSON 20
Review the product; improve the process
The Sprint Review is a working conversation with stakeholders about the outcome and what to do next. The Retrospective examines how the team worked and selects improvements. A demo alone is not the whole Review; a complaint session alone is not a useful Retrospective. Turn observations into decisions and experiments.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a Review agenda and a Retrospective experiment with an owner, measure, and review date.
Review your work against the rubric
Keep product feedback separate from process learning; specify an actionable improvement.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 5 / LESSON 21
Make a roadmap about outcomes
A roadmap communicates direction and uncertainty. A now/next/later format can describe intended outcomes without pretending every date is guaranteed. Fixed external commitments still need explicit planning and risk discussion. Revisit the roadmap when evidence changes. A roadmap is not the same as an ordered backlog.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Create a now/next/later roadmap with an outcome, assumption, and evidence checkpoint in each horizon.
Review your work against the rubric
Use outcomes; mark uncertainty; explain what could change the sequence.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 5 / LESSON 22
Forecast without false precision
A forecast is an evidence-based expectation with uncertainty. Estimates support decisions; they are not guarantees or personal productivity scores. Story points and velocity are optional practices, not Scrum requirements. Do not compare teams using their point totals. Discuss ranges, assumptions, dependencies, and what could change.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a stakeholder forecast with a range, assumptions, risks, and the next update date.
Review your work against the rubric
Avoid a guarantee; name the dependency; explain what evidence will narrow uncertainty.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 5 / LESSON 23
Negotiate stakeholder tradeoffs
Stakeholders have legitimate but competing interests. Understand the need behind a request, explain the current goal, and make the cost of choosing visible. A reasoned “not yet” should include when the idea will be revisited. Do not use a scoring spreadsheet to avoid responsibility for a difficult decision.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Draft a concise “not yet” message: acknowledge the need, explain evidence, offer a next step.
Review your work against the rubric
Respect the stakeholder; avoid invented promises; name the learning needed to reconsider.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 5 / LESSON 24
Build accessibility and privacy in
Accessible and privacy-conscious experiences require early collaboration and verification. Clear language, keyboard access, meaningful errors, and minimal data exposure support more people. Ask appropriate specialists about applicable requirements; a practice course cannot determine real agency obligations. Quality is part of useful delivery, not a decorative final phase.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a notification and identify three accessibility or privacy questions to review before delivery.
Review your work against the rubric
Minimize sensitive content; include a clear next action; specify how keyboard and assistive-technology use will be checked.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 5 / LESSON 25
Measure whether the product helped
Use a small set of outcome and guardrail measures. Compare like periods and populations; changes can have causes beyond your feature. Pair numbers with qualitative feedback. Avoid claiming causation from one before/after chart. Fewer support calls could signal improvement, a seasonal change, or an inaccessible support route.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Design a measurement plan: baseline, pilot population, outcome, guardrail, and review decision.
Review your work against the rubric
Include a denominator and collection method; consider alternate explanations; keep help available.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 6 / LESSON 26
Simulation: choose the first slice
You are the Product Owner for the fictional Claim Status Tracker. Research suggests unclear status and document requests drive repeat calls. The team can deliver one narrow usable path, not all four candidate features. Treat estimates as assumptions. Your goal is to reduce uncertainty for claimants while protecting quality.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a decision memo choosing a first slice and deferring the others. Include a Product Goal, evidence, risk, and success measure.
Review your work against the rubric
Choose a useful feasible slice; explain opportunity cost; preserve quality; distinguish known facts from scenario assumptions.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 6 / LESSON 27
Simulation: prepare the Sprint
Carry the decision into a coherent Sprint proposal. Write stories and criteria, surface dependencies, and discuss capacity with Developers. You propose value and clarify needs; you do not force a task count. Make sure the goal still makes sense if one lower-priority item is dropped.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Create three stories, two criteria each, a Sprint Goal, a draft Definition of Done, and a dependency note.
Review your work against the rubric
Make criteria observable; keep the goal coherent; include error handling and quality; treat selection as a team conversation.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 6 / LESSON 28
Simulation: respond to disruption
Halfway through the fictional Sprint, a new request arrives for SMS updates. At the same time, testing finds that one status label incorrectly suggests a claimant must act. Distinguish a new opportunity from a defect that threatens the current goal. Ask for evidence before making a commitment.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Write a decision log for both issues: impact, consultation, decision, scope tradeoff, and stakeholder update.
Review your work against the rubric
Address misleading wording; protect quality; collaborate on the plan; record SMS as an evaluated option.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 6 / LESSON 29
Simulation: inspect the pilot
The fictional pilot includes 20 participants: 15 correctly explain their next action; 5 misread “in review.” Two keyboard users encounter a focus problem. These invented observations are learning material, not real program data. Do not declare success just because most users completed the task.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Prepare a Review summary with findings, limitations, two backlog changes, and one Retrospective experiment.
Review your work against the rubric
Use the actual scenario counts; do not hide failures; distinguish product changes from a process experiment.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
WEEK 6 / LESSON 30
Bring the work together
A useful portfolio shows how you think: the problem you framed, the evidence you sought, the options you weighed, and what changed after feedback. Explain decisions in plain language. You do not need programming expertise to demonstrate responsible product ownership. This course is practice, not certification or a guarantee of employment.
YOUR ASSIGNMENT · 20–30 MINUTES
Put it into practice.
Assemble your final case study. Give a three-minute walkthrough and write a reflection: what changed, why, and what you would learn next.
Review your work against the rubric
Show the chain from problem to evidence to decision; identify uncertainties; demonstrate collaboration; select one skill for further practice.
This is a self-assessment. Your writing is not graded by AI. Revise until you can explain your choices.
Complete the assignment, review it, and pass the check to finish this lesson.
GO TO THE SOURCE
A small, reliable reading shelf.
Use these alongside the lessons. The Scrum Guide defines the framework; story formats, roadmaps, and the exercises here are practical techniques.