Deadlines are a great feature in Microsoft Project. Here's how they work http://ow.ly/Bgfs302zHP0
Microsoft Project and Deadlines
Featured Partner
Top Posters
Zine Eddine
2 posts
Alex Lyaschenko
27 posts
mxsiegel
0 posts
Mattvtek
0 posts
Gareth Evans
3 posts
PP Admin
3, 129 posts
Rajkamal Tangirala
5 posts
Rahul Kumar
1 posts
blake333_
0 posts
Jeamiell Ostrovsky
2 posts
Our Partners
Emily,
To add to the elementary discussion of your article:
There are two main advantages to using a Deadline instead of a Finish-No-Later-Than constraint in MSP:
In every practical respect, Deadlines in MSP function identically to Finish-on-or-Before constraints in P6. That is, they override the late-finish dates in the absence of more stringent conditions, and Total Slack is reduced as a consequence.
Unfortunately, your article seems to invite the novice scheduler to use Deadlines willy-nilly without fear of complications, and this is wrong. Imposing multiple deadlines "throughout the schedule" as you suggest in the final paragraph makes Total Slack completely unreliable as an indicator of the Driving Path to Completion -- of the Project or of any deadlined milestone. Since MSP defines "Critical" tasks solely based on Total Slack, your novice scheduler may be hard-pressed to accurately describe where the real "Critical Path" is.
For these reasons - and for your mention of "longest path", which is a concept that is distinctly foreign to any out-of-the-box MSP schedule - I would suggest deleting your "Summary" paragraphs and starting over. In my view, Deadlines in MSP are essentially not a huge advantage - but a patch needed to offset weaknesses in other areas of the tool.
By the way, all of these issues are easily resolved with a 3rd-party add-in that I use, but very few MSP users seem to have access to similar tools.
Rgds, tom