Loading Profile...
What's the best way to split "Accept/Reject" responsibilities among multiple people?
I'm head of product for a software company (doing ongoing internal product development) and up until now I've been the sole customer and done all accepting and rejecting. We're adding a VP of engineering who will take responsibility for the more technical and internally facing stories, while I'll continue to be responsible for customer-facing features and bugs.
I have 2 options in mind to track whom should accept any specific story:
Option 1: Labels
We would apply a label to each story, either "eng" or "prod". We would keep a saved search for those tags, and each person would see the stories ready for them to accept. A big advantage: we can add labels to many stories at once.
Option 2: Change "requested by"
No matter who requests a story, we would use that field to track who is responsible for it. We sometimes refer back to the original requester to get more info on the story, but if the story makes sense to the manager then they can re-assign to their own name before placing it in the backlog. Biggest advantage: stories will show up in the right person's "my work" list and they will get the right emails.
Does anyone have experience with this, or general thoughts on the issue? After writing this up I'm leaning toward option 2.
I have 2 options in mind to track whom should accept any specific story:
Option 1: Labels
We would apply a label to each story, either "eng" or "prod". We would keep a saved search for those tags, and each person would see the stories ready for them to accept. A big advantage: we can add labels to many stories at once.
Option 2: Change "requested by"
No matter who requests a story, we would use that field to track who is responsible for it. We sometimes refer back to the original requester to get more info on the story, but if the story makes sense to the manager then they can re-assign to their own name before placing it in the backlog. Biggest advantage: stories will show up in the right person's "my work" list and they will get the right emails.
Does anyone have experience with this, or general thoughts on the issue? After writing this up I'm leaning toward option 2.
I’m still happy with tracker after years of use
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Update: we're a week into option 2 and things are working pretty well. It's sometimes hard to make sure that every story has the right person selected in the "requested by" field.
Since I can't find a way to do a boolean search on the requested by field (to find all stories that were are not set to one of the 2 official requesters) I exported all stories to CSV, opened in a spreadsheet, and sorted by requester. Each row has a link that can be dragged into the browser so I can go change the requester manually.
I’m happy enough, though I'd like a better hack
