[failboat]

Where is the category for devs that will weasel out of any work by claiming a ticket is out of scope, or that the responsibilities for handling a certain piece of work lies with some other team, or that you should go through the project manager so that the work can be done 5 sprints later?

[leetcrew]

the first thing I ask myself in this sort of situation is whether the person is actually correct. part of being effective in a specific role is refusing to take on random work people throw at you. estimates can't be valid if key players are spending lots of time on stuff that wasn't on the schedule.

if the person is really just being obstructive, explain to their manager (or have your manager explain to that manager) why you think that team should fix the issue. keep going up the chain until someone with authority knows who ought to fix the issue. it's possible you get all the way to the CEO without finding someone responsible for fixing the issue, but in this case the problem is with the organization, not the IC.

[nullserver]

Worked in an environment were anything vague in ticket/story would cause team to reject considering it.

At first I was horrified at this. “You can’t tell the boss no!”

Six months later I had to admit it was by far the most productive team I had or have ever been on.

[Redsquare]

huh, they should be writing up their own after building a shared understanding of the problem in hand, what you experienced was a top down ticket factory

[vp8989]

Hah, that is definitely a category. The person who always creates a "follow up ticket" but never, ever does any of them.