Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the It Oversight topic
No spam. Unsubscribe anytime.
Audit findings spur bill to tighten reporting on Maryland IT megaprojects
Summary
Lawmakers pressed for clearer, standardized reporting and stronger oversight of the Department of Information Technology (DoIT) after the legislative auditor described repeated problems in large IT projects and the committee heard a bill to expand project reporting requirements.
Delegate Jared Kaiser and other lawmakers told the Health and Government Operations Committee they want more transparent, readable reporting on major information technology development projects administered through the Maryland Department of Information Technology (DoIT).
The bill (House Bill 7-38) would revise reporting requirements so project status, cost-to-date, estimated cost to complete, schedule and scope changes — particularly for Major Information Technology Development Projects (MITDPs) — are presented clearly and uniformly to the General Assembly and the public.
Nut graf: The Office of Legislative Audits told the committee its February audit found repeated and significant weaknesses in oversight and reporting of MITDPs, including inaccurate annual figures, incomplete documentation of approvals, and insufficient monitoring of scope changes and project managers. Lawmakers and stakeholders argued the bill would make project data readable to non-technical audiences and provide earlier warning when projects go off track.
What the audit found The Office of Legislative Audits summarized its report: it found 16 audit findings, seven of which related to MITDPs. The auditors described DoIT’s performance as “unsatisfactory” because of repeat findings and significant weaknesses. Key concerns included DoIT not documenting oversight steps, failing to evaluate project requests for sufficiency, and not always supporting the cost-to-date and estimated cost-to-complete figures in its public annual reports.
Numbers cited Witnesses said DoIT oversees dozens of major IT projects: testimony cited 53 MITDPs with a combined nominal value approaching $3,000,000,000. The auditor told the committee that DoIT’s annual report sometimes lacked documentation to support estimates and anticipated changes to project scope and schedules.
Stakeholders and proposed changes Representative testimony said the current DoIT report is jargon-filled and not helpful to non-technical legislators. The bill’s sponsor and the Legislative Auditor asked for standardized, plain-language metrics (cost, scope, schedule, expected outcomes and key risks), clearer oversight of project managers and contracts, and better documentation of independent verification and validation work. The Maryland Hospital Association and other stakeholders said they support the bill’s intent but pressed for tweaks to timing and report elements so hospitals and vendors are not overwhelmed by duplicative submissions.
Next steps Committee members agreed to pursue amendments that aim to narrow reporting elements to high-value, actionable items and to work with DoIT and stakeholders on implementation timing. The bill hearing closed with the sponsor urging a favorable report and a schedule of follow-up meetings with DoIT and stakeholders.
Ending: Lawmakers signaled broad bipartisan concern about project overruns and agreed to seek technical fixes that would make state IT project reporting more transparent, timely and useful to policymakers.
