Development Of Healthcare App For Koala City Council: Project Scope, Schedule, Cost, Stakeholders, And Risks

1. Background Information about the Project

1.Background Information about the Project

a) The project is deployed for the development of the improved healthcare facilities by the development of a healthcare mobile application suitable for the improved services and treatment. The mobile application would help in easing the treatment facilities by forming the improved information processing. The patients, staffs and nurses would be able to employ the use of the application for facilitating the transfer of the information. The project of Development of Healthcare App for Koala City Council would allow the users for developing effective and improved operations.

The implication of the application for the treatment of the patients due to the project of Development of Healthcare App for Koala City Council would help in,

• Increasing the capability of treatment facilities for the patients
• Integrating the database so that communication can be eased

b) The project is formed for the development of treatment facility to the patients of Koala City Council by using the Healthcare application development. The main objective of the project is to form an effective start by introducing key stakeholders and reviewing project preliminary scope, assumptions, constraints, and milestones.

The key deliverables of the project are Healthcare Mobile Application, Project plan, Cost Estimation/Budget, Risk Management Plan, Communication Plan, and Stakeholder Analysis Plan.

2.Project Scope

a) The project of Development of Healthcare App for Koala City Council requires both human and material resources for the development of the healthcare application. The resources required for the project are listed below,

Human: Analyst, Documenter, Project Manager, Planner, Designer, Database Developer, Tester, Programmer, Engineer, and Trainer

Material: Software, Simulation Software, Database Software, Testing Tool, Programming Tools, and Network Tools

b) The work breakdown structure for the project of Development of Healthcare App for Koala City Council in organizational structure is given below,

     

3. Project Schedule

a) Gantt chart is a project planning diagram made from the table of the project schedule made in any specific software (Rodger et al., 2015). The implication of the project Gantt chart is implied for the improved project planning and documentation. The project Gantt chart is helpful for the deployment of the project schedule in an estimated table resource for the project. The project schedule for the project of Development of Healthcare App for Koala City Council with the resource allocation is shown in the table below,

                             

WBS	Task Name	Duration	Start	Finish	Predecessors	Resource Names
0	Development of Healthcare App for Koala City Council	94 days	Mon 4/2/18	Thu 8/9/18
1	Project Initialization	15 days	Mon 4/2/18	Fri 4/20/18
1.1	Requirement Analysis	3 days	Mon 4/2/18	Wed 4/4/18		Analyst
1.2	Stakeholder Analysis	2 days	Thu 4/5/18	Fri 4/6/18	2	Analyst
1.3	Feasibility Analysis	2 days	Mon 4/9/18	Tue 4/10/18	3	Analyst
1.4	Initiation Documentation	4 days	Wed 4/11/18	Mon 4/16/18	4	Documenter
1.5	Charter Documentation	3 days	Tue 4/17/18	Thu 4/19/18	5	Documenter
1.6	Project Kick off meeting	1 day	Fri 4/20/18	Fri 4/20/18	6	Project Manager
2	Project Planning	16 days	Mon 4/23/18	Mon 5/14/18
2.1	Selection of plan methodology	2 days	Mon 4/23/18	Tue 4/24/18	7	Planner
2.2	Plan outline is formed	4 days	Wed 4/25/18	Mon 4/30/18	9	Planner
2.3	Plan is reviewed	2 days	Tue 5/1/18	Wed 5/2/18	10	Planner
2.4	Plan is completed	7 days	Thu 5/3/18	Fri 5/11/18	11	Planner
2.5	Plan Approval	1 day	Mon 5/14/18	Mon 5/14/18	12	Project Manager
3	App Designing	13 days	Tue 5/15/18	Thu 5/31/18
3.1	App design software is selected	2 days	Tue 5/15/18	Wed 5/16/18	13	Designer, Software[1]
3.2	User Interface is designed	5 days	Thu 5/17/18	Wed 5/23/18	15	Designer
3.3	Simulation of the design	3 days	Thu 5/24/18	Mon 5/28/18	16	Tester, Simulation Software[1]
3.4	Design Review	2 days	Tue 5/29/18	Wed 5/30/18	17	Designer
3.5	Design is approved	1 day	Thu 5/31/18	Thu 5/31/18	18	Engineer
4	App development	29 days	Fri 6/1/18	Wed 7/11/18
4.1	Database is created	5 days	Fri 6/1/18	Thu 6/7/18	19	Database Developer, Database Software[1]
4.2	Prototype Testing	3 days	Fri 6/8/18	Tue 6/12/18	21	Tester, Testing Tool[1]
4.3	Integration of the database	3 days	Wed 6/13/18	Fri 6/15/18	22	Database Developer
4.4	Programming of the application functions	7 days	Mon 6/18/18	Tue 6/26/18	23	Programmer, Programming Tools[1]
4.5	System Alignment	3 days	Wed 6/27/18	Fri 6/29/18	24	Engineer, Network Tools[1]
4.6	Black box testing for functions	2 days	Mon 7/2/18	Tue 7/3/18	25	Tester, Testing Tool[1]
4.7	White box testing for functions	2 days	Wed 7/4/18	Thu 7/5/18	26	Tester, Testing Tool[1]
4.8	System is reviewed	3 days	Fri 7/6/18	Tue 7/10/18	27	Engineer
4.9	Application development is completed	1 day	Wed 7/11/18	Wed 7/11/18	28	Engineer
5	Go Live Application	20 days	Thu 7/12/18	Wed 8/8/18
5.1	Application Launch Plan	2 days	Thu 7/12/18	Fri 7/13/18	29	Planner
5.2	Implementation of application launch plan	2 days	Mon 7/16/18	Tue 7/17/18	31	Engineer
5.3	Development of training manuals	3 days	Wed 7/18/18	Fri 7/20/18	32	Trainer
5.4	Training Programs are formed	2 days	Mon 7/23/18	Tue 7/24/18	33	Trainer
5.5	Training is provided	5 days	Wed 7/25/18	Tue 7/31/18	34	Trainer
5.6	Beta test of usage	3 days	Wed 8/1/18	Fri 8/3/18	35	Tester, Testing Tool[1]
5.7	Staff review is evaluated	2 days	Mon 8/6/18	Tue 8/7/18	36	Analyst
5.8	Application is launched for healthcare	1 day	Wed 8/8/18	Wed 8/8/18	37	Engineer
6	Project is Closed	1 day	Thu 8/9/18	Thu 8/9/18	38	Project Manager

