Does anyone know of a way to create empty sprints so we can plan out sprints for the year - i.e. we create sprints with start and finish dates, for the whole year and then in planning we can simply add in the items to the relevant sprints throughout the year?
Hi @Simon Phillips,
You can add as many (empty) sprints as you like. You cannot set the dates up front, as they are filled out when you start the sprint.
But that should not keep you from creating a couple right away.
(just click the Create Sprint button a couple of times)
Just be aware that the more sprints you create up front, the more hassle it will be to assign issues from the backlog into the correct sprint. In sprint planning, that will usually be the next sprint (maybe 2 or 3 maximum ahead of time).
And I know from experience that no living being is capable of correctly planning the allocation of work to the correct sprints up front for several months correctly. That will mean you'd be dragging work across sprints all of the time.
In the end, in terms of effective work management I'd dare to suggest not creating more than like 2 or 3 sprints ahead of time will often prove to be most effective in terms of organising your work.
About the vacation part: the tool does not support you there. The sprint is a commitment of the set of issues you commit to as a team for a certain time box (of usually just a couple of weeks, right).
The tool is there to visualise the result of your underlying sprint planning process, where you sit together as a team and decide what the amount of work you are going to undertake during that time box. In that meeting, you take the capacity of your team (and as such also holidays) into account to decide what work will be committed. And it is the result of that exercise that ends up in your sprint.
You are right that it may be added value to include this capacity information into Jira to support your overall process. The Atlassian Marketplace offers quite a few apps that may support that capacity use case
personally I would do this outside of Jira. I can imagine planning an entire year out would inevitably result in constant change. as each sprint approaches you can then use the external reference to build the upcoming sprint. Alternatively, maybe your create a dummy scrum board for planning then clean things up as you move the issues into the actual execution scrum board. just a crazy idea. :-)
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events