i got a suggestion for your project. Instead of clicking a team member to make it work on a task, what if you have to manage the size and priorities of the lanes, and the other aspects of your production.
the biggest problem that i see now is that you have to do 2 kinds of managment, making people work, and making the flow of work effective.
by eliminating the first one you are simulating a little better how a dev shop should work.
with this approach your devs would work on the projects based on their priority, but would stop if there too much stuff queued in test, the founder would be finding new projecst only if there's enought capacity for the devs , if not it can concentrate on other tasks. Late projects will cost you money so it doesn't make sense to have them in queue. you could also add that the team member time can cost you money.
