Create User Stories

This activity produces user stories together with clear, testable acceptance criteria. The Product Owner typically authors the stories, ensuring customer needs are captured in a way that is easy for all stakeholders to understand.

Key Points

  • Outputs include user stories and their acceptance criteria that state conditions of satisfaction.
  • The Product Owner leads the writing, collaborating with customers, stakeholders, and the team.
  • Stories should be small, valuable, and follow INVEST; they are refined during backlog refinement.
  • Using the format "As a [role], I want [goal], so that [benefit]" promotes shared understanding.

Example

On a mobile banking project: "As a checking customer, I want to deposit a check by taking a photo so that I do not need to visit a branch." Acceptance criteria include: photos must pass clarity checks, deposits under $5,000 are accepted, user sees a confirmation, and an error displays for blurry images.

PMP Example Question

Which artifact captures the testable conditions of satisfaction for a user story created in this process?

  1. Acceptance criteria
  2. Definition of Done
  3. Sprint Goal
  4. Release plan

Correct Answer: A — Acceptance criteria

Explanation: Acceptance criteria specify the testable conditions that confirm a user story meets customer expectations.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your Agile career!

HK School of Management helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More