PPMP20010: Project Audit, Termination, Governance Reports - Barwon

This assignment presents a comprehensive project audit, termination, and governance report for the "Implementing 3 Tier Structure for Storage in Barwon Health Organization" project. Part A includes an audit plan covering performance, compliance, quality, change/exit, risk, and best practices, along with a project termination/closure plan aligned with PMBOK knowledge areas. Part B details the project's governance structure, including overall responsibilities, roles, performance criteria, governance arrangements, relationship to the portfolio, authorization points, and delegation. The report assesses the project's success in meeting its objectives and provides insights into project management best practices. Desklib offers this document along with numerous other solved assignments and resources to aid students in their studies.

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
PPMP20010 - Assignment 2
Part A
Project Audit and Termination
Report
1 PROJECT INFORMATION
Project name: Implementing 3 Tier Structure for Storage in Barwon Health
Organization
Date: 7th April, 2018
Project ownership: IT Project Management
Prepared by: <<name of the student>>
Distribution list: Chris Jones, CEO (Barwon Health Organization)
Jessica Keith, CFO (Barwon Health Organization)
Laurence Heath, Head of Project Steering Committee
(Barwon Health Organization)
ENTER YOUR NAME WITH STUDENT ID PAGE 1

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
2 AUDITABLE CATEGORIES
Auditable Category WBS ID and Item Description Applicable metrics
1. Performance /
Progress
1.1 Initial Documents are made Proper Report for
deployment of the
successive integration would
be helpful for the alignment
of functions
Report Structure and
Template
1.2 Project Kick off Meeting A kick off meeting for the
project is executed
All members are present in
the meetings
1.3 Plan is Developed The final plan required for
the completion of the project
would be made
Project Plan Template
2. Compliance 2.1 Outline of design is made Design outline is made for
the integrated system
development
Design template is followed
2.2 Design Review Review of the design based
on the client’s requirements
Simulation Testing Results
2.3 Complete Design is made The design required for the
deployment of the final
system would be made
Design Graphics
3. Quality 3.1 Backup database is created A backup database is
created for the new system
that would be aligned for the
formation of the migration
Storage capacity of the
database
3.2 Migration of data The database is migrated to
be implied for forming the
effective development of the
operations.
Successful alignment of the
data is deployed
3.3 Integrated Database is
developed
An integrated database
would be formed for
supporting the utilization of
the operations
All 3 structure gets
integrated data
4. Change / Exit 4.1 Development of HCI, VDI, The hybrid structure
ENTER YOUR NAME WITH STUDENT ID PAGE 2

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
and Microsoft SQL comprising of HCI, VDI, and
Microsoft SQL is developed
4.2 Integration of the
technologies
The three technologies
developed would be
integrated on the same
platform
5.1 Test Plan is developed Test plan for the integrated
structure is developed
5. Risk 5.2 Testing of the structure The testing of the structure is
managed for the
management of the
operations for hybrid
structure
6.1 Implementation Plan An integrated
implementation plan would
be formed for the utilization
of activities
6.2 Implementing the structure The news structure would be
deployed successfully for
easing the operational
development.
6. Best Practices /
Lessons to be
Learned
7.1 Deployment Plan Deployment plan would be
aligned for forming the
utilization of the effective
integration plan.
Feasibility Analysis
7.2 Deploying the hybrid
structure
The new hybrid structure
would be deployed for the
organization
Integration of the operations
8 Final Documentation and
Closure
The final document for the
project closure is made
Report Structure
3 AUDIT PLAN
Audit Category Item When will it
be
conducted?
Who will
conduct?
Purpose (discovery
or decision-
making)?
Performance /
Progress
Documents Initial Phase Project
Manager
Decision Making
Test results Deployment
Phase
Tester Discovery Making
Plan feasibility Plan Phase Project Decision Making
ENTER YOUR NAME WITH STUDENT ID PAGE 3

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
Manager
Compliance Plan End of
Planning
Phase
Planner Decision Making
Test Reports Test Phase Tester Discovery Making
Design Designing
Phase
Designer Discovery Making
Quality Design of new
structure
End of Design
Phase
Designer Discovery Making
HCI, VDI, and
Microsoft SQL
At the end of
the execution
Phase
IT
engineer
Discovery Making
Integration of
the system
Deployment
Phase
IT
engineer
Decision Making
Change / Exit Data Migration Before the
execution
phase
Database
Admin
Discovery Making
System
Modification
Deployment
Phase
Developer Decision Making
Change
Implementation
Deployment
Phase
IT
engineer
Decision Making
Risk Implementation
plan
Monthly Vendor Decision Making
Change Plan Once Vendor Discovery Making
Best Practices /
Lessons to be
Learned
Hybrid
Structure
End of project Project
Manager
Discovery Making
Integration of
the system
Deployment
Phase
IT
engineer
Decision Making
System
Modification
Deployment
Phase
Developer Decision Making
4 PROJECT TERMINATION / CLOSURE
Controllable
Category
Item &
Explanation
PMBOK Knowledge Area
Input
Tool &
Technique Output
1. Deliverable 1.1 Plan Project List Ms-Project Plan Schedule
The project plan is developed for the alignment of the activities and
the alignment of the operations for listing the development of the
influential development.
1.2 Meetings Charter
Document
Project
Meeting
Deliverable of the
project
The proper meetings would align for the deployment of the
operations and listing the modification of the activities supporting the
ENTER YOUR NAME WITH STUDENT ID PAGE 4

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
management of the success development
1.3
Administration
Log book Strategy
Development
Model
Proper
Administration of
the operations
The project administration is developed for the alignment of the
activities and the alignment of the operations for listing the
development of the influential development.
2. Configuration 2.1 Software Design Operation Complete system
The configuration of the software would be based for the alignment
of the successive alignment of the operations. It would also help in
forming the final project development.
2.2 System Hardware Program Final System
Development
The system deployment of the activities would align with the
deployment of the activities supporting the management of the
activities.
2.3 Design User
Requirements
Design Tools Complete Design
The alignment of the operations had also helped in forming the
complete design alignment of the activities. The design development
would also help in ceasing the formation of the successive
integration.
3. Status
Accounts
3.1 Cost
Budget
Resource List Resource
Estimation
Final cost
The status accounts are formed for listing the alignment of the
activities would list the alignment of the successive development.
The cost budget estimation would also help in ceasing the formation
of the successive integration.
3.2 NPV
analysis
Cash Inflow-
outflow
NPV analysis Final Benefit
analysis for the
project
The NPV would be based for the alignment of the successive
alignment of the operations. It would also help in forming the final
project development. The NPV would also help in ceasing the
formation of the successive integration.
3.3 Operation
Development
Logs Analysis
Methods
Operational
Development
The operation development would be based for the alignment of the
successive alignment of the operations. It would also help in forming
the final project development. The operation development would also
help in ceasing the formation of the successive integration.
4. Logs 4.1 User
Documentatio
n
User
requirements
Analysis
Method
Final Documents
Many logs are employed for the formation of the users
documentation and deployment of the final documents. The user
documentation would also help in ceasing the formation of the
successive integration.
4.2 Training
Documents
Training
Requirements
Documentation Final Training
Manuals
The documentation would be aligned for the formation of the
activities and alignment of the successive modification. The training
documentation would also help in ceasing the formation of the
successive integration.
4.3 Test
Results
Test Results Statistical
Analysis
Final Reporting
The final test results would also help in forming the alignment of the
final test results and unified formation of the process integration. The
tests result would also help in ceasing the formation of the
successive integration.
5. Issues 5.1 Risk log Risk
Identification
List
Risk Analysis
Tool
Final Risk List
The risk log is formed for overcoming the alignment of the
ENTER YOUR NAME WITH STUDENT ID PAGE 5

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
successive development model. The risk log would be formed for the
identification of the operations.
5.2 Priority
Matrix
Risk Priority
Forms
Severity-
Likelihood
Analysis
Risk Mitigation
The priority matrix is formed for the alignment of the priority analysis
of the integrated management. The priority matrix would also help in
ceasing the formation of the successive integration.
5.3 Risk
Assessment
Risk
Identification
List
Prioritization
deployment
Final assessment of
risk
The assessment would also in forming the utilization of the support
the influential deployment of the operations. The risk deployment
would also help in ceasing the formation of the successive
integration.
6.
Procurements
6.1 Contract
with vendor
Requirements
of client
Documentation Final Contract with
Vendor
The contract with vendor is a major deliverable for the project as it
would help in assigning the work to the project contactor
6.2
Agreement of
Payment
Agreed
Payment
Documentation Agreed Payment
with externals
A mutual agreed value would be accepted in return of the work done
by the contractor
6.3
5 TERMINATION / CLOSURE PLAN
The project Closure Plan is developed with the help of final documentation and storing
the final report for future uses. The Implementation of 3 Tier Structure for Storage in
Barwon Health Organization is an IT project and hence the report developed would result
in forming the future reference. The final phase of the project is monitoring and closing.
Hence it is important for the project manager to deploy the effective project termination
and closure of the activities. The termination plan would also help in ceasing the
development of the final report structure. The closure of the Implementing 3 Tier
Structure for Storage in Barwon Health Organization project is based on the
development of the successive project completion and monitoring of the system
implemented.
ENTER YOUR NAME WITH STUDENT ID PAGE 6

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
Part B
Project Governance Report
1. PROJECT INFORMATION
Project name: Implementing 3 Tier Structure for Storage in Barwon Health
Organization
Date: 7th April, 2018
Project ownership: IT Project Management
Prepared by: <<name of the student>>
Distribution list: Chris Jones, CEO (Barwon Health Organization)
Jessica Keith, CFO (Barwon Health Organization)
Laurence Heath, Head of Project Steering Committee
(Barwon Health Organization)
ENTER YOUR NAME WITH STUDENT ID PAGE 7

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
2. OVERALL PROJECT RESPONSIBILITY
The responsibility for this project lies by dividing the work among the project
team member. The project manager would have to ensure that the project is
completed successfully. The project steering committee are in charge of the key
decision made in the project. The alignment of the activities would be the
responsibility of the operations supporting the development of the improved
activities.
The key decisions making is the responsibility that lays on the hand of the project
governance board and the project investors. The project manager would manage
all the activities that would sum for the completion of the project. The operations
of the project is carried on by the project team members.
3. ROLES, RESPONSIBILITIES AND PERFORMANCE CRITERIA
The roles, responsibilities and performance criteria for this project consist of
assigning each of the project team members with some specific work
responsibility. The documenter would be responsible for the activities of initial
documents are made and final documentation and closure. the project manager
would be responsible for the activity of project kick off meeting. The planner
would be responsible for the activity of plan is developed. The system designer
would be responsible for the activity of design of new structure is made. The
database admin would be responsible for the activity of existing data is backed
up. The IT engineer would be responsible for the activity of development of HCI,
VDI, and Microsoft SQL and integration of the technologies. The tester would be
responsible for the activity of testing of the 3 tier structure. The software team
would be responsible for the activity of deployment of the new hybrid structure
and implementation of the new structure.
4. GOVERNANCE ARRANGEMENTS
The governance arrangements for this project consist of processes that would
tend to the review of the changes occurring to scope, budget, schedule, and
quality. The development of the final review of the changes would be based on
the final project deliverable and alignment. The implication of the improved
operations would be the responsibility of the activities.
5. RELATIONSHIP TO THE PORTFOLIO
The Relationship to the Portfolio for this project is aligned for the formation of the
effective system integration and alignment of the improved operations. The
relationship study of the portfolio would be based for the deployment of the
information processing and the alignment of the operations. The portfolio
development is based for the modifying the existing system into the newly
formed 3 tier architecture.
ENTER YOUR NAME WITH STUDENT ID PAGE 8

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
6. AUTHORISATION POINTS
The authorisation points for this project are the project board meetings where the
project plan, design, and system would be approved. The alignment of the final
project deliverable of integrated system would be the responsibility of the project
plan development. The authorization of the project deliverable would be based
on the consideration supporting the final project plan development.
7. DELEGATION
The delegation arrangements for this project are the testing results that would be
helpful for the alignment of the final project deliverable. Moreover, the project
steering committee must be aligned with the support and development of the
successive final project development. The alignment of the project delegation
would be based for the formation of the effective project deliverable.
8. INFORMATION VALIDITY
The manner in which information validity for this project is assured is by the use
of the effective reporting and documentation. The key decisions making is the
responsibility that lays on the hand of the project governance board and the
project investors. The project manager would manage all the activities that would
sum for the completion of the project. The operations of the project are carried
on by the project team members. The various test reports and documents would
be eased for the management of the information processing.
9. SCRUTINY
The scrutiny arrangements for this project are the system test results and review
process that would help in easing the final speculation of the final project
deliverable. The influence of the development activities would also be favourable
for the modification of the information and process that are not appropriate for
the project.
10. STATUS REPORTING
The status reporting arrangements for this project are the project log books that
must be filled and submitted in the project. The time to time completion of the
project would be reported to the project governance board and it would tend to
form the delivery of the final project assurance.
ENTER YOUR NAME WITH STUDENT ID PAGE 9

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
11. IMPROVEMENT
The improvement arrangements for this project are dependent on the culture and
harmony of the project activities. The deployment of the 3 tier structure would
also be helpful for supporting the modification of the operations favourable for
the project deployment.
12. STAKEHOLDER ENGAGEMENT
The stakeholder engagement arrangements for this project is given below,
Stakeholder Unaware Resistant Neutral Supportive Leading
Investor C D
Client C D
Steering
Committee
C D
Project
Manager
CD
Contractor C D
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 Implementing 3 Tier
Structure for Storage in
Barwon Health Organization
200 days Thu 3/1/18 Wed 12/5/18
1 1 Initiation Phase 25 days Thu 3/1/18 Wed 4/4/18
2 1.1 Initial Documents are made10 days Thu 3/1/18 Wed 3/14/18
3 1.2 Project Kick off Meeting 5 days Thu 3/15/18 Wed 3/21/18
4 1.3 Plan is Developed 15 days Thu 3/15/18 Wed 4/4/18
5 2 Design of new structure is made30 days Thu 4/5/18 Wed 5/16/18
6 2.1 Outline of design is made 10 days Thu 4/5/18 Wed 4/18/18
7 2.2 Design Review 5 days Thu 4/19/18 Wed 4/25/18
8 2.3 Complete Design is made 15 days Thu 4/26/18 Wed 5/16/18
9 3 Existing Data is Backed up45 days Thu 4/5/18 Wed 6/6/18
10 3.1 Backup database is created15 days Thu 4/5/18 Wed 4/25/18
11 3.2 Migration of data 15 days Thu 4/26/18 Wed 5/16/18
12 3.3 Integrated Database is
developed
15 days Thu 5/17/18 Wed 6/6/18
13 4 3-Tier Structure Development70 days Thu 5/24/18 Wed 8/29/18
14 4.1 Development of HCI,
VDI, and Microsoft SQL
30 days Thu 5/24/18 Wed 7/4/18
15 4.2 Integration of the technologies40 days Thu 7/5/18 Wed 8/29/18
16 5 Testing of the 3 Tier Structure15 days Tue 8/28/18 Mon 9/17/18
17 5.1 Test Plan is developed 5 days Tue 8/28/18 Mon 9/3/18
18 5.2 Testing of the structure 10 days Tue 9/4/18 Mon 9/17/18
19 6 Implementation of the
new structure
20 days Thu 9/13/18 Wed
10/10/18
20 6.1 Implementation Plan 7 days Thu 9/13/18 Fri 9/21/18
21 6.2 Implementing the structure 13 days Mon 9/24/18 Wed 10/10/18
22 7 Deployment of the new
hybrid structure
30 days Thu
10/11/18
Wed
11/21/18
23 7.1 Deployment Plan 10 days Thu 10/11/18 Wed 10/24/18
24 7.2 Deploying the hybrid structure20 days Thu 10/25/18 Wed 11/21/18
25 8 Final Documentation and
Closure
10 days Thu
11/22/18
Wed 12/5/18
Documenter,Documents[1]
Project Manager
Planner
System Designer
System Designer
System Designer,Design Tools[1]
Database Admin,Backup Software[1]
Database Admin
Database Admin
IT engineer,IT tools[1]
IT engineer
Tester
Tester,Testing tools[1]
Software team
Software team
Software team
Software team
Documenter,Documents[1]
T S W S T M F T S W S T M F T
Dec 3, '17 Feb 11, '18 Apr 22, '18 Jul 1, '18 Sep 9, '18 Nov 18, '18 Jan 27, '19 Apr 7, '19
ENTER YOUR NAME WITH STUDENT ID PAGE 10

