You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'd like to pick your brain about what you think would be the best JIRA set-up when it comes to a several year long AAA game project. The objective being to use JIRA to its maximum potential for Sprints, Planning, Tracking and Reporting across the board.
I used JIRA in the past but mostly for BUG reporting.
I've just joined a new company developing a AAA project in terms of size and ambition and would like to build the foundation for proper communication and project management.
I've been scrambling my head around several, potential set-ups but can't really seem to make a decision at this stage on the path to follow, especially when it comes to defining PROJECTS.
Should I create one and only project (the game)? Or should I create one project per major milestone (FPP, Pre-Alpha, Alpha, Beta...)? Or should these be Epics instead?
When it comes to creating a Scrum Project, should it be team managed or company managed (to be fair, I have trouble seeing the difference)?
Thanks for the advice and support!