Loading Profile...
How to handle Tasks?
How do you guys handle the concept of tasks inside a story in Tracker? We would like tasks to be visible and belonging to story in a tree view.
I’m confused
1
person has 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?Hi Bruno...instead of stories that decompose into many tasks, we prefer to work with small, granular stories that can be completed in a few days or less. It's possible to maintain a to-do list in the story description field, though.
-
Inappropriate?Makes sense, agile methodology talks about going back to the domain honor to iron out the details of a story. Where should I store those? What about the engineering tasks?
I’m happy
-
Inappropriate?Hi Bruno...you can use comments as a running discussion with the story owner, as well as the description field and/or file attachments. For engineering work that isn't really part of implementing a particular feature story, you can create chores (another type of story). The most important thing, in my opinion, is to break your features into small, independent stories, that can be implemented relatively quickly, and not worry too much about how the stories break down into coding tasks.
1 person says
this answers the question
EMPLOYEE