The Gantt chart for the project of Development of Healthcare App for Koala City Council is shown below,

The project schedule and Gantt chart have shown that the project can be divided into Project Initialization, Project Planning, App Designing, App development, and Go Live Application. The project start date is Mon 4/2/18 and the end date is Thu 8/9/18 for the duration of 94 working days. The project has been expected to complete in 4 months of time with the application development activities running for 3 months and the application launching for 1 months of time.  The project initialization comprises of requirement analysis, stakeholder analysis, feasibility analysis, initiation documentation, charter documentation, and project kick off meeting activities. The project planning comprises of selection of plan methodology, plan outline is formed, plan is reviewed, plan is completed, and plan approval.

2. Project Scope

The app designing comprises of app design software is selected, user interface is designed, simulation of the design, design review, and design is approved. The app development comprises of database is created, prototype testing, integration of the database, programming of the application functions, system alignment, black box testing for functions, white box testing for functions, system is reviewed, and application development is completed. The go live application comprises of application launch plan, implementation of application launch plan, development of training manuals, training programs are formed, training is provided, beta test of usage, staff review is evaluated, and application is launched for healthcare.

b) Project Network Diagram is made with the help of the drawing tools and the design include the project activities listed in a parallel box and connected in a sequential way (Kerzner, 2013). The project network diagram is helpful for listing out the activities in a diagram method for the alignment of the project diagram. The network diagram for the project of Development of Healthcare App for Koala City Council is given below,

The project network diagram is made for deploying the improved project management activities and the alignment of the project tasks (Olson & Anderson, 2016). The project alignment methodology is formed for forming the use of waterfall methodology and the integration of the project activities in a systematic and aligned method. The network diagram helps in forming a pictorial representation of the project activities along with project summary activities and the development iof the improved project activities. The integration of the project development methodology would allow the formation of the project activities in waterfall methodology for overcoming the deployment issues and considering the advanced processes.

The project planning structure is waterfall in approach and the activities of the project are sequential in nature. The project analysis is deployed for the deployment of the application and carrying out the alignment of the improved project operations. The critical path of the project is sequential and it is shown below,

                                

