Jonathan ClayChange Manager| Close Brothers Motor FinanceLeeds, West Yorkshire, United Kingdom
I am looking for an example to put into a presentation. Can anyone suggest an example I can put into a slide? I am looking for examples to demonstrate impacts of changing the triple constraint.
Recently I had project that require to crash the schedule. I managed a server migration project from a loaner server to a brand new server. The date for returning the loaner server cannot change but my deliverable date for the brand new server was delay. Those impacted the application testing on the new server timeline. Therefore I need to crash the schedule in order to complete the application testing before I can do production server migration.
Hope this will help you. Saving Changes...
saurabh mahajanPMP, ITIL, PRINCE2| vodafonePune, Maharashtra, India
We had scheduled delivery of 6 major management reports. But due to technical hurdles there was a delay in starting with the first report itself. In that situation I had to crash the schedule to prepare and publish all 6 reports on time. Saving Changes...
Darren KosaPlanning & Controls ContractorHampshire, United Kingdom
Hi Jonathan,
Due to development delays, the verification and validation activities were firmly on the Critical Path.
In order to meet the baseline delivery date (Time), the project manager approved the use of overtime for the test team (Cost), to ensure all the requirements (Scope) would be able to be tested and accepted.
Regards,
Darren Kosa Saving Changes...
Ayman Omar AtallahDeputy Project Control Manager| Consolidated Contractors CompanyDoha, Qatar
A frequent example that usually happens in Oil and Gas Construction sector, where several delays occur on the engineering and procurement deliverables of the project. Consequently, construction contractor should develop a crash schedule in order to meet the contractual completion dates set earlier with less time. Therefore, acceleration is required by mobilization additional resources to complete The "Scope" with less "Time" but at Higher "Cost". Saving Changes...
