We are looking for a tool to help us plan releases, and thus I am playing around with Easy Agile Roadmap.
Our sprints last 1 (bug fixes sprints) to 3 (feature sprints) weeks, after each sprint a new version of a product is released.
We use epic to group stories under a common subject.
During a Sprint, we may work on 1, 2 or even 3 epics but we won't always close an epic at the end of the sprint as some user stories might still be in Todo state (ie: they were not planned in the sprint)
Your product is really interesting, but it does not seems to match our organisation.
Is there a way to plan sprints and not epics ? It would also be nice if the sprint duration could also be taken into account when planning.
Is it in your plan to support our use case or do we miss the point ?
Maybe we just need some kind of Gantt chart tool....
From what you describe the user story map (Easy Agile User Story Maps) may be a better way to plan what is in upcoming sprints. You can use the epics as long lived groupings/buckets for stories and split the story map horizontally for sprints of any duration.
As for Easy Agile Roadmaps, we're exploring the possibility of 'splitting' epics into multiple chunks as there are teams, such as yours, who work on an epic for a release and then come back to it a few releases later. We envisage it is still one issue in JIRA, yet it can appear several times on the roadmap.
And we also have a story on the Easy Agile Roadmaps backlog to visualise sprints on the roadmap, similar to how you can add versions and ad hoc markers today.
Hope that helps. Happy to answer any other questions you have.
Nick Muldoon, Product Manager, Easy Agile
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