Story breakdown in JIRA

[Shruti Ahuja]

We have a project in which each story requires work on multiple components and environments . Each task is done by a separate team member and is needed to complete a story .

E.g Story S1 needs -

XML to be created

XML to be loaded

ETL to be created

ETL to be loaded

Config to be updated

Each of these tasks has to be done on Dev , QA & production for it to get completed. Majority of the time , all these cannot be completed in the same sprint for the story to be done .

Need thoughts on how stories should be broken up so that its completed in a sprint and how should environment specific tasks be managed ?

Thanks

[Cloudites Owner]

Don't comingle stories with change controls, use different issue types. For example:

S1 - Status: Costomer Signed Off, Issue Type 1 (Many tasks to get to this status)

CC1 - Promote S1 to Pre-Producrion Alpha - Issue Type 2 (Triggered when main S1 issue Status = Customer Signed Off

Compartmentalize stories based on the services layer to optimize well built stories flowing through environment progressions, this will reduce the number of times you have to touch the code for the story, ultimately saving costs.