Jira
Jira is a ticketing system that allows teams to manage and share the status of work as well as a mechanism to prioritize that work. This helps create transparency into all work executed by a delivery team, resulting in: - a single point of truth for all work done by a team - no hidden or untracked work - high alignment and updates between team members on the work in progress - ownership of all the work by the team - allows leaders to see what is happening without distracting team members
Features¶
- Backlog. Prioritized list of tickets to be reviewed, refined, and readied to bring into the sprint.
- Kanban Boards. Single pane of glass for current work in progress.
- Ticket Status. Provide real-time conversation and associated commits and build history with each ticket, along with ongoing comments and status updates.
Breakdown of Ticket Types¶
Jira refers to tickets as issues. Although there are various ticket types out of the box (include customizations), a lean DevOps team will focus on these tickets:
| Ticket | Purpose | Duration |
|---|---|---|
| Epic | Large bodies of work, feature focused or higher, spans multiple Sprints | 1-4 iterations |
| Story | Small amount of work, driven by the Product Owner | 1 day |
| Subtask | Small amount of work (often created in-sprint) that lives under a story or task | <1 day |