This question really asks for "best-of-use" advice on how to use JIRA and JIRA/Portfolio to go from user stories that are created by product manager and actual development tasks that are created by the team to support the user stories created by the product manager.
At our organization, we started with Product Manager creating top level epics and under those epics, he created user stories. For example, as an Epic he created User Management. Under those epics, he created user stories such as create a user, update user, reset a password, login into the system, etc.
So, essentially, this is what we have right now in JIRA: https://www.atlassian.com/agile/requirements
We wanted to get a general idea of how long these would take, so we met and discussed all the epics with the UI, backend, QA, DevOps, UI/UX guys on the project to get some rough estimates. So now, for each epic, I have rough estimates for QA, DevOps, UI/UX and backend implementations.
These estimates allow me to create appropriate "fake" estimate tickets under each Epic, assign those to Teams in JIRA/Portfolio and get an idea of how long the project will take.
So, at this point, I have a few questions:
Are there some documents or processes which are written on how to use JIRA to effectively manage/track/administer a project from start to finish?
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