| title | description |
|---|---|
Jira |
Working with Jira boards and tickets |
We use Jira as a common tool for managing product work. Each team works within a "project."
Our workflow takes Jira issues through these stages:
| Define | Ready | In Progress | Review | Merged | Monitoring | Done |
|---|---|---|---|---|---|---|
| Further definition or requirements needed before engineering work can begin | Requirements, priority, and high-level design are established enough that work can begin | Actively being developed | Pull request submitted and being reviewed or improved | Merged and deployed to staging; ready for QA | Deployed to production | Confirmed to work as expected in production; any data has been collected; clean-up complete (no further tracking necessary) |
- Epics should be goal oriented
- Stories should be impact oriented
- Subtasks (when necessary) should be release oriented, usually corresponding to pull requests
(TO DO)
(JK)