tl;dr: I believe ticketing tasks is in opposition to the creative process.

Of course we need to define our goals. I love the proverbial ‘epic’. And I do get tickets in general– eg for recording and tracking items like bugs. And for waiting in line at Baskin-Robbins. But in terms of software craftsmanship, or any kind of craftsmanship, does the technique of ticketing a ‘task’ help? Does it not constrain and limit — by definition? And if not, then is it a ‘task’ in the first place?

Do other creative industries use tickets for their tasks? I’m no luthier, but I find it hard to believe a firm designing a new guitar is using tickets to define their tasks. How come it’s different in software development? It’s never made sense to me.

ps// this is my first post on reddit! thx for taking the time hope to get some elucidation.

submitted by /u/jmazin
[link] [comments]