You have to categorise and control your specific development otherwise you are at the risk of never actually making the game. First recommended option to combat this is Asana it is good for solo/small to medium teams working across multiple assets or projects, Teams who are more responsive to visual scrums, Teams who enjoy more ad-hoc workflows that are more lightweight and flexible, and Teams who don’t want to spend money on their process management. But it also isn’t so good if You are a team of two, or a solo developer also if Your project is relatively small in scale and You need strong security features due to your IP. Next is “Monday” which was formally known as dapulse.com. It is good if you have medium to large teams working across multiple assets or projects,teams who want to reduce time spent on set-up, teams working across larger, more long-term projects, teams who respond to visual material, teams who want to be able to customize to an extreme level, and eams who need high-level, quick support for changing and managing scrums. It is not good if you are a small team/don’t have much to spend, your project is small in scale/scope, you want to keep parts of the planning for your project away from your team at large. Next is Trello and is one of the most suggested. It is good if you are a small to medium teams working across one small to large project, a teams who like to see all facets of development laid out for them, you have individuals dedicated to managing the board health. It is bad if you have a large number of assets you need to generate, your project is big in scale or spread across many different teams, you want to manage your project health more closely, You don’t have the time to manage a large number of cards and their placement. There are more but these are the ones that interested me because I plan to be part of a smaller team.