The U.S. Defense Department is escalating its commitment to open source software with a proactive push for agency participation to publicly share custom-developed code.
In “Peace Through Entrepreneurship: Investing in a Startup Culture for Security and Development,” former State Department staffer Steven Koltai makes the case that world peace can best be achieved through nonmilitary means, especially entrepreneurship that leads to global job creation.
Innovation, disruption, accelerators, have all become urgent buzzwords in the Department of Defense and Intelligence community. They are a reaction to the “red queen problem” but aren’t actually solving the problem. Here’s why.
The Office of Naval Research has been one of the largest supporters of innovation in the U.S. Now they are starting to use the Lean Innovation process to turn ideas into solutions. The result will be defense innovation with speed and urgency.
Earlier this year, the Information Technology and Innovation Foundation published an assessment of federal government websites that includes rankings around page load speeds, mobile friendliness, Domain Name System Security Extensions, Secure Sockets Layer and accessibility.
The General Services Administration will host an in-person U.S. Federal Blockchain Forum meeting on July 18 in Washington, D.C., as part of an effort to facilitate virtual currency adoption within the federal government.
We just finished our second Hacking for Defense class at Stanford. Eight teams presented their Lessons Learned presentations.
With the help of GSA and the brand power of USA, the opportunity to truly scale impact is endless.
As of 20 January, President Obama signed the TALENT Act of 2017 (H.R.39) into law as one of his last acts as President.
The U.S. Department of Defense’s Defense Innovation Advisory Board approved 11 recommendations “aimed at keeping the Defense Department on the cutting edge in technology, culture, operations and processes.”
The General Services Administration has issued a request for information related to the federal government’s use of software-as-a-service.
By the end of the class our sponsors inside State had experienced a practical example of a new and powerful methodology which could help them better understand and deal with complicated international problems and apply technology where appropriate.
We’ve just held our seventh and eighth weeks of Hacking for Diplomacy at Stanford, and the attention our course is getting from Washington – and around the world – has been interesting.
U.S. Defense Secretary Ash Carter announced the DOD will open its third technology innovation “outpost” in Austin, expanding the reach of the Defense Innovation Unit Experimental that serves as a “bridge between those in the U.S. military executing on some of our nation’s toughest security challenges and companies operating at the cutting edge of technology.”
The Defense Information Systems Agency has released a series of videos and request for information for the National Background Investigation System, created in the wake of security incidents that lead to data breaches of millions of federal government employees and contractors.
With the release of a new identity management platform, 18F is slowly culling together all the requisite pieces for an easy-to-deploy, cloud-based federal government web management platform.
The White House released an official Federal Source Code policy that green lights the use and free distribution of software code developed for and by the U.S. Government.
Join a select cross-disciplinary class that takes real problems from the U.S. State Department and asks students to use Lean Methods to test their understanding of the problem and deliver rapid-fire innovative solutions to pressing diplomacy, development and foreign policy challenges.
After two years of helping lay a new foundation for how the federal government buys, builds and delivers government digital services, Technology Transformation Service Commissioner Phaedra Chrousos announced she is stepping down. I asked Chrousos to share some parting thoughts.
Government Technology’s Jason Shueh finally brings to light the core impetus surrounding backlash against 18F efforts to fix federal government technology development and procurement practices.
Hillary Clinton released her technology and innovation agenda that promises to expand the U.S. Digital Service and agency-specific digital teams, encourage the continued adoption of open source and open data and bring a more user-friendly approach to federal government operations.
The Federal Aviation Administration is looking for a chief data officer. Salary is $124,900 to $175,700. Application deadline is July 12.
The U.S. Government Accountability Office released a report on the fiscal and administrative state of 18F and the U.S. Digital Service, both established to make federal government websites work better for users, and it appears the agency could use some help from the two on its own site, gao.gov.
It’s very easy, especially in a political environment, and especially for a high-profile organization like 18F, to be critical of its operations. There are a long list of items I’d like to see GAO look into and, right now, 18F isn’t one of them.
We just held our seventh week of the Hacking for Defense class. Now with over 750 interviews of beneficiaries (users, program managers, stakeholders, etc.) almost all the teams are beginning to pivot from their original understanding of their sponsor’s problem and their hypotheses about how to solve them.
Last Week Tonight’s feature segment focused on antiquated 911 technology, particularly its inability to leverage mobile geolocation and effectively pinpoint a caller’s whereabouts from his or her cellphone.
The 5,000 sq. ft. lab Superpublic unites under the same roof for the first time innovation teams from the private industry, federal, state and city government agencies and from universities.
Grant cites two government originals, Central Intelligence Agency analyst Carmen Medina and U.S. Navy lieutenant Josh Steinman, who both worked to change traditional thinking within two large bureaucracies.
The White House extended the Federal Source Code Policy comment period to April 18 and, to date, there there are 147 comments with much of the discussion centered around licensing and security.
The White House has published a federal source code policy that requires custom code paid for by the U.S. government be made available to all federal agencies, and a portion be released to the public.