K
Kevin Slane
This is probably a pretty goofy question, but one that perplexes me
nonetheless.
If I have a simple project with 5 tasks, and assign myself as the resource
on all of them, why does MSP shove the first task all the way out (it's a
half day task) to the end of the project, then put the remaining tasks in
order?
If I add dependencies, then all the tasks show up in order from 1 to 5, but
the reality is, these tasks aren't actually dependent on each other. So,
without setting dependencies where they probably shouldn't exist, and without
setting start-no-earlier-than constraints on my tasks, how can I tell project
to just schedule all the tasks in order based on their ID order? I just
don't understand why it wants to have me start with task 2 and push task 1
all the way to the end.
nonetheless.
If I have a simple project with 5 tasks, and assign myself as the resource
on all of them, why does MSP shove the first task all the way out (it's a
half day task) to the end of the project, then put the remaining tasks in
order?
If I add dependencies, then all the tasks show up in order from 1 to 5, but
the reality is, these tasks aren't actually dependent on each other. So,
without setting dependencies where they probably shouldn't exist, and without
setting start-no-earlier-than constraints on my tasks, how can I tell project
to just schedule all the tasks in order based on their ID order? I just
don't understand why it wants to have me start with task 2 and push task 1
all the way to the end.