JIRA for a large non-Agile project

Just had a  question on the best way to use JIRA for a large multi-year project.  Obviously, the default agile methodology isn't a good fit, so what's the best way to organize work given there may be hundreds, if not thousands of tasks created during this project?   

Should we go the route of using versions to mark milestones, or should we create EPICS and stories instead?  

If anyone has suggestions, I'd greatly appreciate it!

 

1 answer

This widget could not be displayed.

Hi Matthew,

a good way how to handle such a large project would be JIRA Portfolio which is quite handy add-on. Along with use of versioning you gain high level insight into your plan and overall progress while being able to test different scenarios for any changes

Thank you for the feedback.  We'll take a look at JIRA Portfolio.

-Matt

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

573 views 25 15
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you