Split Sprint and Release to JIRA
we currently have the following states / columns in JIRA:
- Open / Todo (-> The developer takes the task and starts working)
- Running (-> Developer sets tasks to run)
- Done (-> QA tests when setting and assigning a problem, ready to deploy or open)
- Ready to deploy (-> Developer deploys these tasks as of release date)
- Deployed (-> QA / Stakeholder Verification Task again on Live / Production and closed or reopened)
- Done / Closed
In my current understanding, this is wrong because we are trying to solve two problems in one dimension: Development and Deployment. I would like to separate the sprint from the release / versions. We are currently unable to complete the sprint until all tickets are approved in production, which will result in bottlenecks.
What would be your proposal? One of the ideas I have in mind: Limit the status to Open, In Progress, Done, Closed, and handle deploy / release over JARA versions. If the problem occurs during production, an error ticket must be opened.
Otherwise, I don't see a chance as the JIRA 6.4 version / release doesn't seem to contain status columns.
source to share
Releases the production portion of your team's definition? If that's the workflow you have, it makes a lot of sense.
There is no separation of concerns between development and deployment. Code that has been developed but not deployed has no business value. Development is simply a step in the release process, which is the point at which the value is implemented.
A sprint is a timeframe, not a given amount of work. When the end of time runs out, the work you are still doing is not getting done. If you regularly can't get all the work you bring to the sprint, then that suggests that you are working too hard. Team speed, which is a measure of the work done by each sprint, should be a good indication that you have a sprint.
If your bottleneck is release to release and release validation, perhaps you should focus on improving that process? Perhaps this could mean more automation of the release, or better coordination with stakeholders on validating releases.
source to share