| layout | title | permalink | comments |
|---|---|---|---|
page |
Other countries |
other-countries/ |
true |
- News coverage
- The difference between 18F and USDS by Ben Balter (ex-PIF)
- Official sites
- US Digital Service (USDS). "We're on it boss (okay, listen, here’s what you’re going to do)"
- 18F. Software engineering and culture consultant. -- "Here’s the best way to build software (and you can too!)"
- 143 people (as at Jan 2016).
- 18F guides: Curated knowledge base of best practices and guidelines.
- 18F partners with other organisations on a fee-for-service basis. Partnership Playbook.
- Structure: 18F has 143+ people, with the Consulting team (design and product strategists), Design team (Frontend and Visual designers), and Delivery team (software developers, product leads, and SREs).
- Presidential Innovation Fellows. Parachute technologists from private sectors into government agencies for 1-year stints.
- Code for America. Non-profit that pairs local government with teams of experienced technologists for 1 year. Like Teach for America, but for coding.
- UK GDS
- Background: Martha Lane Fox's masterplan
- GDS Service Manual: a set of guidelines and useful information
- Section for CTOs. Useful for educating stakeholders (not just CTOs) on technical issues, e.g. how to treat security or open source software.
- Government as a Platform
- High-level introduction by Mike Bracken
- Technical elaboration on GaaP: Building a platform to host digital services
- Main idea: from this to this
- Looking at open-source PaaS technologies
- Non-technical explanation of GaaP: GaaP for the rest of us
- Some tips from the UK to the White House on making the US Digital Service a success - Diginomica
- Describes transition issues, including handling vendor backlash, handling change within the government, driving culture change
{% include common.md %}