Web Based Oncological Working System

Question: Discuss about the Web Based Oncological Working System. Answer: Project Background WOWS project is collaboration between Centre for Multimedia Computing, Communications, and Artificial Intelligence Research (MCCAIR) at Federation University Australia and the Oncology division of the Western Gippsland Cancer Institute (WGCI) at the Western Gippsland Hospital (WGH). Problem Statement There are manual processes that are followed in WGCI for maintaining patient information and medical records which lead to a number of challenges in terms of handling, storage and management of the same. The project will provide an automated and digitally advanced solution for WGCI to store, view and manage the patient information which will improve quality, efficiency and accuracy of medical care (www.tbs-sct.gc.ca., 2008). Project Vision For MCCAIR, WGCI Who will use the automated solution for automated management and storage of patients records The WOWS: Web-based Oncological Working System Is an Automated information systems That - will overcome the challenges of manual processes in handling and managing patient records (Rothman, 2013) Success Criteria Meeting the due deadlines for all the deliverables Completion of the project within defined budget Good customer feedback on the delivered solution Project Approach The project will be developed and managed by the Agile Development and Management Methodology. This approach would be ad-hoc and value driven in nature which will proceed in an iterative and incremental manner. The project will be developed in a series of sprints on the basis of product and sprint backlogs and will be achieve by Scrum team. Customer will be involved at every phase to provide with valuable feedback and the same will be incorporated in the sprints that will be executed thereafter. The final result will come in the form of an end product meeting all of the clients requirements and will include automated central data repository for storing the patient records and information, visual representation of the data and management of the same. Project Plan Project Scope In Scope Release Priority Story# Story Name Description 1 1 1 Interfaces Development of user and system interfaces for patients and medical professionals that will act as a portal for the solution 1 1 2 Login/Log Out Design, development and implementation of login and log out functionalities 1 1 3 Operations on Patient data Ability to view, edit, search and modify the information in an authorized manner 1 1 4 Patient Record Report HTML report of patients clinical information 1 1 5 User Administration Setting up of admin account and user privileges 1 1 6 Reporting Reporting functionalities associated with the data 1 2 7 Online Help Assistance and support with the functionalities of the portal Out of Scope The required changes in the existing hardware and equipment available with the associated parties will not be covered. Management of the third party vendors and associated activities will not be covered (projectyap.com, 2016). Project Participants Role Name and Organization Responsibility Co-CEOs Phil Smart, WGCI Bill Bright, MCCAIR Approval on project plan and other documents along with requirements specification Project Manager ABC Preparation of project plan, resource allocation, conduction of meetings Business Analyst IJK Analysis of the requirements gathered from all the varied sources Designer CDE Designing of the advanced digital solution Developer FGH Development of the advanced digital solution End-user LMN Acceptance testing and providing the user feedback Constraints, Assumptions and Risks Constraints Constraint Impact Project shall be completed in a maximum of 6 months An effort of 8 hours per day for 6 days a week for by team members failing which schedule overrun may occur leading to penalties Project shall be completed under $700,000 Accurate budget allocation and utilization of the same in all the project activities failing which budget overrun may be caused Actual patient data cannot be used during development and testing Test data to be developed for the designing, development, testing and implementation of the solution Assumptions and Dependencies The project will be completed in 6 months and under $700,000 The tools and equipment required for development and other activities will be made available to the team Client will be available for providing requirements and feedback during the agile development and management of WOWS Third party vendors will deliver the products on decided schedule (Lant, 2010) Risks Risk Mitigation Strategy Schedule Overrun Internal team meetings to re-strategize the project to compensate for the time exhausted Budget Overrun Re-allocation of the leftover budget in the remaining activities Technological Changes Migration to the newer technological tools and features in a step by step manner Security Risks Application of advanced security mechanisms such as access control, firewalls, anti-virus software and internet security (Galen, 2016) Quality Risks Quality audits on a frequent basis to validate and verify product quality after every sprint and in-between as well Resource Scarcity One-on-one discussions between resource and manager along with better HR policies (Cvsnead, 2013) Timeline Estimate Date Milestone and Deliverables 11th August 2016 Project Charter Document 25th August 2016 Project Plan 5th October 2016 System Design Document 19th October 2016 Release of Sprint 1 19th November 2016 Release of Sprint 2 19th December 2016 Release of Sprint 3 12th January 2016 Implementation Plan 20th January 2016 Test Report 30th January 2016 User Manuals 11th February 2016 Go-Live, Closure Report Budget Estimate A total of $700,000 will be allocated to complete all of the project activities. References Cvsnead,. (2013). Structured Agility: Developing an Agile Project Charter. TheAdaptivePM. Retrieved 10 August 2016, from https://theadaptivepm.wordpress.com/2013/04/04/sdlc-vs-agile-getting-chartered/ Galen, R. (2016). Agile Chartering - Beginning with the End in Mind. Projecttimes.com. Retrieved 10 August 2016, from https://www.projecttimes.com/robert-galen/agile-chartering-beginning-with-the-end-in-mind.html Lant, M. (2010). How To Make Your Project Not Suck by Using an Agile Project Charter. Michael Lant. Retrieved 10 August 2016, from https://michaellant.com/2010/05/18/how-to-make-your-project-not-suck/ projectyap.com,. (2016). ProjectYap - Projects - Collaborative Agile Project Management. Projectyap.com. Retrieved 10 August 2016, from https://projectyap.com/project.html Rothman, J. (2013). Keys to Chartering an Agile Project. ProjectManagement.com. Retrieved 10 August 2016, from https://www.projectmanagement.com/articles/280949/Keys-to-Chartering-an-Agile-Project www.tbs-sct.gc.ca.,. (2008). Project Charter Guide (1st ed.). Retrieved from https://www.tbs-sct.gc.ca.