c) The project milestone consists of the major attainable factors for the project that can be pointed out from the project schedule table (Burke, 2013). The milestones generally are the last activity of the project phase and they form the final closure of the project phase. The project initialization phase consists of project kick off meeting as the milestone event. The project planning phase consists of plan approval as the milestone event. The app designing phase consists of design is approved as the milestone event. The app development phase consists of application development is completed as the milestone event. The go live application phase consists of application is launched for healthcare as the milestone event.

WBS	Task Name	Duration	Start	Finish
1.6	Project Kick off meeting	1 day	Fri 4/20/18	Fri 4/20/18
2.5	Plan Approval	1 day	Mon 5/14/18	Mon 5/14/18
3.5	Design is approved	1 day	Thu 5/31/18	Thu 5/31/18
4.9	Application development is completed	1 day	Wed 7/11/18	Wed 7/11/18
5.8	Application is launched for healthcare	1 day	Wed 8/8/18	Wed 8/8/18

3. Project Schedule

4.Project Cost

a) The project cost estimation is deployed for effective employment of the improved activities in an estimated project budget (Parker & Fox, 2016). The cost estimation can be employed by the use of the improved project analysis and development. The cost estimation is also helpful for listing the project operations in a table format along with the expected usage of the resources and the cost occurred for the activities. The cost estimating worksheet is implied with the parametric estimate factors of WBS ID, type of resource, cost variable, cost per unit, number of units, and cost estimate. The cost estimation would also involve the development of the total cost of completing the project by summing up the individual expense of the resources used for the project. The following table would show the cost estimation of the project,

COST ESTIMATING WORKSHEET
Project Name: Development of Healthcare App for Koala City Council
	Parametric Estimates
WBS ID	Type of Resource	Cost Variable	Cost per Unit	Number of Units	Cost Estimate
1.1	Human	$/hr	$80.00	24	$1,920.00
1.2	Human	$/hr	$80.00	16	$1,280.00
1.3	Human	$/hr	$80.00	16	$1,280.00
1.4	Human	$/hr	$90.00	32	$2,880.00
1.5	Human	$/hr	$90.00	24	$2,160.00
1.6	Human	$/hr	$140.00	8	$1,120.00
2.1	Human	$/hr	$100.00	16	$1,600.00
2.2	Human	$/hr	$100.00	32	$3,200.00
2.3	Human	$/hr	$100.00	16	$1,600.00
2.4	Human	$/hr	$100.00	56	$5,600.00
2.5	Human	$/hr	$140.00	8	$1,120.00
3.1	Human	$/hr	$110.00	16	$1,760.00
3.1	Material	$/use	$3,199.00	1	$3,199.00
3.2	Human	$/hr	$110.00	40	$4,400.00
3.3	Human	$/hr	$80.00	24	$1,920.00
3.3	Material	$/hr	$2,799.00	1	$2,799.00
3.4	Human	$/hr	$110.00	16	$1,760.00
3.5	Human	$/hr	$140.00	8	$1,120.00
4.1	Human	$/hr	$110.00	40	$4,400.00
4.1	Material	$/use	$2,599.00	1	$2,599.00
4.2	Human	$/hr	$80.00	24	$1,920.00
4.2	Material	$/use	$1,499.00	1	$1,499.00
4.3	Human	$/hr	$110.00	24	$2,640.00
4.4	Human	$/hr	$130.00	56	$7,280.00
4.4	Material	$/use	$4,999.00	1	$4,999.00
4.5	Human	$/hr	$140.00	24	$3,360.00
4.5	Material	$/use	$3,299.00	1	$3,299.00
4.6	Human	$/hr	$80.00	16	$1,280.00
4.6	Material	$/use	$1,499.00	1	$1,499.00
4.7	Human	$/hr	$80.00	16	$1,280.00
4.7	Material	$/use	$1,499.00	1	$1,499.00
4.8	Human	$/hr	$140.00	24	$3,360.00
4.9	Human	$/hr	$140.00	8	$1,120.00
5.1	Human	$/hr	$100.00	16	$1,600.00
5.2	Human	$/hr	$140.00	16	$2,240.00
5.3	Human	$/hr	$80.00	24	$1,920.00
5.4	Human	$/hr	$80.00	16	$1,280.00
5.5	Human	$/hr	$80.00	40	$3,200.00
5.6	Human	$/hr	$80.00	24	$1,920.00
5.6	Material	$/use	$1,499.00	1	$1,499.00
5.7	Human	$/hr	$80.00	16	$1,280.00
5.8	Human	$/hr	$140.00	8	$1,120.00
6	Human	$/hr	$140.00	8	$1,120.00
Total Cost Estimated	$99,931.00

