Work Breakdown Structure WBS Paper

Work Breakdown Structure WBS Paper

Work Breakdown Structure WBS Paper

Electronic Medical Record Algorithms Project

  1. Preparation of the System

1.1.1 Design of the Electronic Medical Record Algorithm

1.1.2 Nursing Department User Interviews

1.1.3 Functional Requirement Determination

1.1.4 Determine the Technological Needs

ORDER NOW

Implementation – Work Breakdown Structure WBS Paper

Work Breakdown Structure WBS Paper

1.2.1 Establish the testing plan

1.2.2 Create Database Tables

1.2.3 Training of Departmental Heads on the use of the System

1.2.3 Training on Data Recording and Cleanup

1.2.4 Customization of the Electronic Medical Records Algorithm

Monitoring

1.3.1 Integration of the EMRA with the payment systems

1.3.2 Testing of the EMRA with the payment systems

1.3.3 Ad hoc process of Information Recording and Development

1.3.4 Setting up of the EMRA Gateway

Task Start Date Days to Complete
Design of the Electronic Medical Record Algorithm 19-Jul 7
Nursing department user interviews 26-Jul 7
Functional requirements Determination 2-Aug 7
Determine the technologies needs 9-Aug 7
Establish a testing plan 16-Aug 7
Establish an implementation plan 23-Aug 7
Create database tables 31-Aug 8
Training of Departmental Heads on the Use of the System
Train on Data Recording and Cleanup 6-Sep 6
Customization of the Electronic Medical Record Algorithm 13-Sep 7
Integration with the payment system 21-Sep 8
Testing 25-Sep 6
Ad hoc process of information recording and development 4-Oct 9
Setting up of the EMRA Gateway 11-Oct 7

 

The Gantt chart offers a horizontal bar chart that shows the process of controlling the planning and implementation of the EMRA gateway project. Gantt charts, therefore, provide a graphical representation as well as illustrations of the established project schedule that is intended at helping in the process of planning, coordination, as well as in the tracking (Alvarenga et al., 2018) of the EMRA gateway project as illustrated in the excel document.

For project management processes such as this, the Gantt chart remains critical in the illustration of the status of the EMRA gateway project status. Despite its efficacy, one needs to understand that one of the key challenges in using a Gantt chart relates to the fact that it may fail to indicate and provide the proponents of task dependencies (Bagchi et al., 2017). This factor makes it significantly challenging to understand and determine the tasks that often go off the scheduled period.

Nonetheless, the EMRA project schedules have been developed and confirmed by different stakeholders, hence warrant strict adherence to the schedules. The schedule details a set of restrictions that include the testing process of the plans that may need to be approved by the project teams before their execution. Further, the schedule makes it possible for one to identify the tasks that need to be executed daily (Alvarenga et al., 2018) and ensures project implementation adheres to the required quality (Baim-Lance et al., 2020).

A consideration of the risks involved remains a fundamental aspect that needs a priority, efforts that may play a critical role in establishing the impacts and the dependency of the tasks. A mitigation plan may equally need to be established before the project deadline. This process may involve the reliance on activity patch approaches that revolve around the use of conceptual measures. These measures should be designed to cater to the stakeholder’s expectations in relation to what the project expects to achieve.

References for Work Breakdown Structure WBS Paper

Alvarenga, J. C., Branco, R. R., do Valle, A. B., Soares, C. A. P., & da Silveira e Silva, W. (2018). Revaluation of the Criticality of the Project Manager to the Project’s Success. Business Management Dynamics, 8(2), 1–18. https://www.academia.edu/38198520/A_revaluation_of_the_criticality_of_the_Project_Manager_to_the_projects_success_pdf

Bagchi, T. P., Sahu, K., & Jena, B. K. (2017). Why CPM is not good enough for scheduling projects. IEEE International Conference on Industrial Engineering and Engineering Management (IEEM), Singapore. pp. 1748-1752, doi: 10.1109/IEEM.2017.8290191.

Baim-Lance, A., Onwuegbuzie, A. J. & Wisdom, J. P. (2020). Project management principles for optimizing productivity of mixed methods studies. The Qualitative Report, 25(3), 646-661.

N527PE_Project_Planning Instructions

The student will develop a project proposal, a project risk assessment, a work contract between the PC vendor & the hospital, a scope statement, a brief work breakdown structure, a cost estimate, a Gantt chart, and a succinct business case plan. Many templates are available for free download or able to be easily created.

**For the Gantt chart: You can use the applications Microsoft Excel or Microsoft Visio.  Microsoft Visio has a great template to use and may be available with certain Microsoft packages.

Microsoft Visio does not work on a Mac so feel free to use a product of your choice that will work on a Mac.  Mac technology questions are not supported. Other Resources are located below:

I have uploaded the templates provided. You can use the project of the hospital transitioning to a new electronic health record.

