Warning: Declaration of Jetpack_IXR_Client::query() should be compatible with IXR_Client::query(...$args) in /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719

Warning: Cannot modify header information - headers already sent by (output started at /home/projec94/public_html/wp-content/plugins/jetpack/class.jetpack-ixr-client.php:91) in /home/projec94/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1719
{"id":342,"date":"2011-04-05T10:27:24","date_gmt":"2011-04-05T15:27:24","guid":{"rendered":"http:\/\/projectprofessionals.org\/?p=342"},"modified":"2011-04-05T10:27:24","modified_gmt":"2011-04-05T15:27:24","slug":"managing-risk-of-delay-%e2%80%93-as-planned-schedule-accepted-programme-part-3","status":"publish","type":"post","link":"http:\/\/projectprofessionals.org\/2011\/04\/05\/managing-risk-of-delay-%e2%80%93-as-planned-schedule-accepted-programme-part-3\/","title":{"rendered":"Managing Risk Of Delay \u2013 As-Planned Schedule \/ Accepted Programme (Part 3)"},"content":{"rendered":"

This post is the third in a series of discussions regarding various aspects of time management.\u00a0 More specifically, we have titled the series MANAGING RISK OF DELAY, since we focus heavily on the managerial aspects of program \/ project management.\u00a0 This post addresses some ideas regarding the time management baseline.<\/p>\n

Introduction<\/h3>\n

A Critical Path Management (CPM) plan and schedule (programme) is one of the most fundamental managerial tools used in professional project management.\u00a0 It reflects (hopefully) the intention of the lead or prime contractor regarding project execution.\u00a0 Further, it reflects (again, hopefully) the intentions of all key stakeholders, including the owner (owner, developer, employer).<\/p>\n

Ideally, this meeting of the managerial minds can be achieved and documented through a schedule approval process.\u00a0 Again ideally, the detailed schedule would be developed in a timely fashion and submitted to the owner.\u00a0 Once revisions and improvements have been achieved, the owner would approve this tool.\u00a0 Once approved, this baseline schedule would form the as-planned schedule (or accepted programme, as termed in United Kingdom).<\/p>\n

An issue arises when the contractor fails to submit a suitable schedule and\/or the owner refuses to approve a suitable submission.<\/p>\n

Cases<\/h3>\n

In one case, the contractor submitted a proposed CPM schedule; however it did not conform to the contract time provisions and requirements.\u00a0 The owner (rightfully, by most standards) refused to issue an approval.\u00a0 The parties then proceeded without resolution of this key baseline matter.\u00a0 Ultimately, when time-related disputes arose, the contractor was unable to demonstrate a cause and effect relationship under the contract provisions.\u00a0 This unfortunate situation precluded the contractor from prevailing on an otherwise legitimate time-related claim against the owner.<\/p>\n

In another case, the contractor prepared and submitted a (seemingly) legitimate schedule in a timely manner.\u00a0 The owner replied with some comments and requests; but, failed to take action regarding approval or disapproval.\u00a0 The parties proceeded to use (essentially) the submitted schedule and updates for managerial purposes including replanning and resolution of issues.\u00a0 This platform provided the contractor a tool for use in preparing time-related claims.<\/p>\n

Conclusions \/ Lessons Learned<\/h3>\n

The message and the conclusions regarding schedule submission and approval are summarized in the following recommendations:<\/p>\n