Proper Epic/Story/Task set up - Application Migration Project (Next-Gen)

[Nick van der Net]

Hi folks,

I have started a new Scrum Master role and have inherited a next-gen project for an Applications Migration project.

The current set up has the Applications as Epics, and the corresponding migration tasks (including testing) as child stories.

We're not using sub-tasks at the moment.

I'm looking for the best way to set up this structure. I suspect the Applications would be better placed as stories, though each application needs to be migrated to different sites during different sprints.

I'd like to use sub-tasks, but I guess I'm really after some input as to the best way to do this. This really is my first 100% Scrum Master role.

Thanks!

[Ash Pitt · Accepted solution]

Hey @Nick van der Net 

So many ways that you could potentially set this up but IMO it sounds like what you have there is ok.

Epics are ok to capture work within a feature/application as Epics can span out across a period of time (say a few sprints, months etc).

Having your tasks types (eg Stories, Bugs) within the epic make sense if you're prioritising the items in sprints.

In next gen the release feature exists, so you could add another layout that allows you to create versions and attach them to specific jira tasks. 

For example Application A is an epic with a total of 10 tasks. 5 of those tasks could be deployed in release 1.0, the next 5 could be deployed with release 2.0.

Hope that makes sense! The cool thing about next-gen is it does give you some flexibility to try things out.

Also here's a good resource that may help :) 
https://www.atlassian.com/agile/tutorials/epics

Cheers

Ash