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.
My team and I are using JIRA for over more than 3 years now. Our team consists of 6 developers and we are developing several online games. The current JIRA structure is as follows, we have 2 projects / boards:
However somewhere over the course of those 3 years everything around us has changed, but we've never changed the way we work in JIRA. And I'm not sure what's the perfect way to implement JIRA (and porfolio for planning) in our situation.
My best bet would be this scenario:
The above scenario rises some questions:
Thanks in advance for helping us to use JIRA in the best possible way :)
What we have is:
1) A 'private' sales project (INT) that is used to manage a bunch of the company' sales stuff and connect it to development. We have a CRM for sales specifics but this project will 'connect the dots' for the sales team and offer real-time (through Agile Board) progress on our available time.
2) For every new 'sale' a new Epic is created in the INT project. We create Epics from the internal so that all follow the same workflow, etc.
3) For every new software, a new project is created. All projects share the same configuration.
4) For every new software a new Service desk project is created. All SD share the same configuration.
5) We use porftolio to plan everything.
6) We use Scrum to manage all software development and support. Development Issues come from Portfolio while support tickets come from the Service Desk Portal in which the support rep creates a 'linked issue' as a bug into the respective project. Those tickets show up in portfolio and are treated depending on how critical they are.
7) In Portfolio issues are related to the Epic respectively. Cross-releases are managed w/o problems this way.
8) We dont use estimation by hours but story points instead. With a little bit of statistics you will be able to get a bunch of information out of it. Also portfolio will automatically adjust to what your team can produce. No need to change weekly... just enter holidays and get going.
* We are just 8 employees using Jira, so we manage to keep everything under the 100/month which is our budget for all this. I pretty much use everything: agile, service desk, confluence, portfolio, tempo and more addons.
hope it helps.