Blog

Friday, July 17, 2009
Evidence-based decisions
Vivek Kundra, Federal CIO

Today, the Department of Veterans Affairs (VA), under the leadership of Secretary Shinseki and VA CIO Roger Baker, announced that it will temporarily halt 45 IT projects which are either behind schedule or over budget and work to determine whether these programs should be continued. We’re not talking about a trivial sum here—the Fiscal Year 2009 combined budget for the 45 projects is approximately $200 million. The worst offender of the bunch was 110% over budget and 17 months behind schedule.

We were able to catch these contracts, in part, thanks to our new tool, the "IT Dashboard” which helped shed light on the performance of projects across the federal government.

During the next few weeks, the VA will audit these 45 projects to determine whether additional resources or new management teams can get them back on schedule. If they can’t be fixed, the projects will be canceled.

If you are just hearing about the IT Dashboard for the first time, it allows you to see which IT projects are working and on-schedule (and which are not), offer alternative approaches, and provide direct feedback to the chief information officers at federal agencies.

Given the size and complexity of the federal IT portfolio, the challenges we face are substantial and persistent. The dashboard is not a substitute for good management. Its value comes from leaders who use the information to make tough, evidence-based decisions on the future of IT investments.

The VA’s announcement is part of a broader effort by the Administration to make the federal government more transparent and to boost accountability and drive better performance. From IT accountability to personnel and contracting reforms, the administration is committed to providing better value, efficiency, and effectiveness for taxpayers’ dollars.


Monday, July 13, 2009
Welcome to IT Dashboard – The Blog!
Vivek Kundra, Federal CIO

It has been an exciting time since we launched the IT Dashboard. There have been more than 20 million hits so far, and we’ve received an encouraging response from members of Congress and the public in support of our efforts to increase transparency. One of those 20 million hits was from a prominent IT user; you see for yourself here:



For anybody just joining us, the“IT Dashboard” is a new, one-stop clearinghouse of information that allows anyone with a web browser to track federal IT initiatives and hold the government accountable for progress and results. A part of USASpending.gov, the dashboard allows you to see what IT projects are working and on-schedule (and which are not), offer alternative approaches, and provide direct feedback to the chief information officers at federal agencies – in effect, keeping tabs on the people who are responsible for taxpayer dollars for technology.

Leading up to the launch, we tapped the brightest and most innovative minds from Federal agencies, Congress, independent oversight organizations, and the private sector as we built the IT Dashboard. Over 400 federal employees joined our daily open house sessions for a hands-on opportunity to try the Dashboard, check their data, and suggest improvements. Until July 31, CIOs can submit investment evaluations and update other investment data. During this time, you will notice that the site will continue to be in “beta” as we deliver additional key features.

But we can’t simply make this an exercise in federal agency reporting. That is why we started this blog. We want to hear from you about what works and what doesn’t with the site. Is there a more innovative approach that an investment should consider? Does the contract data look incorrect to you? Is there an application that we should add? This is a site to serve you, and to do that, we need to hear from you.

So bookmark this blog, and come back to us often. There is a lot happening over the next few weeks as we review the entire federal IT portfolio, assess the performance of investments, identify areas to save money, improve performance, and share best practices.

First | Prev   1 2