b) The project budget can also be calculated by considering the expense of the individual project phases in the estimated time duration. The project budget estimation is implied for the calculating the all over resource usage in the individual project phase and then calculate the total cost of the project.  The following is a project budget estimation table,

Project Budget Estimation
Project Name: Development of Healthcare App for Koala City Council
Phase of Project	Resource Usage	Resource Type	Cost
Project Initialization	120 hrs	Human	$10,640.00
Project Planning	128 hrs	Human	$13,120.00
App Designing	104 hrs	Human	$10,960.00
	2	Material	$5,998.00
App development	232 hrs	Human	$26,640.00
	5	Material	$15,394.00
Go Live Application	160 hrs	Human	$14,560.00
	1	Material	$1,499.00
Project is Closed	8 hrs	Human	$1,120.00
Total Budget	$99,931.00

5.Project Stakeholders

a) The stakeholder analysis is done for ensuring that the project would comprise of the development of the improved communication in the organization (Heagney, 2012). The project of forming the improved project activities would require the deployment of the project analysis and deployment. The stakeholders of the project are Analyst, Documenter, Project Manager, Planner, Designer, Database Developer, Tester, Programmer, Engineer, and Trainer. They are responsible for the various activities of the project as listed below,

Project Stakeholder	Activities Involved in
Client- Koala City Council	Sponsoring the project
Analyst	Requirement Analysis
Stakeholder Analysis
Feasibility Analysis
Staff review is evaluated
Documenter	Initiation Documentation
Charter Documentation
Project Manager	Project Kick off meeting
Plan Approval
Project is Closed
Planner	Selection of plan methodology
Plan outline is formed
Plan is reviewed
Plan is completed
Application Launch Plan
Designer	App design software is selected
User Interface is designed
Design Review
Database Developer	Database is created
Integration of the database
Tester	Simulation of the design
Prototype Testing
Black box testing for functions
White box testing for functions
Beta test of usage
Programmer	Programming of the application functions
Engineer	Design is approved
System Alignment
System is reviewed
Application development is completed
Implementation of application launch plan
Application is launched for healthcare
Trainer	Development of training manuals
Training Programs are formed
Training is provided
Patients, Staffs and Nurses	Users of the Application

STAKEHOLDER ANALYSIS MATRIX

Project Title: Development of Healthcare App for Koala City Council Date Prepared: 14th January, 2018
Project Manager and Contractor	Client- Koala City Council
Patients, Staffs and Nurses	Analyst, Documenter, Planner, Designer, Database Developer, Tester, Programmer, Engineer, and Trainer

                                                                                                          Interest

The stakeholder analysis comprises of the various stakeholders grouped in terms of the interest and the power in the project operations. The stakeholder analysis has classified the project stakeholders in four sections namely High Power-Low Interest, High Power-High Interest, Low Power-High Interest, and Low Power-Low Interest. The project managers and contractors of the project have high power and low interest in the project activities. The client of the project (Koala City Council) acts as the stakeholder with high power and high interest. The patients, staffs and nurses acts as the stakeholder with low power and low interest. The project team members (such as analyst, documenter, planner, designer, database developer, tester, programmer, engineer, and trainer) act as the stakeholder with low power and high interest.

4. Project Cost

b) Communication Management is implied for forming the effective transfer of the information within the involved project stakeholders (Rodger et al., 2015). The stakeholders of the project are aligned with the development of the improved communication management. The transfer of the information is aligned for the management of the project activities and carrying out the specific analysis of the project operations. The communication management plan for the project is given below,

COMMUNICATIONS MANAGEMENT PLAN

Project Title: Development of Healthcare App for Koala City Council

Date Prepared: 14^th January, 2018

