NR 543 W3 Test Plan SOLUTION

NR 543 W3 Test Plan SOLUTION

Create a plan to validate the information workflow change proposed in the workflow diagram and analysis assignment week 1;
identify issues that have implications for the practice of nursing informatics; and
acquaint the student with methods to develop test plans.
Develop a plan to validate (test) the proposed information workflow change from the workflow diagram and analysis assignment week 1 that demonstrates all the resources and processes required to ensure that your proposed change(s) work as designed without unintended consequences. Develop a plan that considers scope, schedule, acceptable deliverables (desired end products), resources (human, hardware, software, network and/or other equipment, space, budget), risks, and contingencies to validate changes and deliverables BEFORE change would be introduced into a live system. While you may not know exactly how long this would take or all of the resources required put on your thinking cap to propose a timeframe, budget, etc. Make this plan specific to your proposed change(s).
Introduction – identify workflow and brief background of the issue with the current process and the proposed changes to improve the workflow.
Test plan – should include a discussion of the “scope, schedule, acceptable deliverables, resources required (human, hardware, software, network and/or other equipment, space, budget), risks, and contingencies”
Methodology/Methodologies – can select more than one; discuss the details of how you plan to conduct each methodology. So, essentially, the methodology section answers the “how”.
Evidence-based Plan Development/Recommendations – rationale supporting your choice of methodologies
Conclusion – lessons you learned
If outlined this way, your paper is clearly showing that you are addressing all the required elements as listed on the rubric.

Test Plan

The provision of efficient healthcare services to patients in the patient care settings needs d

NR 543 W3 Test Plan SOLUTION

NR 543 W3 Test Plan SOLUTION

eliberate efforts on the part of the leaders to ensure that the workflow is simplified and not cumbersome to follow (McGrath et al.,2018). Workflow visualization is key in ensuring that individuals know crucial points, hence attending to tasks appropriately as outlined in the workflow. The multisite program or remote monitoring of Covid-19 patients has been using a current workflow to manage the patients who test positive for Covid-19. Even though the workflow has helped in achieving most of the set objectives, there are evident challenges that need to be addressed by modifying the workflow.

The first problem is the lack of information flow between clinicians and nurses as they provide technical support and response to escalations. It is crucial for clinicians and nurses to collaborate through data exchange, a critical component of electronic health records in health care delivery (Coffey et al., 2021). The other problem is the lack of triage and registration before confirming COVID-19. It should be included in the workflow to make it clearer and easy to link data flow. Therefore the purpose of this assignment is to create a test plan to validate the information workflow change that had been proposed. Therefore, the paper will address various aspects such as a plan to validate the proposal, methodologies, and evidence-based plan development.

The Test Plan

            Workflow testing entails mimicking the real environment into the testing phase to enable testing from an end-user’s perspective (Sheikh et al., 2017). Therefore, a workflow test helps examine various workflow characteristics and locate various issues that could hinder the workflow from efficient function or make the workflow fail. As earlier indicated, a proposal was put forth to enable adjustments to the current workflow in managing the patients who test positive for Covid-19. There is a need to include triad and registration before confirming covid-19 and creating a link for better data flow.

The Scope

This test plan covers the testing of the functionality of the adjusted workflow. It is worth noting that the organization already had an existing workflow to help address the Covid-19 positive cases among patients who visit the facility (Han et al., 2020). However, as earlier noted, there are two major problems that exist; lack of information flow between clinicians and nurses as they provide technical support and response to escalations and lack of triad and registration. Therefore, the scope of the test plan is to test the two newly introduced steps, which are to be integrated into the workflow.

The Schedule

Scheduling is key as it asks as a guide to the workflow testers to have in mind when a particular activity should be accomplished. Therefore the table below shows the proposed test schedule

Task Members Responsible Estimated time
Creation of test specifications The test designer 45 hours
Performing the test execution The Test administrator, the tester 20 hours
The test report Tester 5 hours
The test delivers The testing team 10 hours
Total 80 hours


The Acceptable Deliverables

As part of the test plan, the acceptable deliverables indicated what is expected out of the proposed or projected workflow testing or validation (Sheikh et al., 2017). In line with the purpose and scope of the test plan, various deliverables have been identified. While some of the deliverables are expected before the testing phase, some are expected during the testing phase, while the rest are expected after the completion of the testing cycle. The test deliverables before the testing phase are the test plans document, test cases documents, and test design specification. In addition, the targeted deliverables during testing include the test trace-ability matrix, the test data, and the test tool simulators. Upon the completion of the testing cycle, the following deliverables are expected; the release notes, the test procedure guidelines, defect report, and the test reports or results.

