In Jira, should I do a new project or an Epic?
briley last edited by
We are currently redeveloping a monolith application into a micro-services architecture.
So we will split one application into 20+ modules. Today we use a project to track all changes to the monolith. But we are having doubts on how to proceed.
These are our options :
Should we make an Epic for each module that will detach from the monolith ? This has the benefit of allowing us to track time in a centralized manner, but when we will have 25+ Epics and that the modules continue to evolve it will start getting chaotic (I think).
Should we make a new JIRA Project for the module to track all changes ? This means that in the long term we will have to juggle with more than 25 JIRA projects to track all changes, and all timetracking.
I don't know if JIRA offers other options and JIRA Portfolio really seems like overkill.
Do you have any suggestions ?
One project, multiple epics
I don't really see how 25+ epics will be more chaotic than 25+ projects.
Don't overthink things. Redeveloping a monolith application into a micro-services architecture will be challenging enough for your team, they shouldn't also be forced to analyze things from an organizational point of view to see where each task goes where. There will also be cross cutting tasks, like building a service bus for the services to communicate with each other, which will impact all projects (if you go with multiple projects) but won't fit into any of them. Will you create another project for "Platform" stuff?
Only you can answer your question. Do you actually need to keep track of time, cost, etc for each of the micro-service? Does it actually matter? Do you have separate teams working independently on the micro-services? Or do you work on any of them during the same Sprint? If, for example, the CustomerService takes twice as much and cost four times as much than the ShoppingCartService, does it really matter? These are the kinds of questions you should be asking yourself.
Figure out what is important and then figure out what form of organization would best fit that. If you don't think about what you need, then you might just as well flip a coin.