Agile is traditionally a Software Development methodology. While there are many resources online on how to approach DevOps with an Agile perspective, most of them fail to address some issues we are having.
We use a weekly Sprint in JIRA Cloud (with the Grasshopper Plugin). We maintain a swim lane that uses an Operations component and a corresponding JQL filter, and another swimlane for Sprint stories.
Operations tasks are not pointed and don't affect the Sprint in that way. We define an Operations task; vs. a story, as a task which must be done within 48 hours.
The problem is that we tend to create many Operations tasks after the Sprint has been started, and many are left in a non-done status (in-progress, under review, blocked, etc) at the end of the Sprint. This makes Sprint planning more tedious because we expect those issues to automatically carry over to the next Sprint.
My question is whether it would be considered terrible practice to create a long-ending Sprint called Operations that has a end date in 1 or 3 or 6 months. Then keep all Operations tasks there, and all stories in the Active Sprint.
Has anyone experienced a similar problem? Found a better solution?
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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