The Required Resources

 Resources are key in any stage or phase of a project as they allow a smooth completion of various tasks. Resources can take the form of human resources, hardware, software, network and/or other equipment, space, and budget (Kerzner, 2018). One of the main resources to be considered is the nurse manager. The test manager has vast experience in the process of project implementation and, therefore, will be a valuable resource. The test manager will be tasked with implementing the test plan in collaboration with physicians and other technical staff to achieve the set objectives of the test plan. Thus, the major tasks include the management of the entire project, defining the project’s direction, and acquisition of the necessary resources. The tester will also form an integral part of the team and will help identify and describe the appropriate test tools or techniques, verify and assess the most suitable test approach to use, execution the test, the results, and reporting of defects. The test administrator will also be helpful during the project. The test administrator will build up the test environment and ensure that all the assets are well maintained and managed. The administrator will also be expected to support the tester to effectively use the test environment to perform the execution.

The hardware resources are key in the sustenance of the software resources, the program, and other tools needed for effective and efficient use (Kerzner, 2018). Therefore, the expected hardware include server hard lines, the Local Area Network cables, test tool, and computers. They will need to be integrated into the organization’s existing mainframe to help improve the identified flaws in the existing workflow. The estimated budget for the whole testing phase is expected to cover the salaries for the identified team members or human resources and in purchasing the hardware and the software needed to accomplish the tasks effectively. As such, the resources will be acquired with the help of the human resource department after carrying out thorough market research to find the best prices.

Risks and Contingency Plan

Risks are part of any project, and therefore, a comprehensive plan should be in place to ensure that they are well managed when the risks come (Kerzner, 2018). One of the risks of this testing phase is the possibility of the failure to integrate the proposed new parts of the workflow into the existing workflow. Such a failure can have an adverse impact on the organization’s resources. In case such a risk occurs, then the project team plans to review the implementation process and find out the faults so that they can be corrected. The team will also check the compatibility of the proposed additions to the existing workflow.

The Methodologies

The methods are key and form an integral part of the test plan. The methodology answers the how question (Kerzner, 2018). Therefore, this section addresses the methods chosen for the testing plan. In addition, this section will also explore the advantages and disadvantages of the implemented methods and other methods that could have been useful in testing the changes. It is critical to note that, while the proposed changes are not an overhaul of the existing workflow for managing the patients who test positive at the facility, but the addition of more tasks or steps, the testing will be done for the whole system to ensure that the new proposed parts are functional and integrate well with the old parts of the workflow.

The method identified for testing is the agile methodology. The agile testing methodology follows the agile software development principles. This methodology fosters a continuous iteration of the development and testing throughout the whole project. The key feature of this method is that the activities run concurrent, that is, the testing and development activities. The methodology is among the simplest and most effective strategies. It uses continual planning, development, team collaboration, improvement, and delivery and enhances effective change responses (O’Regan, 2019). This testing method will therefore be a continuous process as opposed to being sequential. As such, the testing will start from the point of developing the process of information exchange between the clinicians and nurses as they provide technical support and response to escalations and the introduction of triage and registration.

Using the agile testing method will involve various aspects. For example, behavior-driven development will be used in testing the communication between clinicians and the nursing team to ascertain their understanding of the process. The other strategy involved is acceptance of test-driven development. This approach aims to involve test members with various perspectives like the tester and developer. While the developer focuses on how the problem should be sorted while the tester focuses on what might go wrong. The acceptance tests, therefore, represent the perspectives of the user and describe how the proposed system will operate and verify that the new workflow performs as initially expected (O’Regan, 2019). The exploratory testing will also form an integral part of the agile testing as the tester will identify the functionality of a particular process through an exploration.

The Advantages of the Agile Testing Methodology

The agile testing methodology has various advantages that make it suitable to be applied in the testing phase of this project. One of the major advantages is that the methodology is relatively cheap and saves time. As indicated earlier, agile methodology is one of the simplest strategies, eliminating any complexities and saving time (O’Regan, 2019). The other advantage is that it gives an opportunity to reduce documentation. Documentation can be a source of distraction, hence making the implementation deviate from the central focus. However, with the use of agile methodology, such documentation is greatly reduced.

