As a Product Manager, I am working to build a backlog of Epics for a release, defining them, prioritize them, and then begin grooming them with the team (determining how we break down the Epic into User Stories, and further grooming the storeis). However, before I begin bringing the Epic to the team, there are several things I need to have in place. Does the Epic have architectural input? Is there a mock up/wireframe? Does it have customer validation? is the customer and business value well defined?
What I'm trying to do is make a Kanban board for my Epics so I can keep track of which ones need further definition before bringing to the team, but I don't see a way to do this in Jira.
In my previous job I used Rally (for them an Epic is called a Feature) and we had a means to create Feature Kanban board for the Product Management team. Any help here would be great.
You can modify the "Issue Type" to call it Epic /Feature/etc.
To have a kanban board focus on Epics only you can set a filter on the board to only look at those issue types. You can also use "Quick filters" to further filter the board while viewing it.
Editing issue types:
Editing quick filters:
I usually make what's called an Upstream Board to handle this work. Here's what I do.
I hope that helps!
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