We recently started using Jira Plans for our sprint and capacity management.
We have encountered a behavior which we do not understand and was wondering if anyone could tell me, whether this is intended and what the reasoning behind it is.
We created a Team called "Anna & Stefan" with a capacity of 10d per sprint. A sprint lasts for 2 weeks. I then created a Story with 15d original estimate to be completed over 2 sprints. My expectation would be, that the story would fill up the first sprint fully (10/10 days) and the second sprint only halfway (5/10 days). However it does the exact opposite:
Is this intended? If I increase the original estimate to 16d, it even shows the last sprint as red and overbooked instead of assuming a load of 6 days for the first sprint.
If your story is spanning across multiple sprints then ideally it is better to create an epic with multiple stories. Also, how many people are there in your team? is there an releases associated with that story? Are those resources working on something else during that time?
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
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