i'm wondering what is the best practice for organizing the backlog. currently i'm working on a a big project with many epics and hundreds of user stories. the backlog is bit messy, and the team is unsure which user story will be developed for which sprint.
as far as I understand in the agile framework, we should have releases, and those epics/user stories should be organised by the release, which we are currently trying to achieve. however, my team has strong desire to have a low-level user story assigned to which future sprints!
here is the thing, our design team usualy is ahead of our development team -duh- so they express wishes to know in advance what tasks or user stories in the few upcoming sprints to start working on rather than waiting around till the development team is ready for sprint planning session. the thing is agile adapts as it goes rather than have such clarity of vision in the few months to come (more like a waterfall)
what do you guys think?
I feel like we should not create few sprints in advance since the sprint planning should be the whole team efforts and commitment for the sprint which cant be figured unless the team is ready to commit to it. and as far as organising things per releases, we have a good 8 months between each release so that's too long of a chunk to organise :!
appreciate your inputs
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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