[hdhjebebeb]

Tickets by themselves are a symptom of a good process and not the end goal. If you don't know where tickets come from, why they exist, or when to do them, then the whole process is nonsense.

I've seen this repeatedly at places where they want developers to track what they're doing, but they don't have any product function to populate the backlog, groom it or prioritize tasks. It's basically anarchy but the devs just document what they felt like doing. Of course developers come to resent this system because nobody wants to read their diary - everyone else wants to know how close things are to being done. But because the whole project hasn't been scoped and broken down, it's impossible to get that knowledge from a snapshot of what people have been doing.

[whall6]

From what I’ve seen that’s the only role that product plays to justify their existence