I missed this post the first time around and only decided to respond after seeing your other article today on finding the longest Critical tasks.
Overall I believe your article presents a perfect example of the fundamental inability of MSP users – even supposed experts – to correctly analyze a logic-driven schedule. The primary reason for this is the user community’s reliance on Total Slack as the sole indicator of a given task’s “criticality” or its inclusion on a particular logical path – all while continuing to use constraints, deadlines, and variable calendars.
(I wrote a lot more but it won't fit here, so I made it a blog entry.)
Member for
18 years 11 monthsHi Emily,I missed this post
Hi Emily,
I missed this post the first time around and only decided to respond after seeing your other article today on finding the longest Critical tasks.
Overall I believe your article presents a perfect example of the fundamental inability of MSP users – even supposed experts – to correctly analyze a logic-driven schedule. The primary reason for this is the user community’s reliance on Total Slack as the sole indicator of a given task’s “criticality” or its inclusion on a particular logical path – all while continuing to use constraints, deadlines, and variable calendars.
(I wrote a lot more but it won't fit here, so I made it a blog entry.)
http://www.boyleprojectconsulting.com/TomsBlog/2015/08/21/monitoring-near-critical-tasks-in-microsoft-project/