We’re rewarding the question askers & reputations are being recalculated! Read more.

New answers tagged


I don't think there's a right or wrong answer to this question, but here are the main factors I would consider: How many teams will share the work? If you have more than one team (especially if they might end up using different types of workflows), it might make sense to create different projects. How distinct will the modules be? Are there some general ...


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. ...

Top 50 recent answers are included