Project Charter The WOWS Project

Question: Describe about the Project Charter for The WOWS Project. Answer: Background The project report is based on WOWS project involves the migration of the current paper based clinical documentation system into an advanced digital solutions. With the use of the digital solution, WGCI improves their quality of care with increase in efficiency as well as accuracy. The WOWS should improve over their current clinical system. This project intends to introduce current process to treat the employees. This system consists of the patients data to support the history of the patients. Problem Statement The problem statement is that the existing system of WGCI is paper-based system that makes the communication between the service provider and patients difficult. Due to this, there are lack of centralized data repository and insufficient process to analyze the information of the patients. Therefore, the current system of the organization is back dated and lack of use of technology. Project Vision The vision of the project is to implement WOWS in WGCI with development in 6 months with a budget of $700,000. The purpose of this project is to give accurate information on patients medical history. The vision of the organization is to target the patients by providing web based database driven prototype system to collect their information accurately. Project Objectives To develop a Web-based Oncological Working System for WGCI To complete the project plan within 6 months and a budget of $700,000 To update and maintenance of the patients information so that it an easily access Summary Budget Project Budget Item Cost (in $) Project management cost 120,000 Inherited data transfer 120,000 Training to the staff 50,000 Hardware requirements 122000 CRM licenses 140000 System software 148000 Total $700,000 Success criteria for the project The success factors of this WOWS project are the involvement of the user in the project work, support from the senior level management, and understanding of the hardware as well as software requirements of this project. Proper planning is required to be done before staring the project work such as accurate estimation of budget and schedule (Dalcher, 2015). Due to development of WOWS project, the proposed system can update and maintain the patients information. the entire data becomes centralized so that it can transfer from one location to another. Summary of the project management methodology Agile Methodology: This methodology is used for the project plan as with using this methodology the project plan gives significant flexibility as well as speed to the project plan. This methodology is best suited for the project, as it requires less control as well as real time communication with self-motivated settings of team (Randolph, 2014). This methodology is highly iterative as well as it allows for rapid adjustments through the project. Project Plan Project scope The scope of this project plan is divided into in scope and out scope and it is categorized as follows: In-scope Release Priority Story Story Name Description 16th Aug High Specific requirements of WOWS WOWS All the hardware and software requirements for proposed system are reviewed. 8th Sep Medium Development of training materials Training materials Training should be provider to the service providers of the patients so that they can handle the technical system, therefore development over the training materials are required to be providers to the systems users (Kerzner, 2013). 19th Sep Medium Design and Development Development of WOWS The scope is to develop the best methods to design, develop and quality control of the proposed system. Out of scope Out of scope item 1: The study is required for WGCI to change the market strategies as per the requirements of the patients. Out of scope item 2: Invitation to the targeted participants is required to get the feedback from them. Out of scope item 3: This study is required to aware WGCI about their current market position and strategies used. Assumptions, constraints and expectations Assumptions Assumption1: The assumptions are to be taken by the undertaking director is that every one of the deliverables are done such that the framework would track the status of the request given by the clients with hours spent with the end goal of charging (Verzuh, 2015). Assumption 2: Every one of the deliverables of the undertaking arrangement ought to be conveyed in the given due date and assessed spending plan. Assumption 3: The undertaking arrangement ought to be planned after the rules of the venture. Assumption 4: The issues are to be distinguished and the risk officer ought to find a way to maintain a strategic distance from those identified issues (Burke, 2013). Finally, taking into account the above presumptions the task arrangement must meet with the undertaking targets. Constraints Constraints Impact Use of system The project constraints are that the proposed system is platform independent and it should be kept secured from the unauthorized use. Technology Proper technology is not used and the system is not updated in time (Abdel Azeem, Hosny, Ibrahim, 2014). Time There is also a constraint of cost if the estimated budget is not covering the purchase of both hardware as well as software needed for the project (Kerzner, 2013). Resource There are constraints of resources if proper estimation of budget is not done on time. Expectations Expectation1: The project manager expects that they should complete the project plan within 6 months and within the estimated budget of $700,000. Expectation 2: The project manager also expects that they require more resources for successfully develop the WOWS for the clinical activities. Project Risks Risk Mitigation Strategy Technical Risk: There is failure in the system implementation and the equipments are outdated Due to failure in the system, it hampers the operations of business. The data are to be analyzed properly and the system should be kept up-to-date (Elkabets Shohet, 2012). Financial Risk: There is improper estimation of the budget and lack of fund. The scope of the project is required to minimize. The cost is to be estimated on time. The system requirements should be implemented as per the budget (Eric Kirkland, 2014). Operational Risk: There is error in handling of the system. The systems complexity is reduced and training should be given to the workers (Evans Pipkin, 2012). Schedule Risk: There is improper estimation of the time. Entire project plan should require to schedule properly with estimation of all the activities efficiently. Project Governance Figure 1: Project Governance (Source: Davis, 2014, pp-200) Project participants and its Roles and responsibilities Role Name Organization Responsibility Director Phil Smart Western Gippsland Cancer Institute (WGCS) Their responsibility is to control the overall situation of the company, its strategy and policy and monitoring the authority. Director Bill Bright Multimedia Computing, Communications, and Artificial Intelligence Research Their responsibility is to conduct meeting with the stakeholders and take business related decisions (Hallgren, 2012). Project Manager (Insert your name) WGCS The project manager manages the project and accomplishes the objectives within the project constraints (Maier Branzei, 2014). The person is also responsible for outcome of the project. Project Sponsor Dan Marino WGCS The project sponsor collects the funds for the project plan. Doctors Jelly Fundary WGCS The doctors take care of the required patients information and take care of their health. Business/ System Analyst Katty Kelly WGCS They have the skills to interpret the functional requirements of the business (Verzuh, 2015). Senior supplier Nick Chen WGCS The senior supplier estimates the additional work, supply the required raw materials and review the supply plan. Service provider Anny Andy WGCS The service provider maintains the data of the patients and stores their personal information into the WOWS. Database Administrator Anne Hathaway WGCS They develop as well as ensure the security and integrity of the database (Kerzner, 2013).Their roles are security, warehousing as well as architecture. Risk Officer Jack Hualy WGCS The risk officer identifies the risk and mitigates it on time. Summary schedule Date Milestone Deliverables 13th Aug Completion of the assumption of the hardware and software requirements Hardware and software requirements document 19th Sep Identify the in scope and out scope of the system Scope Document 4th Oct Design of the system plan Design Document of the proposed system 29th Oct Approval of the project plan Approval Document 16th Nov Hire of the required workers Human Resource plan document 12th Dec Testing of the system and user acceptance Testing Document 13th Jan Identification of the risks Risk Management Plan Sign-off section for all stakeholders Stakeholder Name of stakeholder Signature Director of WGCS Phil Smart Director of Multimedia Computing, Communications, and Artificial Intelligence Research Bill Bright Project Manager (Please insert your name) Project Sponsor Dan Marino Business/ System Analyst Katty Kelly Senior supplier Nick Chen Database Administrator Anny Andy Risk Officer Jack Hualy References Abdel Azeem, S., Hosny, H., Ibrahim, A. (2014). Forecasting project schedule performance using probabilistic and deterministic models.HBRC Journal,10(1), 35-42. Burke, R. (2013). Project management: planning and control techniques.New Jersey, USA. Dalcher, D. (2015). Introduction to Software Project Management.Proj Mgmt Jrnl,46(4), e2-e2. Davis, K. (2014). Different stakeholder groups and their perceptions of project success.International Journal of Project Management,32(2), 189-201. Elkabets, S., Shohet, I. (2012). Risk management model for critical infrastructures.Gerontechnology,11(2). Eric Kirkland, C. (2014). Project Management: A Problem-Based Approach.Project Management Journal,45(1), e3-e3. Evans, W., Pipkin, D. (2012). Risk management for the future of clinical negligence claims.Clinical Risk,18(1), 25-27. Hallgren, M. (2012). The construction of research questions in project management.International Journal Of Project Management,30(7), 804-816. Kerzner, H. R. (2013).Project management: a systems approach to planning, scheduling, and controlling. John Wiley Sons. Maier, E., Branzei, O. (2014). On time and on budget: Harnessing creativity in large scale projects.International Journal Of Project Management,32(7), 1123-1133. Randolph, S. (2014). Maximizing Project Value: A Project Manager's Guide.Project Management Journal,45(2), e2-e2. Verzuh, E. (2015).The fast forward MBA in project management. John Wiley Sons.