Clik here to view.
Another anti-pattern here, as demonstrated by the AI bootleg Beatles.
We may find it useful to track tickets and look at their statuses, but are we actually solving problems in our stand-up or our process? or are we just passively looking at a database of things that don’t change from one day to the next.
Caring about reporting on the status of tickets can take attention away from focusing on delivering value. While this isn’t JIRA’s fault, sometimes the model and its observations become the language of the team. We track and input into things, rather than make a difference.
