5. Approve Requirement Flashcards
Purpose
To obtain agreement on and approval of r&d for ba work to continue and solution construction to proceed
Description
Approval r&d may be formal or informal
Predictive typical perform approvals at the end of the phase or during planned change control meetings
Adaptive typical approval reqs only when construction and implementation of a solution meeting reqs can begin
Inputs
Reqs (verified)
Designs
Elements 1
- Understand sh roles
BA responsible for obtain sh approval and require to understand:
- who hold decision making responsibility
- who process authority for sign off across the initiative
- any influential sh who should be consults and informed about the reqs
Elements 2
- Conflict and issue mng
Sh groups frequently have vary point of view and conflicting priorities
Elements 3
- Gain consensus
Approval may confirm that sh believe that sufficient value will be created for the org to justify investment in a solution
Complete agreement may not be necessary for a successful change
But if there is lack of agreement, associated risk are identify and managed
Elements 4
- Track and communicate approval
BA record approval decision, possibly in reqs maintenance and tracking tools.
An audit history of change to reqs:
What was change
Who made the change
The reason for the change
When it was made
Guidelines and tools
Change strategy
Governance approach
Legal/ regulatory infor
Reqs mng tools/ repository: record reqs approvals
Solution scope
Techniques
Acceptance and evaluation criteria: define approval criteria
Decision analysis: resolve issue and gain agreement
Item tracking
Reviews
Workshops
Stakeholder
Customer: review and approve r&d ensure need are meet
End user
Domain sme: review and approve
Project manager: review and approve
Operational support: review and approve
Regulator
Sponsor: review and approve biz case, solution, product scope, all r&d
Tester: responsible for ensuring quality assurance standard are feasible with in ba infor
Outputs
Reqs + Designs (approved)
