Shared publicly  - 
 
“The budget cycle takes two years.”

Vivek brings up so many great points in this piece, but one I’ve been thinking about a lot is the cycle time of government software development.

Our office space at Code for America is the old Moto Development Group office. (We lobbied Cisco to give us the space for our program, and they generously agreed.) Last May, Cisco bought Moto for an undisclosed sum in order to build up their talent in their consumer products division, the cornerstone of which was the Flip camera (which Moto had helped design). By the following April, Cisco had shut down the division and all of the former Motos who’d occupied our office were out of jobs. 11 months from acquisition to shut down.

What happened? Things just changed too fast. People don’t need a Flip camera because they have awesome video on their phones. This isn’t a knock on Cisco for not seeing that coming, it’s about the dizzying speed of technology in the world today. Except in government. Where CIOs need two years to even budget for a project that is expected to last dozens of years.

There’s no sense in this, and there’s no win for the American public in it.
A decades-old methodology for managing software development projects and other government programs isn’t serving the public good. We need to find the political will to change things, or resign ourselves to continue wasting tons of public money.
Ending his run as the first chief information officer of the U.S., Vivek Kundra describes what it's like managing data on a really big scale.
11
5
Elizabeth Shell's profile photoAlexander Howard's profile photoAdam Augusta's profile photoJohn Bullard's profile photo
8 comments
 
Being the first CIO of the United States of America is a huge honor. But 2.5 years on a job having a steep learning curve makes Kundra a quitter.
 
The average time someone sits in a position at Kundra's level is 20 months, Gerald.
 
Seems like 2.5 years is hardly enough to even get started (in the Federal government, private industry is another story).
 
I remember what Katie Stanton said when she left State: "We make it really hard for people to serve our country." See: http://techpresident.com/blog-entry/headed-west-twitter-katie-stanton-reflects-washington Public service is incredibly difficult at that level, and I'm glad we have had Vivek for the time he's been here. Dealing with the criticism for leaving is just another part of the job (and nothing compared to some of the other challenges) but it is one more way we make it hard to serve.
 
As long as they manage to have a smooth transition. Lack of continuity with some of the other recent departures seems to have negatively impacted ongoing projects (e.g. ExpertNet).
 
Well Steve VanRoekel replacing Kundra is a fine appointment. I've heard him speak on changing the culture at the FCC, and he knows how to move things along. And the FCC website, with open data, etc. is stellar.
Add a comment...