Quality Assurance (QA) is a critical part of every web project and initiative. It establishes that code fulfills business expectations through scope, as well as functions, performs and displays in accordance with the objectives set as the metrics for success.
QA is done in house through a coordinated effort between developers, project managers, and QA specialists. However, within the QA phase, there is also a round of quality control measures between the project team and the project implementation team. This process is known as User Acceptance Testing (UAT) and Consolidated Feedback is a key component of that process. We use UAT to gather client Consolidated Feedback to close the approval gap as well as an overall project cost savings measure.
Consolidated feedback is a QA measurement ensuring cycles of UAT feedback are concise. Being concise is important because it saves time, effort, and ultimately money during the build of the project by delineating quality control cycles. During UAT, the project team reviews the project and provides feedback to the project implementation team.
Consolidated Feedback assumes that all critical stakeholders on the project team have had a chance to thoroughly review the project, and provide their individual feedback. This feedback is then moderated typically by the team’s project manager or primary contact, synthesized into a single document, and provided to the project implementation team. This document, which essentially serves as the scope of work for feedback, is known as Consolidated Feedback.
User Acceptance Testing (UAT), if done incorrectly, can lead to very large overruns in the QA budget. Using Consolidated Feedback as the vehicle for communicating feedback is the most cost effective way to manage UAT. Sending in feedback items using a Trickle approach to the project implementation team is much less cost effective. And here is why…
Conducting UAT using Consolidated Feedback enables both teams to clarify and agree upon established metrics for success. Looking at a Consolidated Feedback document, the project stakeholders can feel confident in their comprehensive review of the project while the project implementation team satisfies their client’s needs. If either or both teams feel an extra round of UAT is needed, a change order can always be created to capture the additional level of effort needed, creating a ‘contract’ for change which both teams can work from.