href=”#Stakeholder” title=”List the people or the groups of people who should receive project information.” Stakeholder	href=”#Information” title=”Describe the information to be communicated: For example, status reports, project updates, meeting minutes, etc.” Information	href=”#Method” title=”Describe how the information will be delivered. For example, e-mail, meetings, Web meetings, etc.” Method	href=”#Timing_or_Frequency” title=”List how often the information is to be provided or under what circumstances.” Timing or Frequency	href=”#Sender” title=”Insert the name of the person or the group that will provide the information.” Sender
Project Client	Project progress, resource exhaustion, and activities rescheduling	Board Meetings	Monthly	Project Manager
Project Team	Requirements of the project and the activity scheduling	Kick off meetings	Once	Project Manager
Users	Process of using the healthcare application and detailed analysis of the functions	Training Manuals	Once	Trainer
Project Manager	Technical requirements, complexities, and probable issues along with required solutions.	Project Progress Reports	Weekly	Engineer
Engineer	Functionality of the application is as expected or not	Test Results and Reports	Once	Tester

The table has shown that individual stakeholder of the project requires specific type of communication medium for a specific objective. The communication is implied for the management of the data transfer and implies improved conversation within the project activities. The project client can discuss with the project manager about project progress, resource exhaustion and activities rescheduling through board meetings on a monthly basis. The Project Team can discuss about the Requirements of the project and the activity scheduling through the kick off meetings once throughout the project lifecycle with the project manager. The users can discuss about the process of using the healthcare application and detailed analysis of the functions through the training manuals once throughout the project lifecycle with the trainer. The project manager can discuss the technical requirements, complexities, and probable issues along with required solutions through the project progress reports weekly throughout the project lifecycle with the engineer. The engineer can discuss the functionality of the application is as expected or not through the test results and reports once throughout the project lifecycle with the tester.

6.Project Risks

Project Risk Analysis is developed for ensuring that the effective and improved project operations are deployed for achieving the desired solutions (Bull et al., 2016). The project risk analysis is employed for analysing the risk factors and developing improved solutions for overcoming the probability of occurrence of the issues. The project would comprise of developing supportive plan for the application development so that the users can get the benefit of the faster health support. The risk register for the project is shown below,

RISK REGISTER

Project Title: Development of Healthcare App for Koala City Council

Date Prepared: 14^th January, 2018

href=”#Risk_ID” title=”Enter a unique risk identifier.” Risk ID	href=”#Risk_Statement” title=”Describe the risk event or condition. A risk statement is usually phrased as “EVENT may occur, causing IMPACT” or “If CONDITION exists, EVENT may occur, leading to EFFECT.”” Risk Statement	href=”#Probability” title=”Determine the likelihood of the event or condition occurring.” Probability	href=”#Impact” title=”Describe the impact on one or more of the project objectives.” Impact	href=”#Score” title=”If you are using numeric scoring, multiply the probability times the impact to determine the risk score. If you are using relative scoring then combine the two scores (such as high-low or medium-high).” Score	href=”#Response” title=”Describe the planned response strategy to the risk or condition.” Response
Scope	Quality	Schedule	Cost
1841	Incompatible Data is resulted in forming the issues in completion of the application	3	4	4	3	5	19	Data management should be implied for dealing with the issues of the incompatible data
1842	Errors in programming is resulted due to the issues in program development policy	3	5	3	2	5	18	The programming errors are sorted with the deployment of programming methods
1843	Application not working would be resulted due to inconvenient issues	1	3	5	3	4	16	Appropriate testing is helpful for overcoming the probability of the issues in working
1844	Cost Overrun is resulted when the activities of the project would exhaust more resources	4	2	3	5	4	18	Provisional budget allocation should be used for forming the support to the cost management
1845	Time Delay is resulted when the project activities cannot be completed in estimated time.	5	3	5	3	5	21	The issues in project time delay can be sorted by following a specific project plan

a) 

The project success can be measured with the help of the analysing the project outcomes in terms of deliverable success, process success, and stakeholder success. The deliverable success can be measured by the help of the calculating the project requirements that have been met. The project comprises of a key deliverable and some subsidy deliverables that are required for successful project completion. The achievement of these deliverables is also a measure of the project progress and success. The process success can be measured in terms of the method of managing and completing the project. The project management factors like timeline, cost estimation, communication, and control elements can be used for the analysis of the project success. The stakeholder success is more of a subjective measure type as it includes the coordination and communication in the project. The project success is dependent on the achievement of the client’s expectation from the project.

5. Project Stakeholders

7.Justification of Organisational Capacity to Undertake the Project

Kick-off Meeting

20^th April, 2018

Project Name: Development of Healthcare App for Koala City Council

Meeting Objective: Get the project off to an effective start by introducing key stakeholders and reviewing project preliminary scope, assumptions, constraints, and milestones.  

Agenda: Development of the Healthcare Mobile Application for Koala City Council that would help them for providing better treatment to the patients

