How is the Requirements Management and Communication knowledge area of the BABOK v2.0 defined?

The Requirements Management and Communication knowledge area describes what is involved in managing and articulating requirements to a wide variety of stakeholders. 

Requirement elicitation and understanding business objectives are an evolving if not iterative process. Requirements management includes understanding the link between business or project objectives and the specific requirements that comes from them such that any change or clarification in the objectives will result in a revised set of requirements that reflect the business need.  Furthermore, requirements management is intended to ensure that the knowledge gained about a business, business process, or system during the analysis phase is available in a useful form for future use.

Requirements communication takes into account that stakeholders vary significantly in their roles and backgrounds.  Due to this fact, which requirements are of importance to each stakeholder group and the appropriate format and method in which to present these requirements will vary as well.  The Requirements communication part of this knowledge area takes this into consideration and ensures that all of the stakeholders develop a common understanding of the requirements and solution being presented with the ultimate goal of reaching a formal agreement on the requirements that the solution will meet.  Determining the appropriate level and format of requirements communication is critical to the success of the project.

The tasks involved in the Requirements Management and Communication knowledge area include:

  1. Manage Solution Scope and Requirements
  2. Manage Requirements Traceability
  3. Maintain Requirements for Re-use
  4. Prepare Requirements Package
  5. Communicate Requirements

posted @ Saturday, March 6, 2010 4:38 PM by Chris Adams