Hacker News Reader

> supposedly a tool to manage agile teams, is how every ticket has one person assigned to it.

It's whoever owns the issue. You can make it an epic and assign particular sub-tasks to team members if it's a teamwork.

View on HN

Not sure how that solves the pair programming issue. What you’d need is a way to split the points for a single task among 2+ people without the overhead of duplicating the ticket.

It's, what, two clicks to duplicate a ticket, and another to assign one to other person? Sure a "this person paired" button would be easier, but sometimes you just gotta do jira chores.

Then the status has to be tracked in two places. It’s certainly not impossible, but as a programmer I’m allergic to unnecessary busywork.

Then get rid of the "points" and maybe the "tickets" too.

In my team, points and tickets are useful for knowing we’ve scheduled a solid - not overwhelming or underwhelming - amount of work.

Get rid of the scheduling too if you're doing it too often. Two times a year is good enough.

If only there were some person who's job it was to deal with said busy work because you think it's beneath you. Some sort of manager of the program, who is also technical.

And if there’s pairing on a sub-task…?

Reply on news.ycombinator.com