I would not want a project (as opposed to the next task within the
project) on my to-do list. My to-do list should be filled with tasks
that are ready to go, all the planning and analysis completed, all
the prerequisites met, what might be called shovel-ready. When I
start to work on the to-do list, my objective is to spend nearly all
of my time actually getting things done. If I encounter the next
task of a project at the top of my to-do list, my objective is to do
an efficient and effective job of completing it as soon as possible.
If I cannot do it now, that means that the task's contexts,
dependencies, flags etc. need to be adjusted. Once the task is
completed my objective will be to mark the task completed and begin
work on the next task.
If I were to encounter a project task with uncompleted subtasks at
the head of my to do list, I do not know what I should do. The most
meaningful thing I can think of would be to work on the next
uncompleted subtask. And that's what MLO does for me. It hides the
project task as long as it contains incomplete subtasks
-Dwight