Auditable Categories
Auditable Category |
WBS ID and Item Description |
Applicable metrics |
||
1. |
Performance / Progress |
1 |
Obtain the relevant drawings and designs for the building |
Developed on schedule / Time |
Within budget constraints |
||||
2 |
Project being executed as per the project schedule |
Within budgetary constraints |
||
Within time constraints |
||||
3 |
Project execution is within the scope |
Number of scope change requests |
||
Number of approved/ rejected scope requests |
||||
4 |
Resource utilisation in project execution |
Number of people having to be added / removed in relation to project execution |
||
Additional financial/ time resources requested to execute project |
||||
Actual resource utilisation versus projected/ budgeted resource utilisation |
||||
2. |
Compliance |
1 |
Obtain the requisite permits and approvals from local authorities |
Done within time |
Done within budgetary constraints |
||||
2 |
Project being executed according to applicable safety and health standards for workers at the workplace |
Work place health and safety document |
||
Number of reported incidences related to workplace health and safety |
||||
3 |
Adherence to applicable building codes and standards |
Flags raised for non compliance |
||
Number of requests for scope changes |
||||
3. |
Quality |
1 |
Quality management plan has been developed |
Quality plan and version |
Changes/ updates to the project quality plan |
||||
2 |
Materials used are of the highest/ desired quality standards |
Materials such as concrete mixes tested for quality (stress and strength tests) and passed test based on building and construction standards |
||
Stated period of time allowed for materials setting/ curing |
||||
3 |
Project being executed within scope and quality objectives |
Number of requested scope changes |
||
Approved scope changes |
||||
4 |
Scope management |
Number of reworks done during construction |
||
4. |
Change / Exit |
1 |
Scope management plan document developed |
Number of changes to he current scope document version |
Change requests in the scope document |
||||
2 |
Project being executed according to the project schedule and scope |
Current progress versus project schedule |
||
Additional tasks added / removed as the project is being executed |
||||
5. |
Risk |
1 |
Risk management document developed |
Version of risk management plan |
Roles and responsibility allocated for risk management |
||||
2 |
Risk management plan |
Number of identified risks |
||
Risk profile developed |
||||
3 |
Risk treatment and evaluation |
Risk treatments identified to mitigate/ manage risks |
||
Risk treatments applied to risks |
||||
4 |
Continuous monitoring of risks |
Effects of risks treatments evaluated |
||
New risk profile (likelihood and severity) developed after risk treatment |
||||
Continuous monitoring and updating of risks and the risk document |
||||
6. |
Best Practices / Lessons to be Learned |
1 |
Project report and documentation |
Number and types of project documents created and used |
Number of updates to project documents/ versions |
||||
2 |
Project execution reviews during milestones |
Number of project reviews done during project execution |
||
Project review document |
||||
3 |
Communications and stakeholder management and project execution inspections |
Number of times communications made with stakeholders |
||
Feedbacks obtained from project construction inspections |
Audit Category |
Item |
When will it be conducted? |
Who will conduct? |
Purpose (discovery or decision-making)? |
Performance / Progress |
1 |
Before seeking approvals |
Architect and civil engineer/ Construction quality management team |
To determine whether the plans for the construction comply with legal requirements and standards Ensure plan consistent with intended use and within budget |
2 and 3 |
Every fortnight |
Project manager |
Ensure the project is running within schedule and constraints or time and budget |
|
4 |
Every fortnight |
Project manager and project accountant |
Ensure the resources are being used efficiently and determine current resource utilisation state |
|
Compliance |
1 |
Weekly |
Project manager |
Ensure permits provide to have the go ahead to initiate project |
2 |
Weekly |
Project manager |
Ensure compliance with work place health and safety standards Ensure no injuries or adverse effects to employees due to working on the project |
|
3 |
Fortnightly |
Project manager |
Ensure the building meets applicable quality and safety standards |
|
Quality |
1 |
Every two weeks |
Project manager |
Ensure quality plan being implemented |
2 |
Every week |
Project manager |
Ensure the materials used give value for money and are of the right specified quality |
|
3 and 4 |
Every week |
Project manager, project team |
Ensure project being executed within scope and effectively manage scope changes |
|
Change / Exit |
1 |
Every two weeks |
Project manager |
Monitor and approve changes to project scope |
2 |
Every two weeks |
Project manager |
To tightly manage and control project scope |
|
Risk |
1 |
Every four weeks |
Project manager/ risk management team |
Verify accuracy of the risk management document/ approve changes and editing to the risk management document |
2 and 3 |
Every week |
Project manager/ risk management team |
Identify and monitor risks and treatments given to risks, as well as their effects |
|
4 |
Every week |
Project manager/ risk management team |
Continuous monitoring of project risks |
|
Best Practices / Lessons to be Learned |
1 |
At completion of the project |
Project manager |
Develop overall project report and document issues and incidences for future reference |
2 |
At the end of every project stage |
Project manager |
Document incidences and issue and review project progress and work done so far |
|
3 |
Every week |
Project manager |
Ensure the support of executive project sponsor and keep stakeholders informed and involved in the project |
|
Controllable Category |
Item & Explanation |
PMBOK Knowledge Area |
||
Input |
Tool & Technique |
Output |
||
1. Deliverable |
1.1 |
Project objectives |
Final deliverable analysis |
Verified deliverables |
The final project that is delivered meets the initial project objectives, including that the finished work follows the approved architectural plan |
||||
1.2 |
Scope verification |
Inspection |
Accepted project deliverable Requested changes and approved changes |
|
At the end of the project, the scope must be verified to be consistent with the scope plan document for the project and to verify scope changes and their approvals |
||||
1.3 |
WBS Dictionary |
Inspection |
Accepted project deliverables Recommended corrective actions |
|
The work breakdown structure is inspected to ensure that all the work tasks as detailed in the WBS were executed according to plan and meet the project objectives, otherwise, recommendations can be made for changes |
||||
2. Configuration |
2.1 |
Project baselines |
Product breakdown structure |
Baseline adhered to |
The baselines for the deliverable product is evaluated and specific procedures defined for application during its life cycle |
||||
2.2 |
||||
Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable. |
||||
2.3 |
Configuration control |
Inspections and quality audits |
Change requests made and change control |
|
This entails evaluating all requests for change made during the execution of the project, as well as proposals for changes and whether they were approved and disproved. This process entails evaluating control to the building design, materials used, changes proposed, and any documentation relevant to it |
||||
3. Status Accounts |
3.1 |
Project mission statement and objectives |
Inspection Evaluation of project reports CAD files for building design tests for materials |
Product baselines Approval status of documents Accepted changes |
The project deliverables and design specifications must be audited to ensure there are no variances with the delivered product, and if there are variances, then these were approved in change requests |
||||
3.2 |
Discrepancies in project |
Audits |
Status reports |
|
The configuration phase requires that all discrepancies identified between the original parameters such as design or materials be evaluated and the reasons for such discrepancies verified |
||||
3.3 |
Contractual agreements evaluation |
Audits Tracing all changes form project start to finish |
Contractual Performance Measurement |
|
The contractual agreement must be audited before the project is accepted to ensure all contractual and legal agreements are fulfilled, and in cases where this is not done, reasons given |
||||
4. Logs |
4.1 |
Change control logs |
Scope change document |
Authorised changes |
Change control is an important aspect of any successful project; the change control logs determine the level of changes to scope |
||||
4.2 |
Communications |
Communications plan |
Effective stakeholder communication |
|
The success of projects hinges very closely on how effective the communications plan with stakeholders was managed |
||||
4.3 |
Stakeholder management log |
Stakeholder communication |
Work performance information |
|
Stakeholder management must be effective for project success |
||||
5. Issues |
5.1 |
Risks |
Risk management plan |
Risk profiles |
Projects have inherent risks, at the end of the project, the risk management document is evaluated to see the inherent risks, experienced risks, risk treatments, and the outcomes of the risk treatments |
||||
5.2 |
||||
Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable. |
||||
5.3 |
||||
Write the explanation of the event driven control in this cell and delete this text afterwards. You may use as many words as you require but brevity and succinctness is preferable. |
||||
6. Procurements |
6.1 |
Procurement plan |
Procurement status document review |
Approved procurement Quality materials procured |
Procurement has a direct effect on project execution and budget and requires a detailed plan to evaluate if the procured items meet quality standards and the process used satisfies project objectives |
||||
6.2 |
Procurement documents |
Procurement audits Records management system Contract negotiations |
OPAs updates Closed procurements |
|
A project must have a plan for managing procurement, consisting of the planning, execution, monitoring, and control, and closing processes. Procurement closing and has documents that defines the financial and project information, useful for determining if guidelines set in the procurement plan have been adhered to and met |
||||
6.3 |
Product/ service quality |
Quality inspections Quality tests |
Acceptance criteria |
|
For a construction project such as this, the quality of materials are essential in ensuing overall product quality that meets laid down standards |
The governance for this project follows the PMBOK guidelines to provide the management framework for managing decisions within the project. This project has an executive sponsor, who in this case is the general manager and is the initiator of the project. The project sponsor was responsible for providing guidelines on what was required and for supporting the project to its logical conclusion. The project also has a business sponsor to ensure the business goals are aligned with project goals and objectives. A steering and advisory committee make up the project board to provide advisory services. A project manager is responsible for executing the project to meet the project objectives. The project governance framework is established by the executive sponsor and works with the board and project manager to define roles and responsibilities, while the project manager defines the stakeholder engagement framework. The governance entails planning and defining metrics, such as for risk management, executing the governance, monitoring and controlling, and closing assurance (Alie, 2015).
The project board has overall responsibility for the project. The project is considered successful when the project objectives are met and deliverables achieved within the project budget, time, and scope, with approved/ reasonable changes to the project scope. The project is accepted once all exit criteria as outlined in the controllable project termination elements and the executive sponsor accepts the project to satisfy their requirements. The overall responsibility for the success of this project is with the project manager
The roles, responsibilities and performance criteria for this project consist of identifying and involving senior managers/ stakeholders in the project (Roudias, 2015). This project has an executive sponsor at the apex of the project governance; the sponsor support the project and approves major changes to project scope, schedule, and financing and determines the deliverables for the project. The project also has a business sponsor that ensures the business needs for the organization are met through the execution of the project. The project has aboard to review changes and make some approvals, as well as ensure the project has the right personnel, and materials and equipment for its successful completion. The board will be the steering/ advisory committee and constitutes of a procurement manager, contract manager, human resource manager, and administrative and finance managers. The project then has a project manager in charge of overall project execution and meeting the project objectives and deliverables, the project manager works with a team responsible for various roles and helping the project manager successfully deliver the project. The project team and manager works with a team of contractors such as the main works contractors ad sub contractors including electrical and plumbing sub contractors. The organization chart is shown below;
2 Audit Plan
The governance arrangements for this project consist of a project board, that reports to the executive sponsor and work to ensure the project objectives are met. The board evaluates an reviews requests for changes and ensure that the business and financial objectives of the organization are met in executing the project. The project manager and the project team handle all project documentation and initiate any changes requests that are reviewed by the board and then approved by the executive sponsor, as recommended by Alie (2015).
The Relationship to the Portfolio for this project is a project strategy that is consistent with competitive strategies of the organization, including cost leadership, effective cost management, and organization of the project that is aligned with the organizational structure and culture of the organization; this is augmented by the organization adopting a project driven culture. The project process, culture, and tools are designed in such a way that the organizational goals of expansion and efficiency and accountability are met and fulfilled (Milosevic & Srivannaboon (2006).
The authorisation points for this project are;
The executive sponsor, who authorises the project initiation and changes for requests
The project board, that reviews any requests for changes, such as scope changes to the project
The project manager is responsible for reviewing and liaising with the project board and executive sponsor in evaluating change requests from the project team and ensuring the scope management document is duly updated and archived.
All issues raised by the project team or contractors are escalated to the project manager, who reviews them, creates the necessary documentation, such as scope change management document, and then forwards them to the project board for review. Once the project board reviews the issue or request for change, they make recommendations and forward it to the executive sponsor , who makes a decision whether to approve/ disapprove, or partially approve the issue/ request for change. Finally, once approved, the project manager documents the change and effects the change requests with the relevant persons. The project administrator is also responsible for conflict resolution, together with the project manager. The project manager guides the conflict resolution steps and processes to ensure the project runs smoothly; this forms part of the risk management strategy, according to the ‘Project Management Institute’, (2017)
The delegation arrangements for this project are that the executive sponsor is represented in the project team, while the board has representation trough the HR, procurement, and contract managers. All change requests are documented by the project manager and reviewed by the project board, while authorisation at all stages, including project initiation authorisation, budget authorisation, and acceptance of rejection of the delivered product is done by the executive sponsor. The project manager has an assistant to whom some duties are delegated, such as risk management and monitoring, and risk reporting.
Project Termination / Closure
The manner in which information validity for this project is assured is through the creation of various documents, including the risk management document, the quality management and control document, the scope management document, communications management document, among others (Hedeman, Vis Van Heemst, Fredriksz, & Newton,2012). Roles and responsibilities are assigned to persons responsible for the documentation. Each document will be stored in an electronic form, with a hard copy backup. Only authorised persons with rights to make changes will be allowed to alter or modify the project documents. Any changes must be done procedurally, with the authorised person making changes/ adjustments, with the date of change recorded and then signed; the version of the document will be updated based on the changes made. Some changes will require approval, such as scope changes; however, the persons responsible must sign off and have the document stored and archived. The documents will be retained as per the organizations’ retention policy for stored documents, for up to 7 years.
The scrutiny arrangements for this project are based on the project stages, where using the project schedule and the stages, inspections and assessments will be done, initiated by the board to ensure the project remains within scope and schedule. Further, periodic reporting will ensure the stallholders re kept abreast of the progress.
The status reporting for the project forms part of the overall communication plan for the project (Taylor & Dow, 2013). The project is executed using an agile process that requires documentation of activities and progress, and engaging the stakeholders through an effective communications plan that includes the method and frequency of communication. The project manager is responsible for all communication with stakeholders that includes giving status reports. These will be provided on a weekly basis through e-mail and memos, as well as during meetings with stakeholders. Documentation and document control will manage changes made to the project schedule and scope, and these must be approved by the project board and/ or the executive sponsor
The improvement arrangements for this project are for better budgeting process and to change the organizational culture to a project oriented organisation. This requires elaborate project reviews and engaging all stakeholders to give their views before initiating projects as part f an effective change management strategy
The stakeholder engagement arrangements for this project entails identifying the stakeholder and describing them, and then identifying their roles within the project, their level of influence on the project, and the methods that are used in engaging them (the stakeholder communication plan). The communication with the stakeholders is part of the overall communication plan and includes the frequency of communication, the mediums/ channels of communication, and the person(s) responsible for making the communication (Baugh, 2015)
References
Alie, S. S. (2015). Project governance: #1 critical success factor. Paper presented at PMI® Global Congress 2015—North America, Orlando, FL. Newtown Square, PA: Project Management Institute.
Baugh, A. (2015). Stakeholder engagement: the game changer for program management. Boca Raton, CRC Press, Taylor & Francis Group.
Hedeman, B., Vis Van Heemst, G., Fredriksz, H., & Newton, S. (2012). Project management based on PRINCE2®, 2009 edition. Zaltbommel, Van Haren Publishing.
Miloševic, D. & Srivannaboon, S. (2006). A theoretical framework for aligning project management with business strategy. Paper presented at PMI® Research Conference: New Directions in Project Management, Montréal, Québec, Canada. Newtown Square, PA: Project Management Institute.
‘Project Management Institute’. (2017). A guide to the project management body of knowledge: (PMBOK® guide). Newtown Square, Pennsylvania, USA, Project Management Institute.
Roudias, J. (2015). “Mastering Principles and Practices in PMBOK, Prince 2, and Scrum: Using Essential Project Management Methods to Deliver Effective and Efficient Projects”. Upper Saddle River, NJ. Pearson Education
Taylor, B., & Dow, W. (2013). Project management communications Bible. Hoboken, N.J., Wiley