Team reviewing notes during a backlog planning session

Product Ownership

Being handed a backlog isn't the same as owning a product. Effective product owners make deliberate trade-offs between competing stakeholder demands, protect the team from scope churn, and can explain why the backlog is ordered the way it is — every time, not just when challenged.

This course builds the practical skills behind that role: writing user stories and acceptance criteria the team can actually build from, prioritising a backlog using more than gut feel, and managing stakeholders who each believe their request is the most urgent one. Participants also work on saying no well — a skill that matters as much to product ownership as saying yes.

Course duration & format

  • Duration:

    2 days (f2f) / 4 half days live online sessions

  • Format:

    Instructor-led, face to face (or interactive online), working with a live or simulated backlog throughout

  • Optimum class size:

    12 to 20 participants

  • Entry requirements:

    None, though basic familiarity with Scrum or Agile is helpful

Learning outcomes

  • Write user stories and acceptance criteria a team can build from

  • Prioritise a backlog using structured techniques, not just instinct

  • Manage competing stakeholder demands with a clear, defensible rationale

  • Protect the team from scope churn mid-sprint

  • Say no to a stakeholder request without damaging the relationship

  • Run an effective backlog refinement session

quote icon

Owning a backlog means you can explain why it's ordered that way — every time, not just when someone challenges it.

Intended audience

  • New and aspiring product owners

  • Business analysts moving into a product role

  • Project managers transitioning to product ownership

  • Stakeholders who want to understand how good backlogs are actually managed