Validate Requirement - Business Analyst

Purpose

The purpose of requirements validation is to ensure that all requirements support the delivery of value to the business, fulfill its goals and objectives, and meet a stakeholder need.

Description

Requirements validation is an ongoing process to ensure that stakeholder, solution, and transition requirements align to the business requirements.

Assessing what the outcome will be for the stakeholder when their need is satisfied can be helpful when validating requirements. Implementation of the requirements as a whole must be sufficient to achieve that desired future state for customers and users. In many cases, stakeholders will have different, conflicting needs and expectations that may be exposed through the validation process and will need to be reconciled. See Manage Solution Scope and Requirements.

Input

Business Case: The business case describes the overall business objectives and measurements that the solution is expected to deliver. To be valid, a requirement mustcontribute directly or indirectly to the business case. Other business requirements, including the business need, required capabilities, and solution scope may also be used for validation.

Stakeholder, Solution, or Transition Requirements [Verified]: Requirements need to be verified for validation to be completed. If a requirement cannot be verified, it cannot be successfully implemented and so cannot meet a business need. However, validation activities may begin before requirements are completely verified.

Elements

1. Identify Assumptions

In many cases it may not be possible to prove that implementation of the requirement will result in the desired benefit. If an organization is launching an unprecedented product or service, it may be necessary to make assumptions about customer or stakeholder response, as there are no similar previous experiences to rely on. In other cases, it may be difficult or impossible to prove that a particular problem derives from an identified root cause. Stakeholders may have assumed that certain benefits will result from the implementation of a requirement, and these assumptions must be identified and defined so that associated risks can be managed. See Define Assumptions and Constraints.

2. Define Measurable Evaluation Criteria

While the forecasted business benefits are defined in the business case, the specific measurement criteria and evaluation process may not have been included. Following the definition of the benefits that will result from the implementation of a requirement, it is necessary to define the evaluation criteria that will be used to evaluate how successful the resulting change has been after the solution is deployed (see Metrics and Key Performance Indicators for information on the selection of appropriate criteria, and Evaluate Solution Performance for details on how this assessment is performed post-implementation).

3. Determine Business Value

The business case defines the value delivered by a solution that meets the solution scope, but it is also possible to assess individual requirements or features to determine if they also deliver business value.Specify and Model Requirements outlines some ways in which a requirement can deliver business value. A requirement that does not deliver direct or indirect value to a stakeholder is a strong candidate for elimination. Value does not need to be monetary. Business value can be delivered through requirements that support compliance with regulatory or other standards, alignment with internal standards or policies of the organization, or increased satisfaction for stakeholders, even if those things do not have a direct measurable financial benefit.

4. Determine Dependencies for Benefits Realization

Not all requirements contribute directly to the end result desired by the organization and described in the business case. See Manage Requirements Traceability for the types of relationships that might exist.

5. Evaluate Alignment with Business Case and Opportunity Cost

A requirement can be of value to a stakeholder and still not be a desirable part of a solution. A requirement that is not aligned with the business case should be defined and approved in a separate business case, or considered for removal from the solution scope. Ultimately, each requirement must be traceable to the objectives in the business case, and should also minimize the opportunity cost of implementation.

At the project level, opportunity cost refers to the benefits that could have been achieved with an alternative investment rather than this one. In other words, it is the cost of what you cannot do or have because you chose to invest in this project instead of another one. This concept can also be applied to decisions made within a project. For example, if a project team spends time and energy implementing a feature in a software application, that effort cannot be applied towards additional testing, training for the users, bug fixes, or other project work. That lost work represents the opportunity cost of the decision. The opportunity cost of any decision is equal to the value of the best alternative use of those resources.

Techniques

Acceptance and Evaluation Criteria Definition: Acceptance criteria are the quality metrics that must be met to achieve acceptance by a stakeholder.

Metrics and Key Performance Indicators: Used to select appropriate performance measures for a solution, solution component, or requirement.

Prototyping: Prototyping of product components is used to gain user agreement with the proposed solution.

Risk Analysis: Risk analysis can be used to identify possible scenarios that would alter the value delivered by a requirement.

Structured Walkthrough: Review meetings are conducted to confirm whether the stakeholder agrees that their needs are met.

Stakeholders

All Stakeholders: Virtually all stakeholders are involved in or impacted by validation activities.

Outputs

Requirements [Validated]: Validated requirements are those that can be demonstrated to deliver value to stakeholders and are aligned with the business goals and objectives. If a requirement cannot be validated, it does not benefit the organization, does not fall within the solution scope, or both.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Business Analyst Topics