Capital construction projects are generally high-risk investments given the significant amounts of cash, complexity, stakeholders with conflicting interests, rules, and regulations to comply with, and duration that they span for. As a result of these challenges, project-level risks can easily become enterprise-level risks. The Project Management Institute (PMI) Pulse of the Profession® survey for the year 2020 revealed that an average 11.4 percent of investment is wasted due to poor project performance (pmi.org/learning/library/forging-future-focused-culture-11908).
Senior executives, whether at private sector or public sector organizations, have the responsibility to exercise their duties to enforce corporate as well as project governance. Project governance is defined as the collective business framework used to plan and deliver all commercial and technical aspects of the capital project. It will become the basis for making informed decisions, underpinned by strategic insight and effective risk management.
The Stage Gate Review Process is a formal project life phase-driven go/no-go decision point where selected project deliverables for each stage are reviewed to ensure that the organization’s requirements are met which are a requirement to enforce project governance. Project Management Information Systems (PMIS) like PMWeb include the Stage Gate Review Process as well as the many other business processes of control, oversight, and assurance over the selection, development, and execution of capital projects to ensure a transparent, accountable, and auditable project delivery environment.
PMWeb stage gate module will be used by each organization to identify the project life cycle stages along with their needed details such as the stage gatekeeper, duration of the stage, the project schedule activity it relates to, among other details. In addition, all stage deliverables needed for the successful completion of each project life cycle stage will be also defined. For each stage gate deliverable, PMWeb allows capturing the PMWeb business process used to create the deliverable, the link to the documents that details the deliverable if it was not generated from a PMWeb business process, Work Breakdown Structure (WBS) level, and project schedule activity associated with the deliverable, duration, start and finish dates, responsibility, and other needed information. Additional user-defined fields can be added to the stage gate header as well as the stage gate deliverables if this was needed.
For stage gate deliverables that need to be linked to deliverable documents, whether those were generated by a PMWeb business process or not, it is highly recommended that the PMWeb document management system repository filing structure is aligned with the stage gates and stage gate deliverables. Folders will be created to map the project life cycle stages while subfolders will be created to map the deliverables of the stage gate.
This will enable the organization to upload and store the deliverables’ documents under their designated subfolder. Access permission rights can be added to each folder and subfolder to restrict access. In addition, all versions of each deliverable document will be captured with the option of showing the latest version only.
In addition, PMWeb allows linking each stage deliverable with its relevant business process managed in PMWeb. PMWeb comes ready with most of the common business processes needed to manage the delivery of capital construction projects.
These include for example the project schedule, cost estimates, project budget, procurement bid packages, awarded contracts, change orders, progress invoices, risk register, meeting minutes, submittals, risk registers, prequalification, organization chart, resource requirements, among others.
In addition, links can be also added to newly created business processes using PMWeb visual custom form builder. Those could include the project business case, project charter, scope management plan, stakeholder requirements, testing and inspection checklists, communication management plan, environmental impact analysis among many others.
For each business process, PMWeb allows attaching all relevant supportive documents, whether those were stored in the PMWeb document management repository or not as well as add links to transactions of other business processes that are relevant to the stage deliverable transaction.
To enforce transparency and accountability when executing those business processes, PMWeb allows assigning a workflow for each process. The workflow will map the submit, review ana approve tasks as well as the duration for each task, responsibility to perform the task, others who need to be copied on the task as well as available review actions to be taken for each task. The workflow can be also designed to incorporate the approval authority levels needed for most cost-related business processes.
If there is a requirement to attach the output form of a specific business process transaction to the stage deliverable, then this is also possible. Although PMWeb comes ready with the output forms for most of the ready-to-use business processes, nevertheless, it also possible for the organization to design their output form using their own branding and formatting requirements. For example, the output form shown below is for the interim payment certificate (IPC) form.
If the requirement was more of a report or a register of the different transactions of a specific business process like for example, the change order register, then PMWeb provides the option to generate this report. The report which will be linked to the stage gate deliverable can be designed in any desired form or format.
Additional reports can be also designed to summarize closely interrelated business processes like for example those of awarded contracts, change orders and interim payment certificates displayed above with other business processes needed to provide a comprehensive understanding of one of the project’s management areas, like for example the project’s commercial management. This would require combing the budget and budget adjustments and transfers with the awarded contracts, change orders, and interim payment certificate processes. The project’s commercial status report shown below provides an overall summary of the project’s financial status to date. The reader of this report can drill down for more details if needed.
When the deliverables of a specific project life cycle are completed, then the stage gatekeeper along with the assigned committee will assess the stage to determine whether the project can proceed to the next stage, conditional proceed, put the project on hold or cancel the project. This will be done using a predefined weighted score list for which each item needs to be scored.
Knowing that the value of the personal feedback of those project team members that were involved in the project life cycle stage, PMWeb also allows rating each stage on a scale of 5. The project team members who will be involved in this non-formal rating need to provide the reason for their given score value. The gatekeeper can decide on which ratings to consider in the assessment.
All comments made by the gatekeeper and the committee who were involved in the stage assessment will be captured in PMWeb notes. Those notes will be time and date stamped along with who has provided the input.
Similar to all other business processes managed in PMWeb, a workflow will be assigned to the stage gate to capture the review and approval tasks. The workflow will map the submit, review ana approve tasks as well as the duration for each task, responsibility to perform the task, others who need to be copied on the task as well as available review actions to be taken for each task. The workflow can be also designed to incorporate the approval authority levels needed for most cost-related business processes.
The stage gate review data as well as the data from other business processes like those of budget, budget requests, awarded contracts, change orders, claims, interim payment certificates, actual payments made, baseline and updated project schedule among others will become the basis for generating the project life cycle stage gates status report. Since the data of the different business processes needed to generate the deliverables are managed in PMWeb, the data from all related transactions will become available to be reported on in any desired form and format.
The organization can also have a dashboard to summarize the performance status of their complete projects’ portfolio. The dashboard would usually include a map to show the location of those projects which could be in a single country or across the globe. Similar to all other reports in PMWeb, the dashboard reader can drill down to the performance dashboard of a single project where he/she can keep drilling down until they reach the business process transaction that provided the reported information.
The projects’ portfolio dashboard could have been designed to include graphical visuals to summarize the reported projects’ performance as well as add filters to enable selecting the projects to be viewed in the dashboard. All those customizations and designs will be done to fulfill the reporting requirements of executive stakeholders.
