Need help to get some ideas to handle product deliverable that have multiple interim sub products?

Kent Chiu

Hi,

I have been given a task to organize a product delivery (Demo) using JIRA where a product delivery have multiple sub products. (Sub-demo1, sub-demo2,...).

The following is the structure of the conceptualize product demo:

Demo: the ultimate delivery of the product. It contains multiple sub-demos.

Sub-Demo: interim deliverable leading to the Demo. 

Demo and Sub-Demo: Contain of stories and tasks.

My initial plan is to use Epic for the Demo which contains stories and tasks. The only problem with this is how to organize the sub-Demos? Can Epic contains an Epic?

Ideally, each Sub-Demo is an Epic which contains Stories and Tasks and Demo is an Epic which contains multiple Epics of Sub-Demos.

Currently, I organize it as follows:

1. Demo is an Epic which contains all the Stories and Tasks.

2. Sub-Demo will be a collection of tickets (Stories/Tasks) that have labels for Sub-demo.

I was wondering if there are other ways that better to handle this kind of situation.

Thank you for your help.

Regards,

Kent 

 

Andy Heinzer

An epic cannot contain another epic. 

But what you might do is create Sprints for each sub-demo.  This is one way to organize a subset of stories/task/issues/bugs/etc.   While sprints are really intended to focus more on a time period when teams are working on a subset of issues, it might still fit your needs here.

Typically an issue will not exist in more than one sprint at a time, but all of those issues that exist in sprints (or don't) can still be added to an Epic.

Perhaps it would help to review Dan's post on Epics, stories, versions, and sprints.   It helps provide an overview of each of these terms and how they are intended to be used with Jira Software.