Assignment 2 Grading Rubric
Competency 15 points 14 points 13 points 0 points Points Earned
Project Proposal Develops and demonstrates a clear & precise project proposal inclusive of proposal essentials; supported with professional literature. Develops and demonstrates a project proposal inclusive of proposal essentials; supported with professional literature Develops and demonstrates a brief & vague project proposal while missing important details of the proposal essentials; supported with minimal professional literature. Does not develop a project proposal.   /15
A Contract Develops and provides a clearly written contract between the PC vendor & the hospital inclusive of essential elements. Develops and provides a written contract between the PC vendor & the hospital inclusive of essential elements. Develops and provides a brief written contract between the PC vendor & the hospital. Contract is missing essential elements. Does not develop a written contract.   /15
Project Scope Statement Develops and demonstrates a clear & precise written project scope statement inclusive of essential elements. Develops and demonstrates a written project scope statement inclusive of essential elements. Develops a vague project scope statement. Statement is missing essential elements. Does not develop a written project scope statement.   /15
Brief Work Breakdown Structure (WBS) Develops and demonstrates a clear & precise brief work breakdown structure inclusive of essential elements. Develops and demonstrates an ambiguous work breakdown structure inclusive of essential elements. Develops a vague work breakdown structure. Structure is missing essential elements. Does not develop a brief work breakdown structure.   /15
A project cost estimate Develops and demonstrates a clear & precise cost estimate for the entire healthcare project. Develops and demonstrates a project cost estimate inclusive of most essential elements. Develops a vague cost estimate. Estimate is missing essential elements. Does not develop a cost estimate of the project.   /15
Gantt Chart Develops and demonstrates a clear, timely & precise Gantt chart for the entire healthcare project. Develops and demonstrates a Gantt chart inclusive of most essential elements. Develops a vague Gantt chart. Gantt chart is missing essential elements. Does not develop a Gantt chart.   /15
Competency 5 points 4 points 3 points 0 points Points Earned
Succinct business case plan Develops and demonstrates a clear & succinct business case plan for the entire healthcare project. Develops and demonstrates a business case plan inclusive of most essential elements. Develops a vague business case plan. Case plan is missing essential elements. Does not develop a business case plan.   /5
Competency 5 points 4 points 1 Point 0 points Points Earned
Grammar, spelling, and punctuation AND APA Compliance There are no errors in grammar, spelling, and punctuation AND The paper meets APA format guidelines There are a few minor errors in grammar, spelling, and punctuation that do not detract from the meaning OR There are minor APA format errors There are major errors in grammar, spelling, and punctuation that do not reflect scholarly writing OR There are significant errors in format Content Missing   /5
 
Total Points /100


Background

[Why is the project being undertaken? Describe an opportunity or problem that the project is to address.]

Objectives

  • [specific & measurable objective 1]
  • [specific & measurable objective 2]
  • [specific & measurable objective 3]


Scope

[What will be the end result of the project? Describe here what phases of work will be undertaken.]

 

Timeframe

Description of Work Start and End Dates
Phase One
Phase Two
Phase Three


Project Budget

Description of Work Anticipated Costs
Phase One
Phase Two
Phase Three
Total      $   0.00


Key Stakeholders

Client [name]
Sponsor [name]
Project manager [name]



Monitoring and Evaluation
[Describe how progress will be evaluated throughout and at the end of the project. Formulate clear indicators for objectives and result.]

 

Approval Signatures

 

[Name], Project Client [Name], Project Sponsor [Name], Project Manager

 Risk Register

Risk Identification Qualitative Rating Risk Response
Risk Risk Category Probability Impact Risk Score Risk Ranking Risk Response Trigger Risk Owner
0 1
0 2
0 3
0 4
0 5
0 6
0 7
0 8
0 9
0 10
0 11
0 12
0 13
0 14
0 15
0 16
0 17
0 18
0 19
0 20
0 21
0 22
0 23
0 24
0 25
0 26
0 27
0 28
0 29
0 30
Key Terms
Risk: The risk stated in a complete sentence which states the cause of the risk, the risk, and the effect that the risk causes to the project.
Risk Category:  Categorization of risks by area of project affected, source of risk or other useful category.
Probability:  The likelihood that a risk or opportunity will occur (on a scale from 0 to 10 with 10 being the highest).
Impact:  The impact of the risk on the project if the risk occurs (scale from 0 to 10 with 10 being the highest).
Risk Score:  Determined by multiplying probability and impact (scale from 0 to 100).
Risk Ranking:  A priority list which is determined by the relative ranking of the risks (by their scores) within the project with the number one being the highest risk score.
Risk Response:  The action which is to be taken if this risk occurs.
Trigger: Something which indicates that a risk is about to occur or has already occured.
Risk Owner: The person who the project manager assigns to watch for triggers, and manage the risk response if the risk occurs.
This Risk Register Template is brought to you by www.projectmanagementdocs.com

Project Cost Estimate

Project Estimated Hours Developers Analysts Others Total Cost Status
Phase Req. Avg. Cost Req. Avg. Cost Cost
1 Phase 1 12 3 $90 6 $90 $90 $900
1.1 Phase 1.1 5 1 $30 1 $30 $30 $330
1.2 Phase 1.2 5 1 $30 0 $30 $30 $180
1.3 Phase 1.3 2 1 $30 5 $30 $30 $390
2 Phase 2 20 13 $90 6 $90 $90 $4,740
2.1 Phase 2.1 5 1 $30 1 $30 $30 $330
2.2 Phase 2.2 5 5 $30 0 $30 $30 $780
2.3 Phase 2.3 10 7 $30 5 $30 $30 $3,630
3 Phase 2 6 7 $90 18 $150 $150 $1,020
3.1 Phase 3.1 1 2 $30 3 $30 $30 $180
3.2 Phase 3.2 1 2 $30 3 $30 $30 $180
3.3 Phase 3.3 2 1 $30 3 $30 $30 $270
3.4 Phase 3.4 1 1 $30 4 $30 $30 $180
3.5 Phase 3.5 1 1 $30 5 $30 $30 $210
Total 38 23 30 $330 $6,660