(1) Peter Orszag is directing all executive departments and agencies are to stop issuing new task orders or procurements for all financial system modernization projects – an area of persistent problems – pending review and approval by OMB of new, more streamlined project plans. Financial system modernizations projects in the federal government have become too large and complex. By setting the scope of projects too broadly rather than focusing on essential business needs, federal agencies are incurring substantial cost overruns and lengthy delays in planned deployments. Compounding this problem, projects persistently fall short of planned results once deployed. […] Across the government, there are approximately 30 financial systems projects that are affected by this policy. The total cost expended on these projects is anticipated to be $20 billion over the life of these projects, with an approximate annual spend of $3 billion. OMB expects this new process to result in a significant reduction in these amounts.
This is certainly interesting. While freezing spending for one year does not mean to cancel projects, it is a clear wake up call for major IT deployments and their vendors (see a few references to impacted vendor on this Bloomberg article)
(2) the Federal CIO will undertake detailed reviews of the highest-risk IT projects across the Federal Government. Agencies will be required to present improvement plans to the CIO for projects that are behind schedule or over budget. Where serious problems are identified and cannot be corrected, further actions should be taken, including potential adjustments to Fiscal Year 2012 agency budgets. Within 30 days, the CIO shall issue guidance on how this review process will be conducted.
These amount to about $10 billion worth of projects that were reviewed earlier this year and showed high risk levels.
(3) OMB’s Deputy Director for Management Jeff Zients will develop recommendations, within 120 days, for improving the federal government’s overall IT procurement and management practices. These recommendations will address the root-causes of problems plaguing federal IT projects and focus on proven best practices from inside and outside the federal government. They will include higher standards for project management practices and personnel, additional mechanisms for holding managers accountable for project results, and more rigorous review processes
The purpose of this third initiative is to ensure that practices for procurement, contract and project management improve. The OMB will review experiences from other tiers of governments and other countries to learn what works and what doesn’t.
The OMB is getting serious on scrutinizing IT. The Federal CIO Vivek Kundra started with making IT spending transparent through the IT Dashboard, continued with in-depth project reviews called TechStat Accountability Sessions, and now has the power to pull the plus – or seriously restructure – major projects.
With President Obama having asked agencies to reduce their budgets by five percent in 2012, Vivek Kundra and OMB may be fighting the ultimate battle to salvage IT from this or even further cuts. If all people see about IT are budget and schedule overruns, not only IT will be axed by five percent if not more, but the IT-savvy Obama administration will reach mid term with insufficient credibility.
The time left is not much, but measures are bold. We shall see how many projects will be canceled, delayed or just mildly restructures. If in the next few months the administration will prove to be serious about making IT work and link IT to agency and whole-of-government priorities, odds are that they could buy enough credibility to scale up other high-profile initiative such as whole-of-government cloud computing.
The next few months will also accelerate the tension between incumbent IT contractors and the new kids on the blocks that are (almost) pure cloud players.
By all means, it is going to be interesting to watch.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.