You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Full titleIdentify, analyse and manage requirements
ObjectiveExtract and manage requirements based on the informal needs expressed by stakeholders
ApplicabilityThis practice is essential in early phases of the project, when core requirements are identified and defined. Later, it is an important practice when new features are requested.
Context

The practice applies to all projects. If the needs of stakeholders have not been identified previously, then this practice becomes the core part of requirements elicitation strategy.

Addressed elements in SMM
Actions
  1. Formulate requirements based on the needs expressed by the stakeholders
    1. Each requirement reflects a single feature or constraint of the system
    2. Identify dependencies among the needs expressed by different stakeholders and reconcile them before defining requirements.
    3. Identify dependencies between the identified requirements
    4. Define testable verification criteria for each requirement
    5. Define and manage priorities for the requirements (in collaboration with stekeholders)
  2. Maintain and manage traceability links between requirements and the needs
  3. Use tools to support the management of requirements
    1. Give priority to the tools available and supported within the organization (Jira, wiki)
    2. If possible, use versioning and dependency-tracking capabilities of the tool
  4. Validate the requirements with stakeholders
    1. Obtain explicit approval from the key stakeholders, and at least implicit approval from remaining ones

  5. Consult the IPR issues with the IPR Coordinator

    1. verify which open source licence will be the most adequate for your code

    2. register any pre-existing IP if it will be used in the code

Risks
  1. Requirements are not verifiable
    1. Requirements cannot be translated into test conditions/test cases
    2. Progress of the project cannot be appropriately tracked
    3. Feature regression is likely to happen.
  2. Requirements cannot be traced back to the needs of stakeholders
    1. Stakeholders may loose orientation in the project's priorities and key directions
    2. Some requirements may become orphaned and not backed by the stakeholders
    3. Some needs may not be addressed appropriately by the requirements
Related practices
  • No labels