Why We Write Tickets

John Cutler
HackerNoon.com
2 min readMay 4, 2017

--

Shared with my team the other day in Slack …

Why we write tickets

  • So if we get sick, a teammate can help us out
  • To help us decompose our work into small pieces
  • As a placeholder for a real-life conversation
  • To keep track of how we resolved the issue
  • To make our standups effective
  • To point out dependencies
  • To reflect on the mix/makeup of our work during retros
  • Self-discipline. Don’t take on too much. Try to do one thing at a time

Why we DON’T write tickets

  • To track our time
  • To compete with other team members
  • To show managers we’re busy
  • To make managing people possible
  • To report status, or % complete
  • Because Jira is fun to use
  • External discipline

Hacker Noon is how hackers start their afternoons. We’re a part of the @AMI family. We are now accepting submissions and happy to discuss advertising & sponsorship opportunities.

If you enjoyed this story, we recommend reading our latest tech stories and trending tech stories. Until next time, don’t take the realities of the world for granted!

--

--

John Cutler
HackerNoon.com

Multiple hat-wearer. Prod dev nut. I love wrangling complex problems and answering the why with qual/quant data. @johncutlefish on Twitter.