What is the preferred number of tasks to assign?
I am going to lead a small team for the first time in my career and I am determined to not subject my team to the same issues that I perceive to have been subjected to as a programmer.This question is about one such issue. Some managers that I worked with usually assigned one task at a time and assigned the next task only when I completed the task at hand. Some managers used to assign a few tasks at a time, along with their priorities and left me to tackle them in the order that I liked.I like the latter method, since it allows me to take a break and work on another task, if I hit a wall on any one task. But the managers who preferred the former method probably did so for a good reason.So my question is, how do I choose, as a manager, the right way of assigning tasks? If you feel your personal experience as a manager or programmer assigning or getting assigned tasks contributes to the answer, please share it.As an engineer I tried to look at it as a operations research problem, but I just want to ensure that if there is anything more to it, I don't overlook it.Thanks.