I habe been using User Story Mapping with my clients for a while and now that I'm using Jira/GreenHopper, I would like to still give this experience of hole picture project view.
Easy Agile User Story Maps for JIRA is an add-on to JIRA Agile / Software / GreenHopper that assists teams with conducting story mapping sessions.
You can read more about the practice of story mapping here:
Avion is a user story mapping tool which also integrates very tightly with Jira (both classic and next-gen projects!). You can use Avion to plan your product backlog and the longer term release plan, and push your releases straight into Jira where your dev team can focus on the important day-to-day tasks.
A few useful links:
If you are looking to sync issues from Microsoft TFS to JIRA I recommend you investigate these add-on for JIRA: https://marketplace.atlassian.com/search?query=tfs
This particular question that Wagner asked is about the practice of story mapping, which agile teams conduct to create their backlog. More on that practice in this blog post.
Thanks Michele, have a great day,
If you'd like to use a more lightweight approach for user story mapping, than creating JIRA issues while brainstorming, please have a look at StoriesOnBoard. It can be connected to JIRA, but it's not tied to JIRA's structure, your team can structure their around customer journeys, there's no need to create JIRA epics and issues while your team is brainstorming.
We imagined StoriesOnBoard as a lightweight tool for brainstorming and planning products where teams can just put their ideas on a board quickly and organize them easily.
Have an idea? Just press "n", write a few words and move forward.
"Searching a product" story is too big? Just copy and paste it's card two times and update their titles (by pressing "t" key) to "Search by name and description", "Full text search", "Advanced search".
"Oh, I think we won't really need Advanced Search". Just delete it with the delete key. Gone.
With StoriesOnBoard we'd like to support these situations. I think creating Jira issues as one have to do it in the Jira plugin kills this process.
Jira is fine when you know what to do, selected it, and the team "just" need to implement it and wants to dig into the details of the stories. The Jira plugin is really good at visualising an existing backlog and grouping it's issues by different attributes, but not as good at creating and updating the backlog.
More info about how it works with JIRA: https://storiesonboard.com/blog/post/keep-your-user-story-map-in-sync-with-jira,-trello-and-pivotal-tracker
Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...
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