The agile methodology is also highly adaptable and flexible to changes. There are usually several uncertainties during a project’s lifecycle which can derail the whole process. Agile methodology substantially negates the same as it is highly adaptable to the changes. The next advantage is that the agile methodology offers a platform for getting regular feedback from the users, which gives a chance to make necessary adjustments as appropriate (O’Regan, 2019). When using the agile testing strategy, the team has a better chance of deliberating on various issues through the necessary and frequent meetings. This gives the project a better chance of success.

The disadvantage of the Agile Testing Methodology

Even though the agile testing methodology is robust in testing the proposed workflow, the methodology may have various disadvantages. One of the disadvantages is potential poor resource planning. One of the underlying facts of this method is that the team may not have a clear picture of the end result. This brings a challenge of predicting the accurate efforts such as resources, time, and cost. The other possible disadvantage is fragmented output (O’Regan, 2019). Even though incremental delivery can be helpful in bringing results faster, the output can be fragmented since each team works on components in different cycles. The next disadvantage is difficult measurement. Agile gives results in increments which make the process of tracking difficult and complicated. In addition, it may be a challenge to see the key performance indicators at the start of the project.

Other Methods that can be used to Test Changes

As already discussed, the agile testing methodology will be used in the testing phase of the new information workflow. However, there are other strategies that could work in testing changes. For example, functional testing can be key in this case (O’Regan, 2019). Functional testing entails testing the new workflow against the facility requirement of better management of the patients who test positive for covid-19. This testing cuts across all the test types that are designed to ensure that every part of the whole process functions or behaves as expected. Such functions are evaluated using cases offered by the design team as a benchmark. Therefore, for this project, various functional testing processes can be undertaken including, acceptance testing, system testing, integration testing, and unit testing.

Evidence-Based Plan Development/Recommendation

It is prudent to use evidence-based strategies for testing the workflow as such strategies have been proven and tested. The agile testing methodology which has been suggested for this project is indeed an evidence-based strategy as it has been applied in various projects. Traditionally, software and information flow development and testing methodologies operate on the assumption that the requirements are constant from the start of the project to the end of the project (O’Regan, 2019). However, with an increase in research outputs, it is more evident complexities usually arise, leading to numerous evolution and changes in the requirements. This is where the agile methodology comes in as it entails incremental and rapid cycles where the interaction among the developers, testers, and the uses are emphasized and not the tools and processes. In addition, this methodology was chosen as it is the best to use when responding to change. The existing information workflow has been shown to have flaws that need to be corrected through various adjustments for better functionality. Therefore, the agile methodology takes center stage to respond to such projected changes of increasing information exchange between clinicians and nurses as they provide technical support and response to escalations and introduce triage and registration before confirming COVID-19.


In conclusion, the testing phase is key in any project development life cycle; therefore, a comprehensive test plan is key. Therefore, this write-up has addressed various aspects of the test plan. While the scope of the test plan is to test the two newly introduced steps, which are to be integrated into the workflow, the planned schedule has been projected to take eighty hours, and hopefully, the time will be sufficient. In addition, the project deliverables have been identified and divided into three types. While some of the deliverables are expected before the testing phase, some are expected during the testing phase, while the rest are expected after the completion of the testing cycle. The write-up has also explored various resources required to successfully complete the project, risk and contingency plans, and the appropriate methodologies.


Coffey, J. D., Christopherson, L. A., Glasgow, A. E., Pearson, K. K., Brown, J. K., Gathje, S. R., … & Haddad, T. C. (2021). Implementation of a multisite, interdisciplinary remote patient monitoring program for ambulatory management of patients with COVID-19. NPJ Digital Medicine4(1), 1-11.

Han, B., Li, Q., Chen, X., & Zhao, G. (2020). Workflow for intensive care unit nurses: A time and motion study. SAGE Open10(3), 2158244020947433.

Kerzner, H. (2018). Project management best practices: Achieving global excellence. John Wiley & Sons.

McGrath, S. P., Perreard, I. M., Garland, M. D., Converse, K. A., & Mackenzie, T. A. (2018). Improving patient safety and clinician workflow in the general care setting with enhanced surveillance monitoring. IEEE journal of biomedical and health informatics23(2), 857-866.

O’Regan, G. (2019). Concise guide to software testing (pp. 83-85). Springer International Publishing.

Sheikh, A., Bates, D. W., Wright, A., & Cresswell, K. (Eds.). (2017). Key Advances in Clinical Informatics: Transforming Health Care Through Health Information Technology. Academic Press.