We're struggling with how to present this - an epic is composed of a large number of stories. (about 50) These stories are inter-related, and really bear no resemblance to how we'd actually go about implementing a solution. (Let's call the User Stories "front of house", "back of house", "sides of house") In order to create something that tracks reality, we created different Stories. ( "Foundation", "1st Floor", "2nd Floor", "Roof") Each of our development Stories has meaningful sub-tasks. (Foundation has "Dig Footings", "Pour Footings", "Build Block Wall".) We are reporting time and setting completion of our meaningful subtasks as we build the software pieces. Each developer created and estimated their sub-tasks, and those were nicely rolled up into the Story.
The problem is that the JIRA view of the original User Stories will show NO COMPLETION at all until the house is built from Foundation to Roof. There is no way of saying the "Front of the House" is completed from bottom to top until the whole house is completed. So the management view shows no burndown, no completion, no progress.
In Theory, the view of a house as being Four sides should be equivalent to the view that a house is built from the ground up. Is there another way of us representing our actual development activity?
Can we have the Epic "House" which has children Epics for Foundation, 1st Floor, each of which have Stories for what we used have as Sub-tasks?
Or can Stories have children Stories? If so, how does that show up in a dashboard/burndown chart?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot