I would like to start by saying that I understand this isn't a pure agile way to do things but it is the scenario I am faced with and could use some advice. Our 2 week sprints include both development and testing. However, after the sprints are completed and before the release, we still have a period for integration testing. The dilemma I am struggling with is coming up with a jira workflow that shows burndown during the development/qa sprint (which I believe means we would need to mark the story Done once testing is complete). However, then we would still need to know that there is more work (integration testing) that needs to be done to those same stories before we release. Does anyone else have a similar workflow and could share how you handle this? Or can anyone come up with a workflow solution in JIRA without having to clone every single story?
We use JIRA 7.9 server version.
Our Definition of Done is when the issue is sprint tested and closed.
We use 2-week sprints.
This means our Integration and User Acceptance testing is managed *outside* of JIRA sprints because this work is done by a separate team (who do not use sprints nor JIRA) at a later date (i.e. release preparation).
It is not ideal, but as we release only 3 to 4 times a year (i.e. the results of 4 to 8 sprints of development), it is manageable.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs