Loading Profile...
How to handle recurring responsibilities?
How should I handle small recurring tasks that still provide indirect customer value? Though non-coding in nature, they may still require an assignee to spend time on it. (ie Someone is assigned to answer technical support issues / clear that queue; someone to update the demo for each major feature release). It sort of affects the customer, but I could see it being a chore too. Am I getting too literal with the definitions of each story type?
- N00b
- N00b
I’m overthinking it.
5
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?Depending on the project, these recurring tasks could be identified as features or chores and I'm comfortable with that. What I wonder is if we should be creating new stories from scratch each time - alternatively, we could copy/paste the information to be imported via CSV but it still seems like there could be a better way.
I'm thinking about regularly recurring tasks/stories such as creating content for a blog site or a book, Making/closing sales calls, etc.
Suggestions for how best to handle this? Perhaps our questions suggest some new features to be considered for later?
I’m uncertain
-
Inappropriate?I agree. It would be nice to have the ability to create either template stories or recurring ones. We have specific tasks that need to be performed in a specified order when we open a new location or upgrade internal applications.
It would be nice to select a group of stories, change a couple details, and then activate them to be worked on. -
