Control Your IT Demand!

requirements planning

Benefits of Business Requirements Management

Analysts report that poor business requirements management accounts for as much as 71 percent of software project failures. The main cause is the gap between:

  • What the business team wants
  • How the business team communicates this
  • What IT understands and delivers

Roles in Business Requirements Analysis Projects

Each task to be undertaken needs qualified personnel. A business requirements project is in this sense not different from others. Important roles are:

  • The decision maker;
  • The project manager;
  • The business analyst or the domain expert (one per important domain);
  • The architect;
  • The QA (Quality Assurance) lead;
  • The workshop facilitator;
  • The scribe;
  • The designer;
  • The tester;
  • The application manager.

Want to find out more? These topics can help:

Structured Requirements Guidelines

The following general guidelines can help you become successful with your requirements planning projects:

  • Aim for approximately 30 externally facing requirements per project for manageability. Treat large projects as several smaller ones.
  • Each requirement should have a maximum of 10 or so scenarios for manageability. Break it out into sub-requirements if necessary.
  • Each scenario should have at most 10 to 20 discrete steps.
  • Estimate 2 to 4 man-weeks of pure development time per scenario in a normal external-facing requirement.
  • Assume a 1:1 ratio of development time to test time.

Implementation Services For Business Requirements Management: Consultancy and training

We help you deliver results by successful implementation based on extensive experience gained through many projects. We prefer fixed price fixed date programs, as they offer you and us the utmost value.

Prerequisites For a Successful Application Of Business Requirements Management

The quality of business software requirements is a limiting factor on the success of software development projects.

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.

Recommended Requirements Management Tools

There exist several tools, specifically designed for business requirements management. Important requirements for business requirements management tools are:

  • Easy to use for business users;
  • Structured approach;
  • Documentation generation;
  • Life cycle integration;
  • Process compliance.

Recommended Skills and Experience

We will now give a short overview of the recommended skills and experience in order to be able to successfully complete a business requirements management project.

Checklist Of Business Requirements Management and Analysis Do's and Don'ts

This checklist addresses process and content specific issues of business requirements management and analysis. A checklist must always be specific for an organization, and this list gives you a head-start.

Recommended Business Requirements Management and Analysis Methodology

Our recommended business requirements management and analysis methodology consists of several steps. These guidelines help you extensively to execute successful requirements planning projects. Make sure that you:

  • Select a small group of people with relevant competences to make decisions regarding the business requirements.
  • Organize workshops lead by a skilled facilitator and let a skilled scribe make notes.
  • Discuss the business requirements:
    • In a small number of sessions;
    • From all involved viewpoints;
    • End-to-end;
    • Consider the ROI of the project investment.