but what exactly is the dcma 14-point schedule assessment checking?<\/p>\n
well, essentially it’s evaluating whether a schedule is well-built – whether it adheres to a set of best practices considered important to the success and manageability of a project. these best practices are broken down into a list of 14 checks<\/p>\n
1) checking the logic<\/h2>\n
are is the logic complete? are there missing links. we all know that a schedule is a network, and if that network is not complete because of missing logic, an accurate critical path<\/a> is not possible.<\/p>\n negative lags are often referred to as “lead time”. negative lags can cause all sorts of problems. plus they can be confusing. here, the goal is to have no negative lags in your schedule<\/p>\n the dcma is a bit more forgiving when it comes to positive lags, but the goal here is to minimize their use in your schedule. the goal is no more than 5% of relationships should have a lag. here’s how you might find those lags<\/a>.<\/p>\n p6 and other software supports 4 relationships types, but that doesn’t mean you should build a schedule using only start-start relationships. finish-start is best. dcma says your schedule should use finish-start 90% of the time (or more).<\/p>\n2) looking for leads<\/h2>\n
3) looking for lags<\/h2>\n
4) the right relationship types<\/h2>\n
![\"new](\"https:\/\/no-cache.hubspot.com\/cta\/default\/297539\/12925452-f389-44a1-917c-6576cc060240.png\")
<\/a><\/span>