User stories and acceptance criteria

Scenario#

A product owner describes a new employee request flow, agrees what completion means and links implementation tasks for the delivery team.

Steps#

1. Capture the requirement

   Write the user need and the context behind it. A story gives the team a shared reference for discussing scope before work is split into tasks.

2. Agree on completion

   Record acceptance criteria so reviewers and contributors can discuss the same expected result. Keep clarification close to the requirement.

3. Connect execution

   Link the story to its project and delivery tasks. Review progress in that context as the team plans a sprint or checks what remains.