Quality Management – Little Things Do Matter

The role of Quality Assurance in the development of a software product is often underestimated by the project stakeholders. In most cases, this happens not due to the key stakeholders’ unwillingness to accept that a robust QA mechanism adds great value to the product, but more due to their inability to strike the right balance between the scope of QA and the paucity of time. The extent and intent of the evaluation of the product should be determined largely based on the nature of the product, type of release and the end user.

Customizing QA

If the product is aimed at an external end user, then there is a greater need to secure the quality of the product as a whole and even a low impact issue that is say, affecting the UI/ UX can escalate and disturb the long-standing Client relationship. However, where the end user consuming the technology solution is within the same organization the rules clearly differ. The primary stakeholders will prioritize the core functionality of the product, with lesser focus on the ancillary functions. This system will work fine without major disruptions in the day-to-day operations only if there is a clear understanding and agreement by both business and development on the product features that may or may not impact the business critically.

If the product is in the MVP phase, the outlook towards QA must be very different. The MVP release deadline can sometimes tempt the stakeholders to compromise on the precision, and quality of UI features. It is highly recommended that the developers and QA chalk out the core functional areas, as well as the user-oriented features that will impress the beta / prospective clients for their uniqueness, utility and ease-of-use and have them included in the QA coverage.  Few examples of such features could be adaptability to multiple devices, personalized alerts, data security etc.,

While showcasing a product to the clients or investors as part of the sales pitch, it is imperative to prevent any surprises even if they are inconsequential technical glitches. They can be more damaging when pointed by the clients or investors while product stakeholders are caught off-guard. It is highly possible that though the prospects may not turn away, their trust in the organization and its capabilities will surely take a hit. This will then have an adverse impact on the future projects or investment commitments.

Optimized QA – Key to Building Trust

It is therefore important to build multiple Test Suites customized to handle the imminent release need. A careful compiling, diligent reviewing and continuous update of the Test Scope, tailor-made to suit the project needs at distinct stages / releases / end user, would guarantee that quality assurance does not have to be compromised for timeliness. Taking care of the little things build great trust that can nurture and build stronger client relationships.

By
Shiny Varied Ajimon – Founder