Skip to main content

Business Systems Modernization: IRS Needs to Complete Recent Efforts to Develop Policies and Procedures to Guide Requirements Development and Management

GAO-06-310 Published: Mar 20, 2006. Publicly Released: Apr 19, 2006.
Jump To:
Skip to Highlights

Highlights

The Internal Revenue Service's (IRS) effort to modernize its tax administrative and financial systems--Business Systems Modernization (BSM)--has suffered delays and cost overruns due to a number of factors, including inadequate development and management of requirements. Recognizing these deficiencies, IRS created a Requirements Management Office (RMO) to establish policies and procedures for managing requirements. GAO's objectives were to assess (1) whether the office has established adequate requirements development and management policies and procedures and (2) whether BSM has effectively used requirements development and management practices for key systems development efforts.

Recommendations

Recommendations for Executive Action

Agency Affected Recommendation Status
Internal Revenue Service To improve the requirements development and management policies and practices of the IRS's BSM, the Commissioner of Internal Revenue should direct the Associate Chief Information Officer for BSM to ensure that BSM completes the delivery of policies and procedures for requirements development and management as planned. The policies and procedures should fully describe the processes, include a minimum set of activities required for each project, and provide detailed procedures for each of the key areas of requirements elicitation, documentation, verification and validation, and management. As part of this effort, the policies and procedures should specifically include the following: (1) a standardized process for the elicitation of requirements that ensures that projects fully investigate the requirements needed for a specific system, including gathering requirements from all relevant users and stakeholders; (2) a standardized process for the documentation of requirements that ensures full documentation of the baseline requirements; (3) a process for ensuring formal peer reviews are planned and completed for key products; (4) guidance on tracking cost and schedule impacts of changes to requirements for all projects; and (5) guidance on establishing and maintaining full bidirectional requirements traceability.
Closed – Implemented
In January 2008, IRS provided us a briefing and documentation on policies, procedures, and tools for developing and managing project requirements developed by its Business Rules and Requirements Management office in response to our recommendation. Specifically, IRS developed (1) a standardized process for the elicitation of requirements; (2) a standardized process for the documentation of requirements; (3) a process for ensuring that formal peer reviews are planned and completed for key requirements; (4) guidance on tracking cost and schedule impacts of changes to requirements; and (5) guidance on establishing and maintaining full bidirectional requirements traceability. We have reviewed these documents and found that they address our recommendations. The Business Rules and Requirements Management office has also been implementing the new policies and procedures by providing support to multiple projects throughout the IRS, including the Customer Account Date Engine (CADE), Accounts Management System (AMS), and Modernized eFile systems. For example, IRS stated that the new requirements development and management policies, procedures, and tools were used for CADE Release 5 and that the requirements office is providing support and/or consultation services to three AMS releases. By developing and implementing these policies and procedures and supporting tools, IRS will now be able to more effectively develop and manage project requirements for the acquisition of critical systems.
Internal Revenue Service To improve the requirements development and management policies and practices of the IRS's BSM, and since BSM has ongoing projects that are developing and managing requirements and the development of new policies and procedures is not scheduled to be complete until March 2007, the Commissioner of Internal Revenue should direct the Associate Chief Information Officer for BSM to immediately implement its draft policies while the final policies and procedures are being developed.
Closed – Implemented
The Senate Appropriations Subcommittee on Transportation, Treasury, the Judiciary, HUD and Related Agencies requested that we assess (1) whether the Requirements Management Office (RMO) has established adequate requirements development and management policies and procedures and (2) whether BSM has used effective requirements development and management practices for key systems development efforts. GAO completed this work and recommended that IRS develop and implement new policies and procedures addressing all areas of requirements development and management, and that draft policies and procedures be implemented while the detailed policies are being developed. IRS concurred with this recommendation and agreed to implement the draft policies and procedures as interim guidance while completing development of more detailed policies and procedures for requirements development and management. These interim policies and procedures are made available for BSM projects through its Business Rules and Requirements Management online repository.

Full Report

Office of Public Affairs

Topics

Cost overrunsFinancial management systemsProgram evaluationProgram managementSchedule slippagesStrategic planningSystems managementTechnology modernization programsPolicies and proceduresBusiness systems modernization