The project objectives drive the project schedule as well as the work breakdown structure. The iterative nature of the key objectives results in a nearly completely linear project execution plan. Within that project schedule the work breakdown structure follows the same progression.
The Second Life Project begins with the design of a workflow that will provide the schedule for the inpatient admission. In order to complete this task there must be a series of steps to ensure completion of the workflow. The first step is the design of the workflow. Designing the workflow then requires a validation of the requirements against the design and finally there is a validation of the workflow with key members of the team.
The computer screen design as well as the drop down menus will be required for the workflow. There is also a need to design for the search capability by the patient for visibility into the procedure, diagnosis and age. This follows the same standard operating procedure for developing key objectives in this project. The first is the initial design of the screens based on the requirements developed by the project team based upon the needs of the end users. Secondly a validation of the design will be accomplished by reviewing with the key end users that will cumulate with a validation review for sign-off.
Following the screen design and search capability creation, a patient survey is designed. While this will follow the standard procedure there is one deviation from plan. The initial step is to identify the target audience the survey is intended for. Next the drafting of the survey will take place followed by a validation among the project team. Validation occurs by comparing the project team’s expectations and the derived results of the survey.
The design of the database is critical due to the inherent reliance on the need to store, access and continually update the knowledge database. The steps in the creation include the design, validation and finalization. The validation will be completed through a series of tests completed utilizing data derived through sampling. The finalization will occur after testing and all requirements are met.
Testing the system is a cumulating progression of the initial four objectives. First a test plan is created based upon the key parameters and requirements of the project charter and requirements document. The test subjects are selected based upon sampling and they are used to test the system. The results are finalized after all requirements are met.
Following the testing of the system there needs to be a structured user acceptance testing. This finalizes and completes the project with a direct sign-off by the key stakeholders and end users of the system. In order to complete the user acceptance testing, test cases based upon system requirements will need to be created. These normally come as a series of user stories and scenarios based on the requirements. After the creation of those test cases testing will occur with the key points of users. The results are documented once complete and signoff is obtained.
Once signoff is complete training will begin with the targeted users. A training plan is created based upon usability of the system. Considering the user base multiple test sessions are planned and completed. Feedback is obtained from each session in order to continually improve the training experience.