SCOPE MANAGEMNET PLAN
Scope Objective: The objective of the project is to expand the Clinical Data warehouse and to allow and consume the data from the vendors and onsite clinic data. The scope of the project was to create a modular software package to handle wellness vendor data to ensure appropriate preventative care is being tracked for members, including the systems changes, the vendor wellness database tables, and wellness vendor reporting.
Scope Management Approach: For the project Medical Informatics, scope management will be the sole responsibility of the Project Manager. The scope for this project is defined by the Scope Statement, Work Breakdown Structure (WBS) and Project scope statement. The Project Manager and Stakeholders will establish and approve documentation for measuring project scope which includes deliverable quality checklists and work performance measurements. Proposed scope changes may be initiated by the Project Manager, Stakeholders or any member of the project team. All change requests will be submitted to the Project Manager who will then evaluate the requested scope change. Upon acceptance of the scope change request the Project Manager will submit the scope change request to the Change Control Board and Project Sponsor for acceptance. Upon approval of scope changes by the Change Control Board and Project Sponsor the Project Manager will update all project documents and communicate the scope change to all stakeholders. Based on feedback and input from the Project Manager and Stakeholders, the Project Sponsor is responsible for the acceptance of the final project deliverables and project scope.
ROLES AND RESPONSIBILITIES: The Project Manager and team will all play key roles in managing the scope of Medical Informatics project. As such, the project manager, and team members must be aware of their responsibilities in order to ensure that work performed on the project is within the established scope throughout the entire duration of the project. The table below defines the roles and responsibilities for the scope management of this project.
|Srikanth Kadama||Sponsor||· Approve or deny scope change requests as appropriate· Evaluate need for scope change requests· Accept project deliverables|
|Venkata Keerthi||Project Manager||· Measure and verify project scope· Facilitate scope change requests· Facilitate impact assessments of scope change requests· Organize and facilitate scheduled change control meetings· Communicate outcomes of scope change requests· Update project documents upon approval of all scope changes|
|Tej Chilukuri||Team Lead||· Measure and verify project scope· Validate scope change requests· Participate in impact assessments of scope change requests· Communicate outcomes of scope change requests to team· Facilitate team level change review process|
|Sruthi Kovvali||Team Member||· Participate in defining change resolutions· Evaluate the need for scope changes and communicate them to the project manager as necessary|
|Jeffery Brown||Team Member||· Participate in defining change resolutions· Evaluate the need for scope changes and communicate them to the project manager as necessary|
The scope for Medical informatics was defined through a comprehensive requirements collection process from all sources including third party services, clients and employees. First, a thorough analysis was performed on the company’s current software applications based on employee and user feedback. From this information, the project team developed the project requirements documentation, the requirements management plan, and the requirements traceability matrix for what the new software application must accomplish.
The project description and deliverables were developed based on the requirements collection process and input from tem members in software design, technical support, programming and business applications. This process of expert judgment provided feedback on the most effective ways to meet the original requirements of providing a new software platform from which the project Medical Informatics can improve financial planning and working of the project.
PROJECT SCOPE STATEMENT:
· Project Objective: The scope of the project was to create a modular software package to handle wellness vendor data to ensure appropriate preventative care is being tracked for members, including the systems changes, the vendor wellness database tables, and wellness vendor reporting. The project was divided into modules consisting of: wellness DB tables, promote tables, and wellness vendor reporting. A project manager was appointed, but has since left due to personal reasons
1. Will be creating software for the user usage and can be used to track the members and update the changes.
2. This project will consists of modules for wellness database and Promote tables
3. The project will also have wellness vendor reporting tool
4. The project will done in the allocated budget and time.
5. The module will have authorization and security measurements involved in it.
1) Project Planning —— December 22, 2015
2) Evaluation Plan——– January 2, 2016
3) Development of software—- January 10, 2016
4) Testing Debugging and changes implications——- January 29,2016
5) Final Inspection—— February 21,2016
· Limitations and Exclusions:
1) The project must be developed according to the user requirements
2) The project must not exceed the allocated budget and time
3) Project Manager and the Team are given the responsibility to make any changes in the application.
4) The application is limited to fewer platforms.
5) The application is not an open source but can be bought from the company with licensed version.
WORK BREAKDOWN STRUCTURE: In order to effectively manage the work required to complete this project, it will be subdivided into individual work packages which will not exceed 40 hours of work. This will allow the Project Manager to more effectively manage the project’s scope as the project team works on the tasks necessary for project completion. The project is broken down into three phases: the design phase; the programming phase; and the testing phase.
SCOPE VERIFICATION: As this project progresses the Project Manager will verify interim project deliverables against the original scope as defined in the scope statement, WBS and Scope Statement. Once the Project Manager verifies that the scope meets the requirements defined in the project plan, the Project Manager and Stakeholders will meet for formal acceptance of the deliverable. During this meeting the Project Manager will present the deliverable to the Project Sponsor for formal acceptance. The Project Sponsor will accept the deliverable by signing a project deliverable acceptance document. This will ensure that project work remains within the scope of the project on a consistent basis throughout the life of the project.