Am 06.01.11 17:44, schrieb Steve S: > It's nice to have a reference path like requirement -> user story -> > task, but it would be very helpful to be able to have a ticket > hierarchy, as well. As a team, we prefer to break down higher level > tasks into smaller increments (approximately 8 hour sub-tasks). I > realize that you can structure your user stories so that they basically > define one high level task, and then have each small task reference that > very specific user story, but I am not sure that our system engineers > have enough technical knowledge to be able to make each user story that > specific. > > As a solution, I think it would be great to see something like this: > > A new ticket type, e.g. "master task" > When creating a master task, you can create a referenced sub-task, which > would simply be the current "task" type, so no new ticket type would be > required for this. The master task would be an aggregation of all of > the hours of the referenced sub tasks, but have no actual hours of its > own. It might also contain an aggregate of all referenced sub-task > comments. Of course, links would be permissible between user stories > and master tasks, or just regular tasks. I think it would be wise to > disallow the closing of a master task until all referenced sub-tasks are > completed, and maybe this would happen automatically. > > Is there any chance that this could happen, or is there some > functionality that I'm missing that would already provide this type of > thing?
This is certainly doable - but I would argue that you can achieve the same thing without adding another level of abstraction. All you need to do is split stories that you deem to large into multiple smaller ones and then implement them one after another. In the workflow this means that early in the life of a story it's more of an Epic and then later when you break them down (what you envisioned as master task) they become the right size for stories you can actually implement. To achieve traceability, just mention the ticket link of the 'epic' this was split from in the description - voila. (Don't use the linking feature to link to things of the same type or the whiteboard / backlog will get confused - sorry 'bout that). Regards, Martin -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by Agilo Software GmbH <http://www.agiloforscrum.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
