Verify Requirements
The "Verify Requirements" process emphasizes checking that the quality of requirements aligns with the defined standards of the organization. Meeting these standards aids in efficient communication of the requirements to all stakeholders and ensures that the final product meets the desired quality.
Key Definitions
Verification: This is the act of reviewing the requirements and other product-related information to identify errors, contradictions, and conformity with quality standards. It assesses if the said requirements and product information adhere to a particular regulation, specification, or any imposed condition.
Validation: While verification deals with the adherence of requirements to defined standards, validation is concerned with confirming that a product caters to the needs and desires of the customer and other pinpointed stakeholders.
Notable Points about Verification
Iterative Process: Verification can be carried out in multiple iterations and doesn't necessarily follow a linear path.
Formality Levels: Depending on the techniques applied, verification can be formal or informal.
Scope: Both requirements and related analysis models undergo verification and validation processes. This procedure can be executed on product information, whether at the portfolio, program, or project dimensions. The process might focus on a single requirement, an individual model, or a comprehensive set of product information.
Aim: The main goal of verification is to confirm that requirements and other product data are appropriately structured. It ensures models are lucid enough to be efficiently utilized. When it comes to non-functional requirements or acceptance criteria, verification assesses if these components can be effectively measured. Ultimately, verified requirements are more comprehensible, increasing the chances of successful implementation by the project team.
Author Verification: While the author of the materials can carry out some preliminary verification, it's vital to have an external verification for unbiased scrutiny. This could be conducted by another business analyst not involved in the current project or other project team members.
Review Against Standards: The person responsible for verification contrasts the requirements and other product-related information against any established analysis, compliance, or regulatory standards. This is done to confirm accuracy and alignment with the relevant standards.
Outcome of Verification: Should the product information fail to meet the verification criteria, it necessitates further detailing or rephrasing. This is done to certify that it achieves a satisfactory quality level to progress in its life cycle. One way to evaluate this quality, especially when standards are absent or in conjunction with them, involves the 3Cs evaluation: ensuring the information is correct, complete, and consistent. Moreover, analysis models can be contrasted against established syntax or modeling standards for verification.
By diligently following the "Verify Requirements" process, organizations can ensure that their requirements are clear, comprehensive, and in alignment with organizational standards, leading to successful project outcomes.
Inputs
Product Scope
Product scope refers to the features and functions that are to be included in a product or service. It serves as a boundary that defines what is and is not included in the scope of the business analysis efforts.
Situation Statement
The situation statement provides a narrative description of the context within which the business analysis is being conducted. It outlines the current state, including any problems or opportunities, and acts as a starting point for elicitation.
Stakeholder Engagement and Communication Approach
This input encompasses the strategies and plans for engaging stakeholders and managing communications throughout the business analysis process. It is crucial for ensuring that relevant information is elicited from the right stakeholders in an appropriate manner.
Stakeholder Register
A stakeholder register is a document that lists all the stakeholders associated with the project or initiative. It typically includes information such as stakeholder interests, level of influence, and communication requirements.
Tools and Techniques
Brainstorming
Brainstorming is a technique used to generate a wide range of ideas and solutions. It involves gathering a group of stakeholders and encouraging them to share their thoughts and suggestions without criticism.
Interviews
Interviews are one-on-one or small group discussions aimed at eliciting detailed information from stakeholders. They are structured conversations where the interviewer asks specific questions related to the business analysis.
Retrospectives and Lessons Learned
Retrospectives and lessons learned are techniques used to reflect on past projects or phases of a project. They involve reviewing what went well, what didn't, and what could be improved, providing valuable insights for future elicitation efforts.
Outputs
Elicitation Approach
The elicitation approach outlines the methods and techniques that will be used to gather requirements and other necessary information. It is a plan that guides the elicitation process, ensuring that it is conducted efficiently and effectively.