D
Dave W
You use multiple critical paths when you have multiple subprojects. For a
single project, there should be one critical path.
single project, there should be one critical path.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
J
Jan De Messemaeker
Hi Anton,
In response to your first question, how does MSP choose?
When Multiple Critical Paths is on, every task without successors is
considered critical, whether itis the final one of teh project or not, and a
critical path is calculated backward from each one of these.
Without this option, only the final task without successors is necessarily
considered critical.
HTH
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620
In response to your first question, how does MSP choose?
When Multiple Critical Paths is on, every task without successors is
considered critical, whether itis the final one of teh project or not, and a
critical path is calculated backward from each one of these.
Without this option, only the final task without successors is necessarily
considered critical.
HTH
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620
J
Jan De Messemaeker
Yes.
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620
S
Steve House
And IMHO, you shouldn't ever have tasks without successors except for the
finish milestone. Since the project isn't finished until the last task in
it is done, even the last task in any chain of events would have the overall
Project Finished milestone linked to it as a successor if nothing else. All
chains would converge there and so every possible path through the project
would have that same final last milestone at its end.
Steve House
MS Project MVP
finish milestone. Since the project isn't finished until the last task in
it is done, even the last task in any chain of events would have the overall
Project Finished milestone linked to it as a successor if nothing else. All
chains would converge there and so every possible path through the project
would have that same final last milestone at its end.
Steve House
MS Project MVP
E
Ed Hanna
Steve,
Don't be so humble about your opinion. There are lots and lots of people trying to use MS Project that need to hear what you have said about "network integrity". Many of the ills reported in this newsgroup would simply go away if people took a little time to understand this issue (i.e. the network logic has to be complete--and sound, else the schedule is worthless).
I've seen some big (3,000 tasks) networks which have been composed of 90% orphan tasks (i.e. no predecessor and no successor). These were in big--seemingly sophisticated--aerospace companies and they were managed by full-time, professional "schedulers". As I tell my project management students, if that's the way you intend to use MS Project, you might as well use a pencil and paper--because all you have is a checklist of tasks.
One quick and simple sanity check on any schedule, as you have mentioned, is to open the Network Diagram and see if you have a continuous critical path (red) that is traceable from the first task in the network to the last task in the network. A large percentage of the in-use projects out there today would fail that quick and simple sanity check. Yet people are relying on these schedules! It's no wonder that project failure rates are so high.
Keep spreading the message. I'll do the same.
Ed Hanna
DXI Management Consulting
Irvine, CA
Don't be so humble about your opinion. There are lots and lots of people trying to use MS Project that need to hear what you have said about "network integrity". Many of the ills reported in this newsgroup would simply go away if people took a little time to understand this issue (i.e. the network logic has to be complete--and sound, else the schedule is worthless).
I've seen some big (3,000 tasks) networks which have been composed of 90% orphan tasks (i.e. no predecessor and no successor). These were in big--seemingly sophisticated--aerospace companies and they were managed by full-time, professional "schedulers". As I tell my project management students, if that's the way you intend to use MS Project, you might as well use a pencil and paper--because all you have is a checklist of tasks.
One quick and simple sanity check on any schedule, as you have mentioned, is to open the Network Diagram and see if you have a continuous critical path (red) that is traceable from the first task in the network to the last task in the network. A large percentage of the in-use projects out there today would fail that quick and simple sanity check. Yet people are relying on these schedules! It's no wonder that project failure rates are so high.
Keep spreading the message. I'll do the same.
Ed Hanna
DXI Management Consulting
Irvine, CA
S
Steve House
Thanks - BTW, I'm sure you know (but some other readers might not, hence my mention of it) in MS Project it is possible to have the critical path pick up in mid-stream, as it were, if there is a constraint such as a SNET date on a task such that everything that comes before it has some non-zero amount they could be delayed before the constrained task gets pushed back. Another good reason for avoiding using constraints unless they really, truly, represent external conditions that the schedule must obey.
Steve,
Don't be so humble about your opinion. There are lots and lots of people trying to use MS Project that need to hear what you have said about "network integrity". Many of the ills reported in this newsgroup would simply go away if people took a little time to understand this issue (i.e. the network logic has to be complete--and sound, else the schedule is worthless).
I've seen some big (3,000 tasks) networks which have been composed of 90% orphan tasks (i.e. no predecessor and no successor). These were in big--seemingly sophisticated--aerospace companies and they were managed by full-time, professional "schedulers". As I tell my project management students, if that's the way you intend to use MS Project, you might as well use a pencil and paper--because all you have is a checklist of tasks.
One quick and simple sanity check on any schedule, as you have mentioned, is to open the Network Diagram and see if you have a continuous critical path (red) that is traceable from the first task in the network to the last task in the network. A large percentage of the in-use projects out there today would fail that quick and simple sanity check. Yet people are relying on these schedules! It's no wonder that project failure rates are so high.
Keep spreading the message. I'll do the same.
Ed Hanna
DXI Management Consulting
Irvine, CA
Steve,
Don't be so humble about your opinion. There are lots and lots of people trying to use MS Project that need to hear what you have said about "network integrity". Many of the ills reported in this newsgroup would simply go away if people took a little time to understand this issue (i.e. the network logic has to be complete--and sound, else the schedule is worthless).
I've seen some big (3,000 tasks) networks which have been composed of 90% orphan tasks (i.e. no predecessor and no successor). These were in big--seemingly sophisticated--aerospace companies and they were managed by full-time, professional "schedulers". As I tell my project management students, if that's the way you intend to use MS Project, you might as well use a pencil and paper--because all you have is a checklist of tasks.
One quick and simple sanity check on any schedule, as you have mentioned, is to open the Network Diagram and see if you have a continuous critical path (red) that is traceable from the first task in the network to the last task in the network. A large percentage of the in-use projects out there today would fail that quick and simple sanity check. Yet people are relying on these schedules! It's no wonder that project failure rates are so high.
Keep spreading the message. I'll do the same.
Ed Hanna
DXI Management Consulting
Irvine, CA
A
anton
Greetings,
How does MSProject calculate multipe paths? If I dont choose multiple paths
in options, which path will MSProject display? Since default is not to
indicate multiple paths, when should one use multiple paths?
Thanks
Anton
How does MSProject calculate multipe paths? If I dont choose multiple paths
in options, which path will MSProject display? Since default is not to
indicate multiple paths, when should one use multiple paths?
Thanks
Anton
A
anton
Hello Jan,
Assuming I dont have tasks without successors (except the last), then it
doesnt make any difference whether the option is on or off. Am I coorect?
Thanks
Anton
Assuming I dont have tasks without successors (except the last), then it
doesnt make any difference whether the option is on or off. Am I coorect?
Thanks
Anton
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.