Ensuring unanimous agreement and accurate documentation of project changes among stakeholders, maintaining connections between components to track requirement modifications, preserving requirements for future use, compiling a comprehensive requirements package, and effectively communicating requirements and changes to all involved parties are essential tasks in this context.

This unit standard will enable learners to manage conflicts and changes to requirements and ensure that all stakeholders and the project team remain in agreement on the solution scope. A learner credited with this unit standard will be able to ensure that changes to project work products are agreed upon by all stakeholders and documented accurately, maintain relationships between components to trace requirement changes and update relevant documentation, maintain requirements for re-use, prepare a requirements package, communicate requirements and changes to all stakeholders.

Course Content

  • Formal and informal changes to requirements are approved and documented to ensure that all stakeholder needs are met
  • Conflicts and issues with requirements are highlighted and resolved to ensure that consensus is reached between all stakeholders regarding the
    most appropriate solution
  • Changes to requirements are prioritised to allow the selection, design, and development of the most appropriate solution
  • Multiple versions of requirements work products are maintained to ensure that changes can be traced by change control procedures
  • The relationships between the various requirements components are maintained to ensure consistency
  • An impact analysis is performed when changes are requested to ensure the plan can be updated
  • Impact analysis information is produced to ensure that agreed-upon changes are included in the process
  • Support activities ensure that the solution assessment and validation include the changed requirements.
  • The requirements to be maintained are selected after solution implementation
  • Name the responsible party who will maintain the requirements (i.e., custodian, librarian)
  • The responsible party is identified too
  • Facilitate ongoing use of requirements for impact analysis and solution maintenance
  • Facilitate re-use of requirements on related projects to encourage enterprise consistency of business models
  • Use the agreed requirements and business communication plan to determine the requirements package
  • Determine appropriate format for requirements
  • Create a requirement package
  • The requirements package and business communication plan are used to communicate with all stakeholders appropriately
  • Interaction with stakeholders takes place before, during, and after the project to ensure that they are informed and participate in decision-making
  • Each activity in the business analysis process involves communication on different levels
  • Interaction with the solution team to assure that requirements are correctly understood and implemented
  • All requirements are communicated and understood by all parties involved in the project
  • Non-accredited: Short course only  
  • Duration: 1h 30m
  • Delivery: Classroom/Online/Blended
  • Access Period: 12 Months 
Print Button
Scroll to Top