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.

And it is rarely that the IT organization cannot not improve its business process for requirements practices.

When it comes to getting the business requirements right, companies struggle with two issues:

  1. Business requirements analysis and definition;
  2. Requirements management tooling.

But the market places a disproportionate emphasis on tools for requirements management.

The real opportunity for improvement lies in requirements definition and in how different development methodologies treat changing business requirements.

Area With Largest Improvement!

Requirements Definition offers the most room for improvement:

Business Responsibilities

To perform a successful application of business requirements management business responsibilities are:

  • Develop business requirements that do not presuppose design or implementation details.
  • Prioritize business requirements based on relative need and available resources.
  • Provide sign offs only after carefully evaluating all materials and ensuring thorough comprehension.
  • Communicate changing business needs and collaborate with the development team to determine the impact of these changes.

IT Responsibilities

The IT responsibilities are:

  • Understand business goals and business context.
  • Identify and employ appropriate techniques to define functional and nonfunctional business requirements.
  • Communicate about progress toward fulfillment of business requirements.
  • Manage relationships between business requirements and other life-cycle artifacts to ensure fulfillment of business requirements.

The Change Process

Business requirements change processes must be tightly tied to development methodology:

How Tools Can Help!

Requirements management tools increase the efficiency of mature requirements processes:

  • Avoid business requirements management tools that are too complex.
  • Make end user comfort the No. 1 selection criterion.
  • Adopt business requirements management tools with an eye toward life-cycle integration.

Generally speaking our recommended business requirements management and analysis approach is much more successful.

back to top