In our team we work with Kanban. We release once a week. We want to use versions as a "monthly view" of work, with Easy Agile Story maps, in order to be able to prioritize and structure stories in.
When releasing we want stories to be included in the release. And versions preferably just to be a label for a number of releases. As it is now the stories are related to versions.
Any thoughts on how we can have our releases weekly and use Versions as an overview in Easy Agile Story maps?
Perhaps best for a quick chat on the phone.
A few questions:
Thanks Philip, have a great day,
Product Manager, Easy Agile
Thanks for your answer. See my replies below.
1. It´s one release each week.
2. I would say that the weekly level is great for our development team and for me to keep track on a detailed level. Having issues in one months release would result in very many issues in one release. We are quite a big team. The Versions is a way for us to plan and to communicate to stakeholders on a higher level.
3. Currently 3 months ahead on a high level. But preferably 3-6 months. There can be changes, but sometime there isn´t =)
Best option in this scenario is to use a Scrum board and create a weekly sprint. No need to go through all the ceremonies, and the sprint will let you group the weekly release train and report on it later.
You'll then have the option on the story map to look at the monthly version plus the weekly release sprints.
No need to change the practice you've got today, just leveraging Jira in a slightly different way to achieve the same outcome.
Hope that helps
Thanks Philip, have a great day.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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