Last October, Secretary of Veterans AffairsEric K. Shinseki,W. Scott Gould and CIO Roger Baker moved to take unprecedented control of the VA's 280 IT programs, too many of which were not delivering any value for money.

As you may recall, the VA temporarily halted 45 information technology projects which were either behind schedule or over budget. After a review, 15 of the 45 IT projects were terminated or had their funding cut, another 17 committed to meeting milestones to deliver new functionality to customers, while the final 13 were going to be re-planned or restarted.

This action saved some $54 million.

Well, the VA's management team has followed that unprecedented move with another.

CIO Baker and his team reviewed the remainder of the VA's IT projects and found many of them wanting in some way, an article in Washington Technology reports. CIO Baker announced that only 92 of the 280 are currently authorized to spend their IT budgets.

As for the rest, 93 IT projects are being replanned, 53 have been moved into the not started bin, 21 have either been terminated or completed and 21 are in the "other" category, which I assume means they are still having their fates determined.

In somewhat of an understatement, CIO Baker is quoted as saying, "It is clear we are not spending a lot of money right now... We are being very tight on which projects we are starting to work on."

Kudos to the VA senior management for taking bold, aggressive action to bring what to many of the VA IT staff and contractors must seem privately as "unreasonable" oversight of their IT projects. I only wish that other US government departments would be as aggressive and brutally honest about the state of their IT projects.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less