title
How to create tickets

How to create tickets

A ticket (or card) organizes and tracks our work. Creating tickets may also be best learned during a project (on a project-by-project basis).

Epic

An epic often starts as the big picture and then the user stories fill in the details. A single epic can contain two or more tickets.

As they are prioritized, a group of user stories also can form an epic.

Most tickets should contain a user story
The structure of a user story is: As a(n) X I want to Y so that Z (outcome)
Describes the user need for the work to be done
Example: As an anonymous user, I want to see the latest news articles on the homepage so that I do not have to view older articles that I may have already read.
Avoid more than one action per user story. Red flags would be commas and "ands". Consider splitting actions into multiple tickets.

Explains how we validate that this ticket or card works
Written in a language anyone can understand
Explains what the ticket will not do as well
Acceptance Testing is the process that verifies if the installed piece of code or software works as designed for the user
Ideally the Product Owner (PO) writes the Acceptance Test for a piece of work
Testing with users is an important factor in ensuring the work is performing/created as expected

Written step-by-step so that anyone can pass/fail the test
The PO will also run through the same test
It will also explain the expected results
Contains specific directions or steps a tester can follow that ensure what was developed produces what the engineer intended