Software // Productivity/Collaboration Apps
News
5/15/2014
02:43 PM
Connect Directly
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Open Source Lessons For Feds

White House and agency IT leaders discuss how open source can empower government IT project teams, at FOSE conference in Washington, D.C.

5 Online Tools Uncle Sam Wants You To Use
5 Online Tools Uncle Sam Wants You To Use
(Click image for larger view and slideshow.)

Government executives may have doubts about using open source software, but they could learn a few management lessons from those who live and work in the open source development community, a group of federal IT leaders said this week.

"It's not about code, but the process of making a product [that distinguishes open source software development from the traditional waterfall approach]," said Matthew Burton, former acting CIO at the Consumer Financial Protection Bureau. "You can do open source practices without having to share code."

Burton, along with CFPB senior designer Victor Zapanta, White House aide Erie Meyer, and GitHub government evangelist Ben Balter, spoke at this week's FOSE government technology conference in Washington, providing insiders' views on how open source workflow practices could empower teams of all sizes, even in stodgy federal agencies.

[There's a religious war between the defenders of open-source and commercial product supporters. Learn why: Open-Source Vs. Commercial Software Is A False Dilemma.]

As one of the executives who took part in the launch the Consumer Financial Protection Bureau, Burton offered three lessons that even dedicated commercial-off-the-shelf (COTS) users could take away from open source development practices and apply on the job:

1. Get your products in the hands of actual users -- releasing improvements early and often.
"The open source environment tends to focus on everything that happens after the launch, whereas most enterprises focus on everything ahead of the launch," Burton said. Instead of waiting for a product owner or manager to approve and release large batches of updates, he advised, get feedback from users right away on a specific feature or enhancement. The interaction identifies problems sooner and speeds decision making.

Matthew Burton, as seen in a Consumer Financial Protection Bureau video.
Matthew Burton, as seen in a Consumer Financial Protection Bureau video.


2. Use more products at a lower cost.
In enterprises there's a tendency to think one product will solve all the problems, but that leads to massive projects that can consume all of your project funds without your knowing if the product will ultimately work. Burton pointed out. Better to spread the money into smaller projects -- and consider open source software that can usually be customized less expensively than mammoth software installations.


3. Build for other developers in addition to actual users.
"If you're an open source coder, your hope is that others will improve your product. In an enterprise, working with proprietary software, there's not the same incentive," Burton said. But as leaders turn over and new developers arrive, providing thoughtful documentation can help preserve the value and legacy of your work.

Ben Balter, a recent White House Presidential Innovation Fellow and leading voice for open government data and open source software, argued that open source practices bring about a level of collaboration and speeds decision making in ways that elude traditional projects that rely on sequential decisions.

"Traditional waterfall software development leads to low visibility and management by email," Balter said. "The always-available, asynchronous, and lock-free nature of open source projects offers a useful model for working in tight-budget environments." Workflow constraints, he added, can teach us a lot about working in a more collaborative world.

"What do you do when your agency is just hell-bent on using COTS software?" an Interior Department employee in the audience asked the panelists. He expressed the frustration he and his team experienced after providing a cost/benefit analysis that showed how in-house, open source development was the better business decision over a COTS integration.

"Forget the cost/benefit analysis, and the memo storm, and the decision matrix. Just make something!" answered Erie Meyer, a senior advisor to US CTO Todd Park. "The only way to move these conversations forward is to build what you're talking about. It's not that people disagree with you," she suggested, "They just don't know what you're talking about."

Meyer pointed to a new resource that could help federal open source advocates: a website called GovCode that indexes government open source projects and offers links to open source software code and the developers working on them. The projects are all hosted on GitHub. One example is the White House iOS mobile app code that fetches, caches, and displays articles, photos, and live and on-demand video from multiple sources.

If there's one other reason for considering open source practices in the government workplace, added Zapanta, who advised the Clinton and Obama campaigns and is a founding member of CFPB's technology and innovation team, it's the signal it sends to prospective employees coming out of top engineering and technology schools.

"If you're at Berkley or Carnegie Mellon and you drop the fact that you work on SharePoint or dot.net, their eyes glaze over," he said. "We want people working on projects in government. Drop [open source application] names like Ruby on Rails and Python, and you'll get their interest."

Could the growing movement toward open source hardware rewrite the rules for computer and networking hardware the way Linux, Apache, and Android have for software? Also in the Open Source Hardware issue of InformationWeek: Mark Hurd explains his "once-in-a-career opportunity" at Oracle.

Wyatt Kash is a former Editor of InformationWeek Government, and currently VP for Content Strategy at ScoopMedia. He has covered government IT and technology trends since 2004, as Editor-in-Chief of Government Computer News and Defense Systems (owned by The Washington Post ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Oldest First  |  Newest First  |  Threaded View
WKash
50%
50%
WKash,
User Rank: Author
5/15/2014 | 4:47:12 PM
Open Source Enthusiasts
The outlook for attracting the next generation of talent might not look very promising for the federal government these days, given federal budget cuts and a host of other reasons.  But it is encouraging to the see energy, creativity and passion reflected in the four individuals who discussed this topic at FOSE this week: @Erie Meyer; @BenBalter; @matthewburton; @victorzapanta.
Gary_EL
50%
50%
Gary_EL,
User Rank: Ninja
5/15/2014 | 10:33:17 PM
Re: Open Source Enthusiasts
I agree. Austerity is starting to bite so deeply that federal agencies are being forced to eat their seed corn. It will be increasingly difficult for them to attract the kind of talent needed to implement these open source lessons. They will be forced to use off-the-shelf products and to be increasingly dependent on outside consultants
WKash
50%
50%
WKash,
User Rank: Author
5/16/2014 | 9:57:38 AM
Re: Open Source Enthusiasts
Gary_EL, one challenge I see as well, is that open source projects rely to a certain extent on the willingness of participants to go the extra mile to work together and contribute.  But that kind of spirit (like capital) tends to move to where it's welcome, and government has become a decidely less welcome place to work.

 
SachinEE
50%
50%
SachinEE,
User Rank: Ninja
5/16/2014 | 2:02:18 PM
Re: Open Source Enthusiasts
With the growth of modern technology and the immense opportunities that present day entrepreneurship has to offer, it was easy to see that it was only a matter of time before all the best talents started drifting towards private enterprises rather than work for the government. Even the incentives that used to draw talent to government jobs, such as job security, no longer seem to hold any power and the government must start thinking of ways to encourage free enterprise within their institutions if they hope to put a halt to this trend.
Gary_EL
50%
50%
Gary_EL,
User Rank: Ninja
5/16/2014 | 2:08:21 PM
Re: Open Source Enthusiasts
SachinEE, they really can't, because money talks, and Congress holds the purse strings.I make part of my living working for a government contractor, and the Feds can't even live uop to their existing agreements, because they just don't have the money. As for job security, maybe for the older employees, but it's completely gone for new hires.
WKash
50%
50%
WKash,
User Rank: Author
5/16/2014 | 3:22:44 PM
Re: Open Source Enthusiasts
Gary EL - Sad but true.  Working for the government was always pretty much a commitment to a marathon; the promise at the end was a pretty sweet pension prize --  for those wiling to stick it out. But for newcomers, a government job (if they're lucky) is a chance to add some potentially attractive credentials to your resume, but longer term, it's hard not to see a punishing road ahead on which to build a career. Thank goodness we still have so many willing to serve their country inspite of that.   
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Tech Digest September 18, 2014
Enterprise social network success starts and ends with integration. Here's how to finally make collaboration click.
Flash Poll
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
The weekly wrap-up of the top stories from InformationWeek.com this week.
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.