Reports & Testimonies

  • GAO’s recommendations database contains report recommendations that still need to be addressed.

    GAO’s recommendations help congressional and agency leaders prepare for appropriations and oversight activities, as well as help improve government operations. Recommendations remain open until they are designated as Closed-implemented or Closed-not implemented. You can explore open recommendations by searching or browsing.

    GAO's priority recommendations are those that we believe warrant priority attention. We sent letters to the heads of key departments and agencies, urging them to continue focusing on these issues. These recommendations are labeled as such. You can find priority recommendations by searching or browsing our open recommendations below, or through our mobile app.

  • Browse Open Recommendations

    Explore priority recommendations by subject terms or browse by federal agency

    Search Open Recommendations

    Search for a specific priority recommendation by word or phrase



  • Governing on the go?

    Our Priorities for Policy Makers app makes it easier for leaders to search our recommendations on the go.

    See the November 10th Press Release


  • Have a Question about a Recommendation?

    • For questions about a specific recommendation, contact the person or office listed with the recommendation.
    • For general information about recommendations, contact GAO's Audit Policy and Quality Assurance office at (202) 512-6100 or apqa@gao.gov.
  • « Back to Results List Sort by   

    Results:

    Subject Term: "Earned value management systems"

    5 publications with a total of 9 open recommendations including 2 priority recommendations
    Director: David A. Powner
    Phone: (202) 512-9286

    3 open recommendations
    Recommendation: To help IRS improve its process for determining IT funding priorities and to provide timely information on the progress of its investments, the Commissioner of IRS should direct the Chief Technology Officer to establish, document, and implement policies and procedures for selecting new and reselecting ongoing business systems modernization activities, consistent with IRS's process for prioritizing operations support priorities, which addresses (1) prioritization and comparison of IT assets against each other, (2) criteria for making selection and prioritization decisions, and (3) ensuring IRS executives' final funding decisions on IT proposals are based on IRS's prioritization process.

    Agency: Department of the Treasury: Internal Revenue Service
    Status: Open

    Comments: In April 2017, IRS stated that it had several process improvements underway that would impact its documentation of policies and procedures for prioritizing business systems modernization activities. The agency committed to addressing the recommendation by December 2017.
    Recommendation: To help IRS improve its process for determining IT funding priorities and to provide timely information on the progress of its investments, the Commissioner of IRS should direct the Chief Technology Officer to modify existing processes for Foreign Account Tax Compliance Act (FATCA) and Return Review Program (RRP) for measuring work performed by IRS staff to incorporate best practices, including accounting for actual work performed and using the level of effort measure sparingly.

    Agency: Department of the Treasury: Internal Revenue Service
    Status: Open

    Comments: In April 2017, IRS reported that it was continuing to examine methods for modifying existing processes to measure work performed by IRS staff for the Foreign Account Tax Compliance Act and Return Review programs. We are monitoring IRS's efforts as part of an ongoing review of the agency's information technology operations.
    Recommendation: To help IRS improve its process for determining IT funding priorities and to provide timely information on the progress of its investments, the Commissioner of IRS should direct the Chief Technology Officer to report on actual costs and scope delivery at least quarterly for the Customer Account Data Engine 2 and the Affordable Care Act Administration. For these investments, IRS should develop metrics similar to FATCA and RRP.

    Agency: Department of the Treasury: Internal Revenue Service
    Status: Open

    Comments: IRS began reporting on actual costs and scope delivery at least quarterly using metrics similar to FATCA and RRP and provided the quarterly reports for fiscal year 2016 and the first two quarters of fiscal year 2017 to GAO. As of September 2017, the agency had not implemented the recommendation for the Affordable Care Act Administration investment because it did not see the benefit in doing so given that development work was minimal. We are following up with IRS on this as part of an ongoing review of the agency's information technology operations.
    Director: Cristina Chaplain
    Phone: (202) 512-4841

    3 open recommendations
    including 1 priority recommendation
    Recommendation: To ensure that the SLS cost and schedule estimates better conform with best practices and are useful to support management decisions, the NASA Administrator should direct SLS officials to update the SLS cost and schedule estimates, at least annually, to reflect actual costs and schedule and record any reasons for variances before preparing their budget requests for the ensuing fiscal year. To the extent practicable, these updates should also incorporate additional best practices including thoroughly documenting how data were adjusted for use in the update and cross-checking results to ensure they are credible.

    Agency: National Aeronautics and Space Administration
    Status: Open
    Priority recommendation

    Comments: NASA agreed with this recommendation and reported taking steps to address it through its annual assessment of the SLS's current cost and schedule estimates against its Agency Baseline Commitment. The agency provided the results of this assessment but did not address the deficiencies we identified in NASA's original estimate, including thoroughly documenting how data were adjusted for the update and cross-checking the results to ensure credibility. In order to close this recommendation, NASA's estimate of its current costs would ideally include documentation of how data were adjusted for use in the updated estimate as well as an explanation of any estimating methodology crosschecks. At a minimum, the estimate documentation should include an explanation of variances between the original estimate and the current estimate.
    Recommendation: To provide more comprehensive information on program performance, the NASA administrator should direct the SLS program to expedite implementation of the program-level EVM system.

    Agency: National Aeronautics and Space Administration
    Status: Open

    Comments: The SLS program concurred with our recommendation and has taken steps to implement a program-level earned value management (EVM) system. In May 2016, NASA and Boeing finalized its contract with Boeing for the SLS core stage, the largest development effort in the program. According to NASA officials, the SLS program began receiving contractor earned value management data derived from the new core stage performance measurement baseline in fall 2016. At that time the program implemented a program-level EVM system tracking both in-house and contractor effort.
    Recommendation: To ensure that decisionmakers are able to track progress toward the agency's committed launch readiness date, the NASA administrator should direct the SLS program to include as part of the program's quarterly reports to NASA headquarters a reporting mechanism that tracks and reports program progress relative to the agency's external committed cost and schedule baselines.

    Agency: National Aeronautics and Space Administration
    Status: Open

    Comments: The SLS program concurred with our recommendation. According to NASA officials, the program has taken steps to track and report progress relative to the agency's external committed cost and schedule baselines within the program's quarterly reports to NASA headquarters. The program, however, has not yet provided documentation of these actions to GAO.
    Director: Dave Powner
    Phone: (202) 512-9286

    1 open recommendations
    Recommendation: To address risks in the GOES-R program development and to help ensure that the satellite is launched on time, the Secretary of Commerce should direct the NOAA Administrator to address shortfalls in defect management identified in this report, including the lack of clear guidance on defect definitions, what defect metrics should be collected and reported, and how to establish a defect's priority or severity.

    Agency: Department of Commerce
    Status: Open

    Comments: NOAA agreed with this recommendation. The agency subsequently reported that contractors are required to report defects and that the agency can place a hold or put liens against contractors if defects are not addressed. NOAA also provided documentation to support its recurring meetings at which defects are addressed. Additionally, NOAA provided documentation on its defect reporting requirements and definitions. However, NOAA did not provide documentation showing what defect metrics should be collected and reported, and how to establish a defect's priority or severity. We will continue to monitor the agency's actions on this recommendation.
    Director: Carol R. Cha
    Phone: (202) 512-4456

    1 open recommendations
    Recommendation: To better ensure that the Defense Agencies Initiative (DAI) implements effective risk management and information technology (IT) acquisition best practices, the Secretary of Defense should direct the Director of the Defense Logistics Agency to direct the DAI program office to establish a comprehensive risk log that includes all up-to-date risks with evaluations and categorizations that comply with DLA's defined parameters; and associated mitigation plans.

    Agency: Department of Defense
    Status: Open

    Comments: The Defense Logistics Agency established a risk log for DAI that includes risk evaluations and categorizations, and associated mitigation plans. We will continue monitoring the program's implementation of this recommendation to ensure that the agency is periodically reviewing the status of each risk and updating DAI's risk log and mitigation plans, as intended by the recommendation.
    Director: Chaplain, Cristina T
    Phone: (202)512-4859

    1 open recommendations
    including 1 priority recommendation
    Recommendation: To improve NASA management and oversight of its spaceflight projects, and to improve the reliability of project EVM data, the NASA Administrator should direct the appropriate offices to modify the NASA Procedural Requirements (NPR) 7120.5 to require projects to implement a formal surveillance program that: (1) Ensures anomalies in contractor-delivered and in-house monthly earned value management reports are identified and explained, and report periodically to the center and mission directorate's leadership on relevant trends in the number of unexplained anomalies. (2) Ensures consistent use of work breakdown structures (WBS) for both the EVM report and the schedule. (3) Ensures that lower level EVM data reconcile to project level EVM data using the same WBS structure. (4) Improves underlying schedules so that they are properly sequenced using predecessor and successor dependencies and are free of constraints to the extent practicable so that the EVM baseline is reliable.

    Agency: National Aeronautics and Space Administration
    Status: Open
    Priority recommendation

    Comments: NASA partially agreed with this recommendation. NASA has implemented several initiatives related to EVM training tools and support material to enhance EVM implementation, but has not modified the NASA Procedural Requirements (NPR) 7120.5 to require projects to implement a formal surveillance program. In May 2017, officials reiterated NASA's position that they do not plan to implement a formal surveillance plan due to resource constraints. We continue to believe that implementing this recommendation for projects to implement a formal surveillance program would be beneficial and prevent anomalies in EVM data from occurring. Without implementing proper surveillance, projects may be utilizing unreliable EVM data in its analyses to inform its cost and schedule decision making.