You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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 ?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.