Scientific Endeavours (EF 1120) as standard practice carries out a thorough review of the technical documentations for the project regarding Safety / Fitness for purpose, the underlying assumptions / constraints, Completeness as well as consistence with available technology. The results of that review in negotiations with their originator(s) are fed into the final form of the technical documentations. The Scope management process (in full cognizance of those comments of the technical review exercise), is used to reconcile the Cost estimate as developed in the bills of quantities (where one already exists): otherwise a completely new bill of quantities is developed from scratch using comments/ recommendations of the technical review report.
That way the gaps that could have manifested in the technical and financial plans are closed (or at least greatly minimized); and indeed is the minimum initial “intervention” to qualify the baseline information whence other project plans are developed.
The Change management Criteria is also established here; thereby setting the framework for decision-making in balancing the project objectives as the product evolves.
Subsequently a detailed resource-driven Schedule plan is developed using the contractor’s method statement, thereby providing a strategy that enables managing across the true critical path. Other plans such as Cash flows (derived from inputting the project costs into the schedule plan), Quality control plan, Communications plan and Procurement plans etc follow suit (See summary of Project Management Process groups Deliverables).
Scientific Endeavours’ project leadership derives from nearly fifteen years of consistent and proven project management service delivery, coupled with over twenty five (25) years of consistent engineering practice. Our Principals & Associates are people with a high numeracy / computational background along with other connected skills. Thus resulting in no than 60% of our commissioned projects (averaged over the years 2004 to 2014). being delivered below budget, and 83.5% of projects managed from 2009 to 2012 delivered within budget.
We recognize a diversity of needs as much as there are diverse challenges in project delivery; therefore we created Customized solutions / Entry points (by no means an exhaustive list) for the generic / typical challenges encountered. However we still want to hear from you regarding that peculiar project delivery challenge
Figure 1 gives a broad outline of the process groups’ interaction from Initiation through Planning to Execution through Monitoring / Controlling and finally to Closing for application to a typical project
S/N | Phase | Essential Activities | Specific PM Deliverables |
1 | Initiation | – Project feasibility – Formal authorization – High-level project definition | – Project Scope Statement |
2 | Planning | – Define all activities and resources – Establish schedules – Develop other plans | – Work Breakdown Structure (WBS) – Scope verification – Scope control – Responsibility Assignment Matrix – Change Management Control – Technical Risk Assessment (designs for safety, underlying assumptions, possible value-engineering, coordination of technical details with feedback integrated into final documentation) – Cost Estimate (Bills of Quantity) – Schedule Estimate (detailed resource-driven work program in MS Project 2010 using contractor’s method statement and acceptable logic) – Project Cash Flow (from schedule plan and cost estimate) – Quality Control Plan – Project Organization / Authority structure |
3 | Executing | – Execute the project management plan | – Minutes of meetings |
4 | Monitoring / Control | – Monitor all project activities and processes – Control all changes and change-causing factors | – Configuration management – Progress reports (bi-weekly or other suitable time slices) – Monthly report (capturing progress of activities, expenditure profiles, cost performance, earned values, look-ahead plans, cash flows, etc.) – Updates to program schedule – Re-planning as needed due to logic, scope, or other project changes – Periodic financial statements |
5 | Closeout | – Formally close the project | – Pre-handover report – As-built drawings – Final accounts – Completion certificate |
This section outlines three customized solutions or entry levels for project management services depending on client preference or the status of the project:
This represents the ideal involvement of the project manager throughout the project lifecycle, as summarized in the process groups’ interaction chart. The project manager participates from the initiation stage (rather than being brought in only after contract award to draw up a work program and monitor progress, with poorly articulated risks) and continues through planning, execution, monitoring/controlling, and closing.
During execution, the Project Manager will:
During monitoring and controlling, the Project Manager will:
This scenario involves the project manager “jumping into” an ongoing or distressed project.
Given the emergency nature of such situations, planning efforts will involve backward integration of project definition. The project scope definition (or Statement of Work, SOW) is first documented based on assumptions and information from the existing contract documents.
Key steps include:
The Project Manager is responsible for:
This solution provides professional guidance and support to existing project teams in the following areas:
(Regardless of size or complexity)