Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Monitoring Near Critical Tasks in Microsoft Project 2013

1 reply [Last post]
Emily Foster
User offline. Last seen 1 year 43 weeks ago. Offline
Joined: 19 Aug 2011
Posts: 625
Groups: None

Monitoring your near critical activities can be, in some schedules, as important as the critical ones. Here we describe how to create a filter, so you can easily view near critical tasks in your Microsoft Project 2013 schedule  http://ow.ly/IcII3

Replies

Tom Boyle
User offline. Last seen 4 days 52 min ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

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/