User stories and acceptance criteria

Workflow overview#

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.

Access and next steps#

Available controls depend on your workspace configuration and access to the relevant records. If an area is missing, ask your administrator to review your access.

Understand the platform or choose a starting path.