PRojec software development
shanta75
ITPM1.docxPROJECT:
Objectives
1. To better understand how a software development project is managed from initiation to closure.
2. To better understand what project management plan consists of.
3. To prepare a project management plan for a software development project that has been identified for this semester project.
Project Description
The project requires you to identify a software development project for any industry and prepare a Project Management Plan (PMP) for managing the project from initiation to closure. The Project Management Plan will include the following sections and items:
· Project Quality Management Plan - 6 points
· Quality Assurance Plan
· Test Plan and Strategy
· Project Communications Management Plan - 8 points
· Stakeholder Communications Requirement
· Methods of Communication
· Frequency of Communication
· Performance and Progress Reporting
· Project Risk Management Plan - 6 points
· Risk Register
· Risk Response Plan and Strategy
· Project Stakeholder Management Plan - 5 points
· Stakeholder Register
· Expectations Management Matrix
Peer Review: 10 points
You will prepare the Project Management Plan with all the above sections and items (bulleted list) in MS Word format using APA Documentation Style. For help with the APA Documentation Style, you can visit https://www.pvamu.edu/library/wp-content/uploads/sites/48/apa-reference_list_style_guide.pdfLinks to an external site.. You will embed other files (e.g. Network Diagrams, MS Excel or MS Project file) into the Word file. Ask in the class if you do not know how to embed a file into another . You'll store all the files in a folder and compress (zip) the folder so you can submit the compressed (zipped) folder.
Systemx Hospital Pharmaceutical Tracking Database
(S.H.P.T.D)
Table of Contents
Overview…………………………………………………………………………………….
Introduction………………………………………………………………………………….
Project Management Plan Approach……………………………………………………….
The Business Case…………………………………………………………………………
Project Infrastructure……………………………………………………………………….
Project Governance………………………………………………………………………
Project Team…………………………………………………………………………….
Project Charter…………………………………………………………………………..
Project Scope Management Plan…………………………………………………………….
Scope Statement…………………………………………………………………………
Scope Change Control Procedures………………………………………………………
Work Breakdown Structure………………………………………………………………...
Project Time Management Plan…………………………………………………………….
Project Cost Management Plan……………………………………………………………..
Project Cost Estimation………………………………………………………………….
Project Budget Determination……………………………………………………………
Project Quality Management Plan………………………………………………………….
Quality Management…………………………………………………………………….
Tools and Techniques to be Used………………………………………………………….
Test Strategy and Plan……………………………………………………………………
Project Resource Management Plan…………………………………………………………
Organizational Chart……………………………………………………………………….
Responsibility Assignment Matrix……………………………………………………………
Tools and Techniques for Managing Team………………………………………………….
Project Communication management Plan…………………………………………………….
Stakeholder Communication Analysis……………………………………………………….
Performance and Progress Reporting………………………………………………………..
Project Risk Management Plan………………………………………………………………….
Risk Breakdown Structure…………………………………………………………………..
Sources of Risks …………………………………………………………………………….
Risk Register………………………………………………………………………………..
Introduction
Our team will design a new prescription pharmaceutical tracking system for a major hospital in the Houston Texas area. The old system was extremely vulnerable to cyber-attacks and IT infrastructure outages. Additionally, the central database for prescription drugs could not handle the massive amount of data that was being queried and imputed by hospital administration. The hospital we are consulting with is a tier 5 trauma center, which means it is extremely large and terribly busy. The senior hospital executives have requested the development of a system that is more intuitive and experiences less system errors. In essence our team is tasked with building a more robust and efficient enterprise prescription tracking system
Project Management Approach
The Systemx Hospital Pharmaceutical Tracking Database will use an agile based approach to provide the final enterprise healthcare application system. The project team will effectively and efficiently navigate through the five process groups where a feature is completely finished before moving on to another feature. The primary objectives of this project are to complete each feature within scope and time constrains while being considerate of cost. The final project should increase small business information distribution and data integrity by 40% and reduce critical IT infrastructure failures by 90% across all Houston area hospitals. The project plans will be reviewed and accepted before the initiation of the project.
The approach should go as followed.
· Identify healthcare stakeholders and conduct surveys and determine what key information should be featured in the enterprise pharmaceutical application.
· Research software requirements that will adhere to storage, data surety , and platform infrastructure requirements.
· Use an interactive approach to develop the enterprise application. Imperative to project success is critical relevant feedback.
· Set performance metrics to ensure value creation and control any deviations.
The Business Case
Current Situation
The old system for pharmaceutical order tracking used by Houston area hospitals was extremely vulnerable to cyber-attacks and IT infrastructure outages. Additionally, the central database for prescription drugs could not handle the massive amount of data that was being queried and imputed by hospital administration. The hospital utilizing this technology tier 5 trauma center, which means it is extremely large and extremely busy. This means that if their IT systems fail or are unable to hold land send large volume of patient information, they could lose hundreds of millions of dollars in state funding. The stake holders of this project are the patients, staff and benefactors of the Houston are Hospital healthcare system. This project will deliver an enterprise application that is secure, easy to use, able to handle massive volume of patient data and is easy to query and expand.
Analysis of the Situation
The strategy to complete this project is to use an agile approach to produce deliverables and effectively adhere to the triple constraint. The goal of this project is to deliver within scope, time, and cost objectives, as well as adding value to the Houston hospital healthcare system by improving data pipeline integrity, network security and data sharing by 70% in the Houston area. The Hospital already has adequate information technology and support staff needed to complete the enterprise project. An external healthcare informatics, analyst and a clinical pharmaceutical programmer will be hired to serve as consultants on the project.
There are several know risks.
· Security of the clinical database
· Overloading of the current data warehouse
· Total system failures within the IT apparatus
· Data corruption when sending and receiving clinical data.
Critical Success Factors
· Time constrainers are met.
· Scope goals are met.
· Quality assurance maintained during project.
· Healthcare clinical data integrity increase by 70%
· Pharmaceutical data tracking increase by 70%
· IT security infrastructure hardened by 40%
Analysis of Options
Do nothing – Hope that awareness of healthcare pharmaceutical data issues increase on its own in the healthcare industry.
Do the minimum- Create an enterprise application that limits the damage done by faulty healthcare application and organizes and record pharmaceutical data.
Do more than the minimum – Create an enterprise healthcare application that store organizes and categorizes clinical pharmaceutical data and can automatically cross reference it with stored patient data and doctor notes. Additionally, integrate firewalls and virus scanning tool into hospital IT infrastructure to maintain data confidentiality.
Recommendation
The recommendation is to do more than the minimum. Create an enterprise healthcare application that organizes clinical pharmaceutical data automatically cross reference it with stored patient data and doctor notes. The integrate of firewalls and virus scanning tool into existing hospital IT infrastructure will data confidentiality. These additional features will improve hospital performance and patient diagnosis and treatment.
Assumptions
· Project management plan is a living document.
· All tools’ techniques and templates will be overseen by a project manager.
· The enterprise tool will be created with python.
· An iterative agile approach will be used.
Schedule Estimate
The project will be completed in 12 months
Budget Estimate
The total budget of the project is $200,000
Project Infrastructure/Governance
Figure 1 Pharmaceutical Tracking Project Governance diagram
Project Charter
Project Title: Systemx Hospital Pharmaceutical Tracking Database (S.H.P.T.D)
Project Start Date: May 5, 2021
Project Finish Date: April 1, 2022
Budget Information’s: $200,000 have been allocate to complete this project. Majority of costs will be due to labor.
Project Manager: Paul Beck, (713)-543-6767, [email protected]
Project Objectives: The Systemx Hospital Pharmaceutical Tracking Database will use an agile based approach to provide the final enterprise healthcare application system. The project team will effectively and efficiently navigate through the five process groups where a feature is completely finished before moving on to another feature. The primary objectives of this project are to complete each feature within scope and time constrains while being considerate of cost. The final project should increase small business information distribution and data integrity by 40% and reduce critical IT infrastructure failures by 90% across all Houston area hospitals. The project plans will be reviewed and accepted before the initiation of the project.
Media Project Success Criteria: The enterprise application will improve IT infrastructure integrity, clinical data storage capacity and network security by 70%.
Approach:
· Identify healthcare stakeholders and conduct surveys and determine what key information should be featured in the enterprise pharmaceutical application.
· Research software requirements that will adhere to storage, data surety , and platform infrastructure requirements.
· Use an interactive approach to develop the enterprise application. Imperative to project success is critical relevant feedback.
· Set performance metrics to ensure value creation and control any deviations.
Project Team
Roles & Responsibilities
|
Role |
Name |
Position |
Contact Information |
|
Project Sponsor |
Cynthia Maxwell |
Hospital President | |
|
Senior Manager |
Paul Beck |
Chief Information Officer | |
|
Project Specialist |
Alexander Gram |
Chief Medical Officer | |
|
Project Manager |
Richard Grantham |
Healthcare Associate | |
|
Steering Committee |
Stella Cox |
Pharmaceutical Policy Analyst | |
|
System Administrator |
Rood Wilson |
System Administrator | |
|
System Analyst |
Shaun Baker |
System Analyst | |
|
Technical Lead |
Shamar Griffin |
Technical Lead | |
|
Technical Trainer |
Tiana White |
Technical Trainer | |
|
Hardware Engineer |
Johnathan Black |
Hardware Engineer | |
|
Recruitment Analyst |
Scythia Woods |
Recruitment Analyst | |
|
Technical Clerk |
Clark Henderson |
Technical Clerk | |
|
Software Engineer |
Marcus Rockwell |
Software Engineer | |
|
Database Engineer |
Paul Proteus |
Database Engineer | |
|
Technical Support |
Sheila Zass |
Technical Support | |
|
QA Manager |
Marcus Yang |
QA Manager | |
|
Web Designer |
Chris Masterson |
Web Designer | |
|
Documentation |
Layla Brookes |
Documentation |
Sign-Off: (Signatures of all above stakeholders. Can sign by their names in table above.)
Comments: (Handwritten or typed comments from above stakeholders, if applicable)
Project Scope Management Plan
Scope Statement
Project Title: Systemx Hospital Pharmaceutical Tracking Database (S.H.P.T.D)
Date: May 3, 2021 Prepared By: Paul Beck CIO, Project Manager
Project Summary and Justification: The old system for pharmaceutical order tracking used by Houston area hospitals was extremely vulnerable to cyber-attacks and IT infrastructure outages. Additionally, the central database for prescription drugs could not handle the massive amount of data that was being queried and imputed by hospital administration. The hospital utilizing this technology tier 5 trauma center, which means it is extremely large and extremely busy. This means that if their IT systems fail or are unable to hold land send large volume of patient information, they could lose hundreds of millions of dollars in state funding. The stake holders of this project are the patients, staff and benefactors of the Houston are Hospital healthcare system. This project will deliver an enterprise application that is secure, easy to use, able to handle massive volume of patient data and is easy to query and expand.
Project Characteristics and Requirements:
1. Hospital and medical center submission: Hospital president s and Chief medical officers will be encouraged to send all their information to Paul Beck so that it can be uploaded and integrated into the new Systemex systems.
2. Links: All C Suite links will be tested on a weekly basis. I link is broken stakeholders will be benefited and an alert will be sent out.
3. Data warehouse up grades: enterprise application should be infinite expandable and should be ale to collect to a clou platform or be cross compatible with an external PaaS.
4. Security: Computer networks must be hardened, and data pipelines must be made secure physical security must also be incorporated through biometrics and key codes
5. IT Infrastructure maintains: Software must be easy top maintain to ensure 24/7 IT infrastructure functionality.
Summary of Project Deliverables
Project Management related deliverables: Business case, charter, team contract, scope statements, WBS, schedule, cost baseline, status reports, surveys, design documents, software code, final projects presentation, final project report, lessons learned report, and any other documents required to manage the project.
Product related deliverables:
1. Data Warehouse Upgrade: Improve storage capacity of current data warehouse. Prepare IT Infrastructure for massive data expansion and overhaul.
2. Enterprise Software Application: Research ,design and develop advanced software to stem problems related to in adequate healthcare legacy software. Ensure that new software is easy tom implemented and is compatible with new data warehouse upgrades.
3. Security upgrade: Design and employ firewalls, VPN’s and security monitoring protocol to mitigate threats form trojans and other common malware.
Project Success Criteria: Our goal is to complete this project in 8 months with a budget of $200,00. When completed the new system modifications should increase hospital information distribution and data integrity by 40% and reduce critical IT infrastructure failures by 90% within the Hospital.
Scope Change Control Procedures
It is imperative that the project manager is made aware of all changes in regard to the project. This involves ensuring beneficial changes, determining a change has occurs , and managing and changes. In order to maintain the balance of the triple constraint (time, cost, and scope), all changes must be formally documented. To avoid scope creep, procedures are in place that brings any change request through an integrated change control process that must be approved by the project manager an ultimately the project management board which includes a change control board.
The change control systems is integrated with the project management information system in order to easily control the project scope, The change control systems includes request producers documentation, verification tracking systems and approval rejection.
Scope verification must be communicated to the project manager, project management board, steering committee, and stakeholder. Even if a change is minor and verbally accepted, it still has to be formally documented.
This project will use the scope change control procedure followed by the Project Management Institute.
Steps for Change Control:
1. Be Lean – Limit the scope of change and focus on immediate needs.
2. Define preliminary scope – Having a structure; approach of documenting, evaluating, and approving preliminary scope of work
3. Understanding final Acceptance – Understanding how the project sponsors and project management board formally accept changes
Work Breakdown Structure
Prepared by: Bilal Marquis Date: May 3, 2021
1. Initiating
1. Identify Stakeholder
2. Prepare Project Charter
3. Hold Kick-off meeting
2. Planning
1. Prepare scope statement.
2. Prepare WBS
3. Prepare Schedule
3. Determine Task Durations
3. Determine Task Dependencies
3. Create Network Diagram
3. Create Gantt Chart
2. Identify and Prioritize risks
1. Executing
3. Survey
3. User Inputs
3. Enterprise Application Features
3. Links
3. User Request Feature
3. Search Feature
3. Design Database
3. Design Enterprise Application
3. Construct Enterprise Database
3. Test Enterprise software and database application
3. Launch Enterprise software
3. Project benefits measurement
1. Monitoring and Controlling
4. Progress reports
4. Working data pipelines
1. Closing
5. Prepare final project report
5. Prepare final presentation
5. Lessons Learned
Milestone List
