Verification and change

Verification findings capture a problem observed while checking delivery on a project. A finding has a project, title, severity, status, reporter note, raised-by person and owner. Change impacts record a different kind of concern: what a proposed or discovered change could do to the project’s schedule, cost, resources, technical work, quality, compliance or vendors. Both records give the Project Manager a place to see unresolved delivery concerns beside the requirement work.

• Findings. QA Engineer records the observed problem and assigns an owner for investigation and verification.
• Impacts. Project Manager records probability, impact, mitigation and owner for a change concern.
• Project view. Both records point to a project, so its wider progress and exception counts can be reviewed together.

A finding can move from open through triaged, in progress and fixed to verified and closed. Each change impact can be open, monitored, mitigated or closed. The owner should use those states to communicate actual progress. A critical open finding and a high-impact open change ask for different decisions, even when both concern the same project. The project record helps the lead see them in one operating context.

Agree when a QA Engineer records a finding, how severity is chosen, and who verifies a fix. The reporter note should describe what was observed and where, without substituting for the owner’s investigation. Decide when a verified finding is closed. For impacts, agree how probability and impact are assessed and when mitigation is considered complete. The numeric scores and calculated rating should be interpreted consistently across projects.

Plan a regular review of unresolved findings and change impacts. The Project Manager should know who can change ownership and who can accept a mitigation. If a change affects acceptance criteria, use the project to find the affected requirement and revisit its baseline revision so the recorded decision still refers to the intended scope. Attachments can hold supporting evidence against a parent requirement when the team needs a file alongside the record.

Start with an open high-severity finding on an active project. Give it an owner and a reporter note, then move it through investigation and fixed to verified after the QA Engineer checks the result. Add a related change impact with a category, probability, impact and mitigation, and confirm it appears in the project’s change review. A Delivery Lead should be able to identify the unresolved question, responsible person and next action from the records.

• Open Verification Findings — Open, triaged and in-progress findings with severity and owner.
• Active Projects — The project context and progress behind each verification concern.

Use verification and change to walk the exception review. Continue to baseline review when a change affects accepted scope.