PSPO I study plan
PSPO I · Give each week a clear focus.
8 weeks · About 7 hours per week
Scrum Theory and Empiricism
Define empiricism, transparency, inspection and adaptation in your own words without notes
Explain how the three Scrum pillars enable each other and what breaks when one is missing
Contrast Scrum's empirical approach with a predictive/waterfall approach for a product with high uncertainty
Identify the five Scrum values and describe one observable behaviour that demonstrates each in a team
Your checkpoint
A one-page written summary explaining the three pillars, the five values and two concrete examples of inspection-and-adaptation failure, self-graded against a checklist of 8 key concepts (target: 8/8 without notes).
Scrum Theory and Empiricism & The Scrum Framework and Accountabilities
Map each Scrum event to the pillar(s) it primarily serves and justify the mapping
Sequence the five events within a Sprint and state the purpose, timebox and participants of each
Explain why the Sprint itself is an event that contains the others
Describe how the Sprint Goal creates focus and flexibility and give an example of scope renegotiation that preserves it
Your checkpoint
A hand-drawn or text-based diagram of one Sprint showing all five events with purpose, timebox and participants annotated, plus a 150-word explanation of the Sprint Goal's role.
The Scrum Framework and Accountabilities
Distinguish the accountabilities of Product Owner, Scrum Master and Developers and list what each is accountable for
Explain what 'self-managing' and 'cross-functional' mean for Developers and what they do not mean
Describe how the Scrum Master serves the team, the Product Owner and the organisation differently
Diagnose three short written scenarios and name which accountability is being neglected and why
Your checkpoint
A three-column accountability matrix (Product Owner / Scrum Master / Developers) covering 12 responsibilities with correct placement, plus written diagnoses of 3 scenarios.
The Scrum Framework and Accountabilities & Product Backlog Management
Differentiate the product backlog, Sprint Backlog and product goal in terms of ownership and commitment
Explain how backlog refinement is an ongoing activity rather than a scheduled event
Write three backlog items that each express value rather than a technical task
Describe how the Developers select work for a Sprint Backlog and what commitment it carries
Your checkpoint
A sample backlog of 10 items with an accompanying product goal statement, a Sprint Goal derived from it, and a short written justification of the ordering logic.
Product Backlog Management
Order a set of backlog items by value, risk and dependency and defend the order in writing
Explain how backlog items are sized, split and made transparent enough to start work
Distinguish outcome-oriented goals from output-oriented task lists in backlog formulation
Describe how the Product Owner uses the backlog to maximise value and manage stakeholder expectations
Your checkpoint
A re-ranked backlog of 15 items with a one-line rationale for each position and at least 3 examples of items you split into smaller, value-bearing pieces.
Product Ownership and Delivering Value
Explain how a Product Owner maximises value across the whole product, not just the next Sprint
Describe at least four ways to measure whether a product increment delivered value
Contrast delivering value early and often with delivering everything at the end, using a concrete example
Identify the trade-offs a Product Owner makes between scope, time and quality
Your checkpoint
A value-measurement sheet listing 5 outcome metrics for a fictional product, each with a definition, a data source and how it would inform backlog ordering.
Stakeholders, Customers and Product Strategy & Product Ownership and Delivering Value
Map stakeholder groups by influence and interest and state an engagement approach for each
Explain how customer feedback loops shape the product goal and backlog ordering
Describe how a Product Owner balances competing stakeholder demands while protecting product coherence
Connect product strategy to Sprint-level decisions with a concrete example
Your checkpoint
A stakeholder map for a fictional product with at least 6 stakeholders, engagement cadence per group, and a 200-word narrative linking one stakeholder insight to a change in backlog order.
Scrum Theory and Empiricism & The Scrum Framework and Accountabilities & Product Ownership and Delivering Value & Product Backlog Management & Stakeholders, Customers and Product Strategy
Re-take every self-check from weeks 1-7 and log any concept still below 80% recall
Complete at least two full-length timed practice sets under exam conditions and review every wrong answer
Rewrite your weakest three concepts from memory in plain language
Articulate how the five domains interlock in a single end-to-end product scenario
Your checkpoint
A final review log showing scores per domain across two timed practice sets, plus corrected notes for every missed concept, with all domains at or above 80%.
Milestones
Week 4: Explain the five events, three accountabilities and three backlog artefacts from memory in under 10 minutes, achieving at least 85% on a 30-question self-made quiz covering domains 1, 2 and 4.
Week 6: Produce a written answer to 'how does a Product Owner maximise value?' in under 5 minutes that names at least three concrete mechanisms and cites no more than one uncertain fact.
Week 8: Score 80% or higher on two full-length timed practice sets and show a written correction for every missed question, with each of the five domains represented.