Requirements management consists of the identification, definition and agreement of the project to meet the needs and expectations of interested parties, especially those of the customers and users.

Project requirements are derived from customer needs, which are driven by opportunities and threats. A business case and a project strategy are developed. A strategy is a high level view of how
to attain the vision/targets of the organisation at some point in the future. The strategy is reviewed at various time intervals (e.g. in a systems life-cycle, during the project life-cycle and in each of its phases), as well as in specific areas, for example in procurement.

Possible process steps:

  1. Gather, document, and get agreement on project requirements.
  2. Develop a business case and project strategies and place them under change management.
  3. Define project objectives, appraise the project, carry out a feasibility study, and establish a project plan.
  4. Communicate progress and changes.
  5. Validate requirements at key points in the project life-cycle.
  6. Assess compliance with project objectives and requirements and seek authorisation for the project.
  7. Set up project review process.
  8. Document the lessons learnt and apply to future projects.

Key competence at level:

  • A Has successfully directed the management of project requirements and objectives for important programmes and/or portfolios of an organisation or an organisational unit.
  • B Has successfully managed defining the project requirements and objectives of a complex project.
    C Has successfully managed defining the project requirements and objectives of a project with limited complexity.
  • D Has the knowledge required concerning the management of project requirements and objectives and can apply it.
Dieser Beitrag wurde unter Allgemein veröffentlicht. Setze ein Lesezeichen auf den Permalink.

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.