Projects R Us
By: Mike • Research Paper • 755 Words • February 21, 2010 • 792 Views
Join now to read essay Projects R Us
1.0 Introduction
This report details the Project Plan for Medix to initiate the Software Development Project as outlined in the Project Description. Medix has been formed by the amalgamation of 5 traditional medical practices. Medix is struggling to combine the different record keeping and document management systems of the five practices. This project will combine traditional hard-copy systems and some primitive computer-based systems into a more usable and modern system.
Prior to the development of the software, new staff will be recruited and trained early in the project to help accelerate the project and save time. A prototype will be constructed; If successful, a design will be formulated and coding will begin for the software; and integration of the software with the overall medical system.
2.0 Purpose
The purpose of this document is to outline how Projects-R-US will manage the software development Project for Madix. Projects-R-US has chosen to prototype the new software development in order to make sure the system meets the requirements as stated, and the fact that it is a medical records system; the information must be verified and correct at all times. It is vital for the software to work properly the first time.
2.1 Scope
2.1.1 Inclusion
This project is limited to software development for Madix.
2.1.2 Document
The document covers the following key areas
1. Project Plan
2. Staffing Plan
3. Project Costs
4. Risk Management Plan
2.1.3 Exclusions
The following areas below will not be covered in this project.
• Maintenance of Software
• Implementation of Software
• Operation of Software
• Software Licensing and any other licenses required to run the required software.
2.1.4 Assumptions
The following assumptions apply to the project.
• All personnel are available as required for the project.
• The project will be fully financed by Madix.
• During recruitment selection period (week 3 and 4 of recruitment phase) Project Manager can select (interview and selection committee meeting process) more than one applicants.
• Staffs or new staffs who are not occupied in any task will not cost the project.
• Project Manager is responsible for all activities of the project from beginning to project sign off.
• Project Quality assurance is not priced in the project.
• Prototyping is for testing purposes only.
• Staff will be available for the entire project.
• There are no shortages in the Senior Programmers.
• Contractors may be used as required to keep the project on track and where there is a shortage of specialized skilled staff.
2.1.5 Constraints
The main constraints to the project are:
• Time
The project may fall behind schedule. This may lead to an increase in expenses.
• Resistance to Change
Some staff may hold some resistance to change. This is inevitable and proper training and job placement will reduce minimise this constraint.
3.0 Project Cost
The total costs for the project is estimated at $554,150. A more detailed breakdown of the figures, please refer to appendix 1. The project will take about 9 months to complete.
Month Total
July 2004 $8,000
August 2004 $64,320
September 2004 $45,480
October 2004 $36,000
November