Commonly Used Business Requirements Planning Methodology and Approach (and how to improve it)

Currently, business managers leave the process of gathering of business requirements management specifications often to the 'experts'. We do not recommend this, because because requirements management is a serious part of business planning, and therefore should be handled by business management. Common behavior:

  • ICT experts run the project, and all is in their 'safe hands'.
  • The match between business and delivered project results is to be established during the project test phase. And thus much too late, and too expensive.

ICT personnel use several ways to gather specifications:

  • Through interviews;
  • Through gatherings.

Their first priority is usually to speak key-players separately, and to write the business requirements documents with the help of office products like Word, Excel, or PowerPoint. This makes checking, integration, and life cycle management of the specifications difficult.

Why Traditional Requirements Planning Techniques Can Fail

Traditional business requirements gathering can fail because of:

  • They usually fail to describe what the system needs to do from a user's perspective, adding to the difficulty of communicating the project scope and deliverables.
  • Traditional business requirements tend to be independent of each other.
  • It tends to be hard to translate them into a design.
  • They are hard to test.

It is therefore recommend to use a structured requirements gathering method.

back to top