I'm attempting to setup a new Scrum board or Kanban board (not sure which we want to use yet). When using post-it notes on the wall, we had setup the following columns, Ready, In progress, In validation, Ready for Production. We would create a post-it for each task and the story itself. Then, the story would follow the last task across the board. I can set up these columns in JIRA and configure the board to use Stories as swim lanes. However, the Story itself never exists in any column. Currently the Story is displayed as a band that crosses all columns and doesn't exist in any one column. Is there a way to configure the JIRA boards so that the story flows across the board with the tasks?
If I have understood this correctly:
>Currently the Story is displayed as a band that crosses all columns and doesn't exist in any one column
You have set the "swimlane" to "story". Go into the board configuration, look for swimlanes and change it from "story" to something else (none, for the most simple option). The bands should disappear, and the stories appear as cards.
Hi @Craig Rowland,
I've not seen anything like that myself, but I'm having a hard time visualising how the story itself would move across the board. That's not how scrum / kanban boards work, so neither does JIRA. When you close the last subtask, using the "Active Sprints" view in JIRA, then you have the option to close the story at the same time, so it does it for you.
Are you running Sprints? If so, use a Scrum board, otherwise use Kanban.
Hope that helps.
We're hoping to use JIRA to do something similar to this...http://www.agilemanic.com/kanban/kanban-scrum-tasks-board/
We think of Stories as MMFs. Tasks are the detailed work items that need to be completed to realize the Story. The issue that I think makes this difficult is that the Stories/MMFs have a different workflow from tasks. Tasks are Not Started/In Progress/Done. Stories are Ready/In Progress/Business Acceptance Testing/Ready for Deployment/Deployed. The pictures in the blog above show these sub-columns for tasks that make up a Story.
@Nic Brough, thanks for the suggestion. Unfortunately eliminating the swim lanes leaves you unable to see the progress of a particular Story because you cannot tell which Story any particular task belongs to. At least not by glancing at the board.
I think the best solution in JIRA is going to be to have two boards. A task tracking board will enable the delivery team to see the status of what they're working on, what's done, what's next, etc. A second board with Stories will allow all stakeholders to see the progress of our Stories/MMFs. External stakeholders don't really care about the task level detail anyway.
The tasks remain grouped by stories. However, my other standard advice about boards in JIRA Agile is roughly where you're headed already. Have one scrum board for planning (if you are doing planning). Then set up as many Kanban boards as you need, per team, project, purpose or even user, doesn't matter. Make them the best you can for the target users. Just educate them not to click "release" unless they understand the implications, and you can get as many different views as you want or need.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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