According to Schwalbe (2011) “in quality planning for projects, it is important to describe important factors that directly contribute to meeting customer’s requirement” (p. 297). As for Recreation and Wellness Intranet Project, in order to be sure that project team are not forgetting any requirements that might affect how different people view the quality of the project, it is important to adopt a quality management …show more content…
Some of these aspects includes the functionality of the intranet, features available with the intranet, output of the systems, performance of the system, its reliability, and maintenance requirement (Schwalbe, 2011).
Quality requirement for the Recreation and Wellness Intranet Project were identified from the stakeholders (project sponsor, senior managers, and system users) perspectives. These are identified with careful consideration for project scope statement.
Quality requirement from sponsor’s perspective:
a) A large percentage of registered user have used the system in about three (3) times in a week.
b) A weekly log is generated to show people who used the portal.
c) More than 65 percent of users have gave feedbacks confirming program has improved their health.
d) More than half of registered users have their health statistics compared in a before and after manner.
e) Close to 70 percent of register users have confirmed a significant reduction in the rate of clinic visitation
f) The system is able to support up to six (6) more programs in addition to the initial seven (7) programs within the first 8 months of …show more content…
c) The program is interesting and had fun using it.
d) The portal is fast and responsive and the rate of processing data is high in performance.
Measuring quality or progress on meeting the above listed quality requirements is an iterative quality process. Such that, it will be applied throughout the project delivery cycle. It will adopt a process that with as well focus on the process and product features. The measuring technics will capture data based on define metrics, analyze and process the data, and look towards improving the process in a continuous manner. A simple but informative, configurable, and dock-able dashboard will be built into the features of the system to provide a snapshot in real time. This will provide usage statistics and information on concurrent system users. Another feature will be built in to monitor and ensure system capacity is not use beyond 75 percent at any point in time. Registering and accessing the system shall be made simple from the user interface. The process of registration shall not take more than 3 to 5 steps. In addition, overall design shall be facilitated by user experience in