top of page

Approve Requirements

Purpose:

  • Agree on requirements and designs.

Description:

  • Analysts communicate with stakeholders.

  • Approvals can be formal/informal.

  • Predictive: end of phase/change meetings.

  • Adaptive: approval for solution construction.

  • Analysts gain consensus, manage approval.

Inputs

  • Requirements (Verified):

    • High-quality, verified requirements.

  • Designs:

    • Ready-to-use designs.

Elements

  • Understanding Stakeholder Roles

    • Defining approval processes and stakeholder roles.

  • Conflict and Issue Management

    • Seeking consensus and resolving conflicts.

  • Gaining Consensus

    • Ensuring stakeholder approval and understanding.

  • Tracking and Communicating Approval

    • Recording and communicating approval status

Guidelines and Tools

  • Change Strategy: Manages stakeholder consensus.

  • Governance Approach: Identifies approval stakeholders.

  • Legal/Regulatory Info: Describes rules impacting requirements.

  • Requirement Tools/Repository: Records approvals.

  • Solution Scope: Assesses alignment.

Techniques

  • Acceptance Criteria: Define approval standards.

  • Decision Analysis: Resolve issues.

  • Item Tracking: Monitor agreement issues.

  • Reviews: Evaluate requirements.

  • Workshops: Facilitate approval.

1. Stakeholders

  • Customer: Approves requirements.

  • Experts: Approve based on expertise.

  • End Users: Validate and prioritize.

  • Support: Ensures standards.

  • Manager: Manages risks and approvals.

  • Regulator: Provides regulatory opinions.

  • Sponsor: Approves business case, scope, requirements, and designs.

  • Tester: Ensures quality standards.

2. Outputs

  • Requirements: Stakeholder-approved.

  • Designs: Stakeholder-approved for development.

bottom of page