READ AND RESPOND TO THIS DISCUSSION POST

a) Usually, robust testing is done to ensure the quality of the product is up to standards. Vigorous testing will be required if there are strict regulatory standards or complexity in the system that can result in defects or a history of poor quality issues from the organization or long-term maintenance concerns (Gericke et al., 2008). By performing these tests, hidden system issues can be identified, averted, and addressed to ensure regulatory standards are followed, preventing financial loss or damage to reputation from occurring.

b)With more testing, more quality assurance is gained. However, there are situations where limited resources and budget constraints can prevent more testing; thus, less testing would be applicable if appropriate. Another situation would be if the system has been proven to perform effectively with minimal errors.

c) As the project manager, I would provide a risk assessment and cost-benefit analysis that articulates the risks and effects of reducing testing, emphasizing its long-term impact on loss of funds and reputation, including providing alternative solutions that are more appealing in terms of time and budget while accentuating project objectives and organizational goals. The intent is to persuade stakeholders that further testing is in their best interest for the project to succeed. Communicating and keeping them engaged is essential in this process for them to understand the extent of the situation.

Reference

Gericke, K., Schmidt-Kretschmer, M., & Blessing, L. (2008). A FRAMEWORK TO UNDERSTAND PROJECT ROBUSTNESS. https://www.designsociety.org/download-publication/26706/A+FRAMEWORK+TO+UNDERSTAND+PROJECT+ROBUSTNESS