PROJECT AUDIT, TERMINATION AND GOVERNANCE
REPORTS
NAME OF PROJECT
6 BIBLIOGRAPHY
Alam, M.I., Pandey, M. and Rautaray, S.S., 2015. A comprehensive survey on
cloud computing. International Journal of Information Technology and
Computer Science, 2, pp.68-79.
Brioso, X., 2015. Integrating ISO 21500 guidance on project management,
lean construction and PMBOK. Procedia Engineering, 123, pp.76-84.
Chaves, M.S., Araújo, C.D., Teixeira, L., Rosa, D., Júnior, I. and Nogueira,
C., 2016. A new approach to managing Lessons Learned in PMBoK process
groups: the Ballistic 2.0 Model. International Journal of Information Systems
and Project Management, 4(1), pp.27-45.
Cheng, J., Hunley, B., Kaur, D. and Merckling, E., 2017. Hyper-Converged
Infrastructure: Analysis of HPE’s Decision to Acquire SimpliVity.
Cheng, J.K., Malik, Z.A. and Sorooshian, S., 2017. Understanding the
Interrelationship Between Different Knowledge Areas in PMBOK Through
the Development of System Dynamics Model. The Social Sciences, 12(3),
pp.473-481.
Jaferi, F., Parsa, M. and Sajadi, S.M., 2016. A Study on How to Improve
PMBOK (Project Management Body of Knowledge) Guidelines Performance
by Simulation. World Academy of Science, Engineering and Technology,
International Journal of Industrial and Manufacturing Engineering, 3(1).
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems
approach to planning, scheduling, and controlling. John Wiley & Sons.
Kerzner, H., 2015. Project management 2.0: leveraging tools, distributed
collaboration, and metrics for project success. John Wiley & Sons.
Kerzner, H., 2018. Project management best practices: Achieving global
excellence. John Wiley & Sons.
Snyder, C. and Dionisio, C.S., 2017. A project manager's book of forms: A
companion to the PMBOK guide. John Wiley & Sons.
Snyder, C.S., 2014. A guide to the project management body of knowledge:
PMBOK (®) guide. Project Management Institute: Newtown Square, PA,
USA.
Tesfamicael, A.D., Liu, V. and Caelli, W., 2015, February. Design and
implementation of unified communications as a service based on the open
stack cloud environment. In Computational Intelligence & Communication
Technology (CICT), 2015 IEEE International Conference on (pp. 117-122).
IEEE.
Varajão, J., Colomo-Palacios, R. and Silva, H., 2017. ISO 21500: 2012 and
PMBoK 5 processes in information systems project management. Computer
Standards & Interfaces, 50, pp.216-222.
Veiga, A.P., 2017. Hyper Converged Infrastructures: Beyond virtualization.
arXiv preprint arXiv:1711.09747.
ENTER YOUR NAME WITH STUDENT ID PAGE 11