• Introduction of attendees

The project kickoff meetings would be organized by the project manager and the attendees of the meetings would be the project team comprising of analyst, documenter, planner, designer, database developer, tester, programmer, engineer, and trainer.

• Review of project preliminary scope

Brief Scope Definition: The project scopes to the development of treatment facility to the patients of Koala City Council by using the Healthcare application development

Project Deliverables: Healthcare Mobile Application, Project plan, Cost Estimation/Budget, Risk Management Plan, Communication Plan, and Stakeholder Analysis Plan

Project Success Criteria: The project success criteria involve the project deliverable success, process success, and stakeholder success.

• Review of initial project stakeholder analysis

The initial project stakeholder analysis has yielded in client of the project (Koala City Council), patients, staffs and nurses, and project team as the primary stakeholders of the project.

• Review of initial project constraints

The initial constraints of the project are time, budget, and technology dependency as the project is an IT based

• Review of initial project milestones

The initial project milestones comprise of holding project kickoff meetings, developing an effective project plan, and designing the application for the healthcare.

• Action items for next meeting

The next meetings would comprise of dividing the project work in terms of the improved change management and scope management planning

The project of the Development of Healthcare App for Koala City Council is implied for the development of the improved facilities for the deployment of the project integration and development. The following assignment is a project management plan developed for the project of Healthcare Application Development for improving the facilities of the treatment of the patients. The assignment comprises of developing project charter, complete stakeholder analysis and communication plan, complete project scope, WBS for the project, Gantt chart for the project, project cost benefit analysis, network diagram and critical path, planned budget, and risk identification.

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.

Bull, J. W., Jobstvogt, N., Böhnke-Henrichs, A., Mascarenhas, A., Sitas, N., Baulcomb, C., … & Carter-Silk, E. (2016). Strengths, weaknesses, opportunities and threats: A SWOT analysis of the ecosystem services framework. Ecosystem Services, 17, 99-111.

6. Project Risks

Burke, R. (2013). Project management: planning and control techniques. New Jersey, USA.

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.

Davies, R., & Harty, C. (2013). Implementing ‘Site BIM’: a case study of ICT innovation on a large hospital project. Automation in Construction, 30, 15-24.

Gido, J. & Clements, J.P., (2014). Successful project management. Nelson Education.

Gozman, D., Wilcocks, L., Kovacevic, M., & Craig, A. (2017). Preparing for the wolf: sustainability through business continuity management. Intelligent Sourcing, (3), 50-63.

Heagney, J., (2012). Fundamentals of project management. AMACOM Div American Mgmt Assn.

Heldman, K., (2013). PMP: project management professional exam study guide. John Wiley & Sons.

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.

Kerzner, H.R., (2013). Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Kozma, R. B., & Vota, W. S. (2014). ICT in developing countries: Policies, implementation, and impact. In Handbook of research on educational communications and technology (pp. 885-894). Springer New York.

Kroczek, A., van Stam, G., & Mweetwa, F. (2013). Stakeholder theory and ICT in rural Macha, Zambia. In International Conference on ICT for Africa.

Leach, L. P. (2014). Critical chain project management. Artech House.

Marchewka, J.T., (2014). Information technology project management. John Wiley & Sons.

Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking project management performance and project success. International Journal of Project Management, 32(2), 202-217.

Nawi, H. S. A., Rahman, A. A., & Ibrahim, O. (2012). Government ICT project failure factors: project stakeholders’ views. Journal of Research and Innovation in Information System, 2, 69-77.

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.

Phillips, J. (2013). PMP, Project Management Professional (Certification Study Guides). McGraw-Hill Osborne Media.

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.

Rowell, C.J., (2016). Book Review: Project Management for Information Professionals. Library Resources & Technical Services, 60(4), pp.280-281.

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.

Schumann, C.A., Gerischer, H., Tittmann, C., Orth, H., Xiao, F., Schwarz, B. and Schumann, M.A., (2014). Development of International Educational Systems by Competence Networking based on Project Management. Procedia-Social and Behavioral Sciences, 119, pp.192-201.

Schwalbe, K., (2015). Information technology project management. Cengage Learning.

Snedaker, S. (2013). Business continuity and disaster recovery planning for IT professionals. Newnes.

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.

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.

Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons

Walker, A. (2015). Project management in construction. John Wiley & Sons

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.