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 | PROCESS GROUP | ESSENTIAL ACTIVITIES | SPECIFIC PM DELIVERABLES |
1 | Initiation |
.Project feasibility, Formal authorization, High level project definition |
Project Scope Statement |
2 | Planning |
Defines All activities & Resources, Establishes Schedules, & 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, & co-ordination of technical details with remarks fed back into final documentations), 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 (Generated from the schedule plan, using Cost Estimate), Quality Control Plan, Project Organization / Authority structure |
3 | Executing | Execute the project management plan |
Minutes of meetings, Configuration management |
4 | Monitoring / Control |
Monitors all project activities & processes,
Control all changes and change-causing factors |
Progress Reports (bi-weekly or other suitable time slices) Monthly report, (Encapsulating progress of activities, expenditure profiles, cost performance, earned values, Look-ahead plans, cash flows, etc.), Up-dates to program schedule, re-planning subsequent upon logic, scope, or other project changes) Periodic Financial statements,
|
5 | Closeout | Formally close the project |
Pre-Hand over the report, As-built drawings, Final Accounts, Completion certificate |
This section outlines three Customized solutions or Entry levels for the project management services depending on client preference or status of project;
This is the quintessential involvement of the project manager on a typical project, with functions summarized in the process groups’ interaction chart.
Beginning from the onset or Initiation processes (not the traditional “plug-in” at the conclusion of contract award, where he is “only required to draw up a work program and report on progress” for the project, and Risks that have not been properly articulated), through Planning processes, to Execution processes, to Monitoring / controlling processes, to Closing out processes.
His specific duties within each process groups are expounded as follows;
Here the project manager is responsible for providing & documenting the High-level description of the project using the Project scope statement or Statement of Work (SOW). He also carefully considers the general strategy and technology for the evolution of the project at this stage and ensures that it is aligned with the strategic plan.
Next defines the Work Breakdown Structure (WBS), Establishes responsibilities using the Responsibility Assignment Matrix (RAM), and defines the Change Management Criteria in tune with the client’s requirements.
Finally, he carries out some form of risk identification and assessment whose impact will be reflected in the technical documentations for the project.
Here the Project Manager defines all activities and resources and establishes schedules and other plans such as:
The Project Manager executes the project management plan by;
He also monitors/controls the project activities by;
This scenario involves the project managers “jumping into” an ongoing or distressed project.
Given the “emergency” of these situations, planning efforts will involve a backward integration of project definition. The project scope definition (or SOW) is first documented from the assumptions & content of the existing contract documents.
This is achieved by gathering information on the status of activities carried out thus far, a Work Breakdown Structure (WBS) that outlines outstanding activities to completion can then be developed.
A quick review of general strategy and technology is required at this stage to ensure alignment with strategic plans. Establishing the RAM and defining the Change Management Criteria complete the Initiation process.
Now that the WBS (for outstanding activities to completion) has been established,
Risk assessment of all technical documentations must be carried out, and the implications integrated into these documents and circulated to all stakeholders.
Subsequently, the following activities must be executed;
Activities here proceed as in the execution processes of scenario I. The Project Manager directing/ managing construction activities, gathering information on project activities, and measuring overall project performance using Earned values techniques, by imputing actual experience against baseline plan.
Other functions include;
(Regardless of size & complexity) featuring;
Detailed resource – driven schedule plans,
Materials Scheduling,
Cash flows (variable time slicing),
Pert Chart, Gantt Chart, Calendar view presentations (A3 – A0 formats).
Updates to Schedule plans (progress, resource usage etc.),
Status reporting (% completions, time loss, earliest completion dates, earned values etc.),
Re-planning consequent upon changes to method statements / activity logic,
Expenditure / Cost updates on periodic basis.