3. Validate Reqs

Question 1

Purpose

Answer 1

To ensure that all r&d align to the biz reqs and support the delivery of needed value

Question 2

Desciption

Answer 2

Ongoing process to ensure that sh, solution, transition align to the biz reqs and that design satisfy the reqs

May be expose different, conflicting needs and expectations through the validation process

Question 3

Inputs

Answer 3

Reqs(specified and modeled)
Validation activities may be begin before reqs are verified but cannot be completed before reqs are completed verified

Question 4

Elements 1

Answer 4

1. Identify assumptions
   If an org launching an unprecedented or service, it may be necessary make assumption about cust or sh response.
   Assumption are identified and defined that associated risk can be managed

Question 5

Elements 2

Answer 5

2. Define measurable evaluation criteria
   Used to evaluate how successful the change has been after solution implemented

Question 6

Elements 3

Answer 6

3. Evaluate alignment with scope solution
   - when reqs not align, future state must be re evaluated and solution scope change, or reqs removed from scope solution
   - if design can not validated to support a reqs, might be w a missing or misunderstand reqs, or the design must change

Question 7

Guidelines and tools

Answer 7

Biz objective: ensure reqs deliver the desired biz benefit

Future state description

Potential value

Solution scope

Question 8

Techniques

Answer 8

Acceptance and evaluation criteria
Document analysis
Financial analysis
Item tracking
Metrics and KPI
Reviews
Risk analysis and mng

Question 9

Stakeholder

Answer 9

All sh.
BA conjunction with the cust, end user, sponsor has primary for determine whether or not reqs are validate

Question 10

Outputs

Answer 10

Reqs (validated)
Can be demonstrated r&d deliver benefit to sh align with the biz goals and objective of the change
If r&d can not validated -» not benefit to org, not fall with solution