|
1 Project Description
1.1 Project Description and Background
The project of CQUniversity NAIDOC Week Celebrations is developed for aligning the implication of the enhanced activities deployment supporting the utilization of the project management tools and activities for listing the involvement of the event management activities for celebrating the National Aborigines and Islanders Day Observance Committee (NAIDOC). The School of Engineering and Technology wants to increase the awareness of the CQU staff and students about the cultural heritage and indigenous practices of Aboriginal and Torres Strait Island. The hosting of the event would be eased by the deployment of the effective project plan supporting the utilization of the enhanced deployment of technology. The event would have the primary objectives of making the students and staffs of CQU aware of the perspectives and cultures of the native people. The analysis would also be helpful for forming the implication of the activities for aligning with the implication of the successive activities. The deployment of the project is aligned with the implication of the successive deployment of the event management activities. The deployment of the project for the management of the event of NAIDOC week celebration would be assisted by the implication of the effective deployment of the activities.
The NADIOC week celebration is a major event of aligning the deployment of the activities so that enhanced communication can take place. The celebration week of NAIDOC would be dependent on the implication of the enhanced functional deployment. The School of Engineering and Technology would be responsible for the formation of the activities favouring the implication of the effective activities deployment. The celebration of the event would be assisted by the deployment of the enhanced activities deployment. The implication of the activities would also be assisted for the utilization of the effective activities deployment. The supply of the activities had helped in listing the modification of the activities favouring the formation of the successive management of the activities. The implementation of the successive deployment of the activities has helped in listing the modification of the enhanced successive deployment of the activities. The implementation of the activities had helped in forming the successive implication of the activities supporting the spreading of the cultural event of the NAIDOS
1.2 Justification
|
Output
|
Outcome
|
Benefits
|
|
The event plan for the cultural event is the final deliverable for the project and the implication of the effective activity deployment. The utilization of the activities of project is aligned for improving the successive formation of the awakening for the cultural heritage of the Torres island.
|
The event of NAIDOS would be successfully executed for listing the implication of the effective deployment of the activities. The event would be executed for the week duration so that the staff and student can become acquainted by the implication of the activities for listing the implication of the final project deliverable. The outcome of the project would be supported by the formation of the activities limitation and it would help in spreading to the formation of the effective activities deployment.
|
The benefits of implying the event would be helpful for forming the utilization of the activities and it would also be helpful for forming the implication of the effective activities deployment. The event would have the primary objectives of making the students and staffs of CQU aware of the perspectives and cultures of the native people.
|
|
Stakeholders
The stakeholders of the project are the people that are directly and indirectly related to the implication of the effective integration deployment. The stakeholders of the project are responsible for the formation of the effective functions for the successive integration deployment. The stakeholders of the project can be divided into three sections of sponsor, supplier, and user. All the stakeholders of the project can be divided into the three sections and the following table would provide a brief of the key stakeholders of the project and their description of interest.
Key Stakeholder List
|
|
Stakeholder
|
Category
(i.e. Sponsor / Supplier / User)
|
Description of Interest
|
Description of Influence
|
|
1
|
Project Manager
|
Supplier
|
The project manager would be responsible for the completion of all the activities of the project and the manager would be responsible for the management of the activities.
|
The divisions of the activities would be aligned by the project manager for forming the usages of the information and it would also be utilized for the implication of the effective activities deployment.
|
|
2
|
Board Members of Central Queensland University
|
User
|
The board members of the CQU would act as the main sponsor for the project as they would be responsible for the project deployment.
|
The boards members are responsible for the completion of the project approval
|
|
3
|
Contractor
|
Supplier
|
They are bounded by the procurement and agreements for forming the utilization of the effective and final project activities.
|
Contractor would be responsible for carrying out the project for the formation of the successive deployment of external support to the project
|
|
4
|
Students, and Staffs of Central Queensland University
|
User
|
They would be the end users who would be using the services of the events. The awareness of the event would be acting directly to them
|
The students and staffs of the organization would imply the utilization of the enhanced activities.
|
|
5
|
Project Team
|
Supplier
|
They would get the benefit of recognition after the completion of the event.
|
They would take care of all the activities of the project for implying the implication of the activities.
|
|
6
|
Food vendors
|
Supplier
|
The agreement by the various vendors would be supported by the effective activities deployment.
|
The food vendors would be responsible for providing food and drinks at the event in return of payments
|
2.2 Stakeholders Engagement Assessment Matrix (3 marks)
Stakeholders Engagement Assessment Matrix
|
Stakeholder
|
Unaware
|
Resistant
|
Neutral
|
Supportive
|
Leading
|
|
1. Project Manager
|
|
|
C
|
D
|
|
|
2. Board Members of Central Queensland University
|
C
|
|
|
D
|
|
|
3. Contractor
|
|
|
|
C
|
C
|
|
4. Students, and Staffs of Central Queensland University
|
|
|
C
|
D
|
|
|
5. Project Team
|
|
|
|
C, D
|
|
|
6. Food Vendor
|
|
|
C
|
D
|
|
Stakeholder Communication
|
Communication method
|
PULL or PUSH
|
Justification
|
|
Reports and Documentation
|
Push
|
The communication method of Reports and Documentation would act as the push factor for the deployment of the effective communication strategies. The reports would also be helpful for aligning the various activities deployment plan in implementing the effective activities limit.
|
Traditional Owner/s of the land on which CQ University campuses are located
The single key stakeholder is the most successive operation development for the utilisation of the project ownership. The key stakeholder would help in forming faster decision making and the continuation of the activities so that the project of CQU cultural event can be effectively executed. The stakeholders of the project can be communicated easily for the final decision making.
Opening statement style
The Project Executive should use ‘Acknowledgement of Country’ for the opening statement because the opening statement style is a traditional statement for the culture of Aboriginal and Torres Strait Island.
Requirements gathering for each event
Yes, the study of the previous event management report would help them for forming the successive deployment of the activities favouring the formation of the project activities. It would also serve the implication of the supportive deployment of the activities so that the implication can be carried on successfully. The gathering of the information would also be helpful for listing the implication of the activities deployment.
Requirements traceability
Project Progress Report should be used to track or ‘trace’ requirements throughout the project life cycle
Requirements prioritization process
The prioritization of the requirements would allow the integration of the effective activities for aligning with the implication of the successive activities. The School of Engineering and Technology wants to increase the awareness of the CQU staff and students about the cultural heritage and indigenous practices of Aboriginal and Torres Strait Island. The hosting of the event would be eased by the deployment of the effective project plan supporting the utilization of the enhanced deployment of technology. The event would have the primary objectives of making the students and staffs of CQU aware of the perspectives and cultures of the native people.
The MOSCOW technique is given below,
Must have- Event Management plan
Should have- Knowledge about the implication of the project management activities
Could have- Advertisements for the events
Won’t have- lack of knowledge about the culture and heritage of Aboriginal and Torres Strait Island
Work breakdown structure
WBS Dictionary
|
Resource Acquisition
|
|
WBS ID
|
1
|
|
Description of work
|
The resources are a major factor that would be required for the completion of the project. Hence, it is very important for the accumulation of the required resources for the project. This step is very important for the initiation of the activities of the project.
|
|
Cost Estimate
|
$9,360.00
|
|
Start and Finish Dates
|
Mon 3/5/18
Thu 4/19/18
|
|
Initial Documentation
|
|
WBS ID
|
2
|
|
Description of work
|
The proper documents would be made for the deployment of the activities that would be required in the project for completing the project activities.
|
|
Cost Estimate
|
$10,240.00
|
|
Start and Finish Dates
|
Fri 3/16/18
Mon 6/11/18
|
|
Plan Deployment
|
|
WBS ID
|
3
|
|
Description of work
|
The deployment of the project plan is helpful for ensuring that the activities of the project are completed in the scheduled time. The involvement of the plan would help the completion of the project activities.
|
|
Cost Estimate
|
$5,040.00
|
|
Start and Finish Dates
|
Wed 3/28/18
Mon 4/9/18
|
|
Plan Approval
|
|
WBS ID
|
4
|
|
Description of work
|
The project manager would approve the plan by carefully examining the feasibility of the plan. It would be utmost responsibility for the manager that planned activities must be executed successfully.
|
|
Cost Estimate
|
$6,360.00
|
|
Start and Finish Dates
|
Tue 4/10/18
Thu 4/19/18
|
|
Event Requirements are Prepared
|
|
WBS ID
|
5
|
|
Description of work
|
The event would be dependent on a number of resources and materials. The accumulation of these resources along with the necessary setup and alignment of the event requirements.
|
|
Cost Estimate
|
$18,600.00
|
|
Start and Finish Dates
|
Fri 4/20/18
Tue 6/5/18
|
|
Execution of the event
|
|
WBS ID
|
6
|
|
Description of work
|
The carrying out of the event is another major factor that would be aligned for the deployment of the operations for favouring the utilization of the plan developed.
|
|
Cost Estimate
|
$3,040.00
|
|
Start and Finish Dates
|
Tue 6/12/18
Fri 6/15/18
|
Schedule
Resource Acquisition
|
Activity
|
Description of work
|
Start Date
|
End Date
|
Duration
(days)
|
|
1.1
|
Project Requirement Analysis
|
Mon 3/5/18
|
Wed 3/7/18
|
2
|
|
1.2
|
Human Resource employment
|
Thu 3/8/18
|
Mon 3/12/18
|
2
|
|
1.3
|
Material Resource Acquisition
|
Tue 4/17/18
|
Thu 4/19/18
|
2
|
Initial Documentation
|
Activity
|
Description of work
|
Start Date
|
End Date
|
Duration
(days)
|
|
2.1
|
Deployment of initiation documents
|
Fri 3/16/18
|
Wed 3/21/18
|
3
|
|
2.2
|
Manual Reports are documented
|
Thu 5/17/18
|
Tue 5/22/18
|
3
|
|
2.3
|
Final Reports are made
|
Wed 6/6/18
|
Mon 6/11/18
|
3
|
Plan Deployment
|
Activity
|
Description of work
|
Start Date
|
End Date
|
Duration
(days)
|
|
3.1
|
Outlining the plan
|
Wed 3/28/18
|
Fri 3/30/18
|
2
|
|
3.2
|
Complete Plan is made
|
Mon 4/2/18
|
Mon 4/9/18
|
5
|
Plan Approval
|
Activity
|
Description of work
|
Start Date
|
End Date
|
Duration
(days)
|
|
4.1
|
Submission of Plan
|
Fri 4/20/18
|
Thu 4/26/18
|
5
|
|
4.2
|
Client approval is made
|
Fri 4/27/18
|
Tue 5/1/18
|
3
|
Event Requirements are Prepared
|
Activity
|
Description of work
|
Start Date
|
End Date
|
Duration
(days)
|
|
5.1
|
Site is developed
|
Wed 5/2/18
|
Mon 5/7/18
|
4
|
|
5.2
|
Event set up is made
|
Thu 5/10/18
|
Wed 5/16/18
|
5
|
|
5.3
|
Program is scheduled
|
Wed 5/23/18
|
Tue 6/5/18
|
10
|
Execution of the event
|
Activity
|
Description of work
|
Start Date
|
End Date
|
Duration
(days)
|
|
6.1
|
Event is initiated
|
Tue 6/12/18
|
Tue 6/12/18
|
1
|
|
6.2
|
Event in Executed
|
Wed 6/13/18
|
Thu 6/15/18
|
3
|
|
6.3
|
Event is closed
|
Fri 6/15/18
|
Fri 6/15/18
|
1
|
Cost Baseline
|
|
|
|
|
WBS id
|
Activity name
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
|
1.1
|
Project Requirement Analysis
|
$ 1,560.00
|
|
|
|
|
|
|
|
|
1.2
|
Human Resource employment
|
$ 1,560.00
|
|
|
|
|
|
|
|
|
2.1
|
Deployment of initiation documents
|
|
$ 2,280.00
|
|
|
|
|
|
|
|
2.2
|
Manual Reports are documented
|
|
$ 1,680.00
|
|
|
|
|
|
|
|
2.3
|
Final Reports are made
|
|
|
$ 2,280.00
|
|
|
|
|
|
|
3.1
|
Outlining the plan
|
|
|
|
$ 2,560.00
|
|
|
|
|
|
3.2
|
Complete Plan is made
|
|
|
|
$ 2,560.00
|
|
|
|
|
|
4.1
|
Submission of Plan
|
|
|
|
|
$ 1,680.00
|
|
|
|
|
4.2
|
Client approval is made
|
|
|
|
|
|
$ 3,360.00
|
|
|
|
5.1
|
Site is developed
|
|
|
|
|
|
$ 3,600.00
|
|
|
|
5.2
|
Event set up is made
|
|
|
|
|
|
$ 720.00
|
$ 1,440.00
|
|
|
5.3
|
Program is scheduled
|
|
|
|
|
|
|
$ 3,040.00
|
|
|
6.1
|
Event is initiated
|
|
|
|
|
|
|
$ 3,800.00
|
|
|
6.2
|
Event in Executed
|
|
|
|
|
|
|
$ 4,200.00
|
|
|
6.3
|
Event is closed
|
|
|
|
|
|
|
|
$ 1,600.00
|
|
|
Total weekly cost
|
$3,120.00
|
$3,960.00
|
$2,280.00
|
$5,120.00
|
$1,680.00
|
$7,680.00
|
$12,480.00
|
$1,600.00
|
|
|
Cumulative cost
|
$3,120.00
|
$7,080.00
|
$9,360.00
|
$14,480.00
|
$16,160.00
|
$23,840.00
|
$36,320.00
|
$37,920.00
|
Risks
Risk Register
|
Name
|
Description
|
Likelihood
|
Impact
|
Response type
|
Mitigation strategy
|
|
Delay in completion
|
The activities would be delayed for the deployment of the activities favouring the formation of the successive deployment of the activities
|
Almost Certain
|
Negligible
|
Accept
|
Surrogacy schedule plan should be implied for the project
|
|
Cost Overrun
|
The overrun of the cost would be resulted due to the delayed activities formation.
|
Likely
|
Moderate
|
Transfer
|
Contingency budget allocation should be done
|
|
Competition among team members
|
Team members would have to face the compete with each other for performing better deliverable
|
Possible
|
Minor
|
Exploit
|
Should be used for getting enhanced productivity of the project deliverable
|
Tolerences
|
Tolerance
|
Specific Tolerance allowed
|
|
Tolerance specified for time
|
Project must be completed in 4 months with 1 month of tolerance
|
|
Tolerance specified for cost
|
Project Budget is expected to be $40,000.00, $37,920.00 actual budget with a tolerance of $2,180.00
|
Lessons
|
Previous lessons learned
|
Proposed activity to address
(in current project)
|
Work package which activity will be added
|
|
Lesson
Previously there have been problems with attendance of students and staff at campus events. Attendance was low when students and staff perceived that the event did not relate to them or they had little interest in the event theme.
|
The event management deployment is eased by the implication of the enhanced activities deployment
|
The implication of the effective management of the projects with the help of aligning with the principles of the event management activities.
|
Project Submission Approval
The undersigned acknowledge that they have reviewed the <Project Name> Assessment Task 2 and agree with the information presented within this document.
|
Signature:
|
|
Date:
|
|
|
Print Name:
|
|
|
|
|
Title:
|
|
|
|
|
Organisation:
|
|
|
|
References
Bailey, D. (2015). Business continuity management into operational risk management: Assimilation is imminent… resistance is futile!. Journal of business continuity & emergency planning, 8(4), 290-294.
Caruana, A. (2016). A business continuity plan maturity index: a comparative study of Maltese licensed financial services firms (Bachelor’s thesis, University of Malta).
Cook, J. (2015). A six-stage business continuity and disaster recovery planning cycle. SAM Advanced Management Journal, 80(3), 23.
Gozman, D., Wilcocks, L., Kovacevic, M., & Craig, A. (2017). Preparing for the wolf: sustainability through business continuity management. Intelligent Sourcing, (3), 50-63.
Henderson, C., Klimas, J., Dunne, C., Leddin, D., Meagher, D., O’Toole, T., & Cullen, W. (2014). Key performance indicators for mental health and substance use disorders: a literature review and discussion paper. Mental Health and Substance Use, 7(4), 407-419.
Hills, M. (2016). Being resilient: business continuity principles for vetinary practice. In Practice, 38(10), 484-486.
H?ebí?ek, J., Soukopová, J., Štencl, M., & Trenz, O. (2014). Corporate key performance indicators for environmental management and reporting. Acta Universitatis Agriculturae et Silviculturae Mendelianae Brunensis, 59(2), 99-108.
Karaman, E., & Kurt, M. (2015). Comparison of project management methodologies: prince 2 versus PMBOK for it projects. Int. Journal of Applied Sciences and Engineering Research, 4(5), 657-664.
Krysi?ski, M., & Miller, P. (2016). The Role of Conflict in Project Management in the PRINCE2 Methodology. Ekonomika i Organizacja Przedsi?biorstwa, (6), 3-12.
Olson, A., & Anderson, J. (2016). Resiliency scoring for business continuity plans. Journal of business continuity & emergency planning, 10(1), 31-43.
Parker, E., & Fox, A. (2016). Changing Perceptions About Business Continuity Planning (BCP) in Communities Around Mounts Bay in Cornwall, UK.
Parmenter, D. (2015). Key performance indicators: developing, implementing, and using winning KPIs. John Wiley & Sons.
Peltier, T. R. (2013). Information security fundamentals. CRC Press.
Podgórski, D. (2015). Measuring operational performance of OSH management system–A demonstration of AHP-based selection of leading key performance indicators. Safety Science, 73, 146-166.
Rodger, J. A., Bhatt, G., Chaudhary, P., Kline, G., & McCloy, W. (2015). The Impact of Business Expertise on Information System Data and Analytics Resilience (ISDAR) for Disaster Recovery and Business Continuity: An Exploratory Study. Intelligent Information Management, 7(04), 223.
Rui, X. U. E., Baron, C., Esteban, P., & Zheng, L. (2016). Integrating the ISO/IEC 15288 Systems Engineering Standard with the PMBoK Project Management Guide to Optimize the Management of Engineering Projects. In Complex Systems Design & Management (pp. 291-291). Springer International Publishing.
Sahebjamnia, N., Torabi, S. A., & Mansouri, S. A. (2015). Integrated business continuity and disaster recovery planning: Towards organizational resilience. European Journal of Operational Research, 242(1), 261-273.
Snedaker, S. (2013). Business continuity and disaster recovery planning for IT professionals. Newnes.
Snyder, C. S. (2014). A Guide to the Project Management Body of Knowledge: PMBOK (®) Guide. Project Management Institute.
Stark, C. G., & Willemse, A. (2016, April). Maintaining Business Continuity During the Ebola Crisis. In SPE International Conference and Exhibition on Health, Safety, Security, Environment, and Social Responsibility. Society of Petroleum Engineers.
Tomanek, M., & Juricek, J. (2015). Project risk management model based on PRINCE2 and SCRUM frameworks. arXiv preprint arXiv:1502.03595.
Torabi, S. A., Soufi, H. R., & Sahebjamnia, N. (2014). A new framework for business impact analysis in business continuity management (with a case study). Safety Science, 68, 309-323.
Wallace, M., & Webber, L. (2017). The disaster recovery handbook: A step-by-step plan to ensure business continuity and protect vital operations, facilities, and assets. AMACOM Div American Mgmt Assn.
Xing, J., & Zio, E. (2016, September). An integrated framework for business continuity management of critical infrastructures. In ESREL 2016.
