There is no doubt that a considerable amount of resources of an organization is spent on requirement definition and documentation no matter where the maturity of the Business Analysis practice within the organization. The business has a considerable interest in requirements that lead to IT business solutions and it can define the direction and prosperity of the entire organization.
By maintaining requirements for re-use the Business Analyst (BA) can considerably reduce the resources spent on requirements definition and documentation. In this way the BA identifies long-termed used requirements of the organization that may be used by multiple systems, or continually come up for solutions on multiple projects. These may include requirements that the organization must meet on an ongoing basis, as well as requirements that are implemented as part of an IT business solution.
Whether these requirements are maintained in a repository or not; they must be identified, clearly defined and available to all BAs within the organization. When a requirement must be changed, the change must be communicated to the BA community and understood by the business community concerned.
Maintenance of requirements for re-use can facilitate impact analysis of new, proposed changes to the business, reduce analysis time and effort, assist in the maintenance of previously implemented IT business solutions and support other business initiatives; including training, corporate governance and standards compliance.
Cincinnati and Dayton companies; and companies across the globe need to mature their BA practice within the organization toward effective maintenance management of business requirements, including requirements for re-use. This will give these organizations the benefits stated above and continue the BA practice on the path toward a Business Analysis Center of Excellence (BACoE).
Do you have an effective requirements management process? Do you use a software requirements repository tool to accomplish this?