- Sep 12, 2020
- 395
- 2,610
- 367
Truth is, I have always been on more than one project. During the development of The Goblin Brides I was working on a big mod for a game. I felt that both project complimented each other, as if I felt stuck creativily in one of the projects I started work on the other, and working on one project gave me ideas for the other.There are two schools of thought when it comes to multiple concurrent projects:
1. Multiple projects splits focus, energy, attention, mindset, competence, and 'flow state' (designers and programmers will understand). It's the project management equivalent of "walking and chewing gum." Even if a dev team is quite skilled, focusing on both at the same time may mean that neither project is executed as well as desired, if they're completed at all.
2. Simultaneous projects allows for a dev team to practice different technical skills, different artistic mediums, differing themes and concepts. This is especially true when progress might otherwise stagnate if waiting on prerequisite work to complete, or if creative inspiration (whether coding or artistic) has faltered. If balanced properly, this can allow for extra work to get done and ultimately be more efficient. It might even provide new input into concurrent projects (innovations discovered in tech, new art skills or ideas) that improves the aggregate value.
At the end of the day it depends on the dev team, the particular criteria of the projects they're working on, how they work on those on those specific projects, how good their project management is, and how disciplined they are at holding or adapting their project plans. Too many dev teams try to be heroes, work miracles, and they crash and burn instead when a rational approach would have served them better.
TLDR;
Let's not get too eager about simultaneous projects unless the dev is very, very comfortable and reasonable with the notion and the plan.
Now with just one project I feel it is way harder for me to get out of a creativity mental blocking.