liveBook · Manning

User story

As explained in Developer Experience on Kubernetes

A concise requirements description expressing a software capability from a user's or stakeholder's perspective.

A user story is a short requirements description of a feature from an end user's perspective. It triggers the inner loop, where developers implement the change, while leaving further details for implementation discussion. section 2.1.1

Structure a story around three parts:

  • Role: identify the stakeholder who benefits. section 2.1.1
  • Feature: state the desired capability or behavior. section 2.1.1
  • Benefit: explain why the capability is valuable. Keep the story independent, negotiable, valuable, estimable, small, and testable using the INVEST criteria. section 2.1.1
  • Agree on acceptance criteria with stakeholders before implementation; use them to determine whether the requirement is complete. section 2.1.1

Appointment category selection

As a patient, I want to select an appointment category so that I can book the right kind of appointment for my medical needs. A matching acceptance scenario could require that selecting Cardiology shows only appointment options for that category.

How Developer Experience on Kubernetes covers it

How deep it goes
Defines the template, INVEST qualities, and acceptance-criteria workflow but defers detailed implementation discussion until development begins.
Examples
Uses appointment category selection and a Cardiology visibility scenario to connect a story with testable behavior.
What it assumes
Assumes stakeholder and development-team collaboration while defining requirements and teaches the story structure from its basic definition.
What you can do after
Apply it via a role-feature-benefit template and acceptance criteria to plan, prioritize, and verify a capability.
How it connects
Connects requirements with the inner loop, acceptance criteria, and behavior-driven development.

Also explained in

Compare how 9 books explain user story →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Developer Experience on Kubernetes. The section links point to the parts of the book it draws on.