• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Learnings from govuk

Learnings from govuk



Presentation on what the team behind GOV.UK learned from the rapid agile development process.

Presentation on what the team behind GOV.UK learned from the rapid agile development process.



Total Views
Views on SlideShare
Embed Views



1 Embed 4

http://us-w1.rockmelt.com 4



Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    Learnings from govuk Learnings from govuk Presentation Transcript

    • Learning from building GOV.UKCambridge Geek Night 20th February 2012gareth rushgrove | morethanseven.net
    • Gareth Rushgrovegareth rushgrove | morethanseven.net
    • TextWork at UK Government Digital Servicegareth rushgrove | morethanseven.net
    • Serious Government Businessgareth rushgrove | morethanseven.net http://www.flickr.com/photos/phae_/6796331463
    • Blog at morethanseven.netgareth rushgrove | morethanseven.net
    • Curate devopsweekly.comgareth rushgrove | morethanseven.net
    • The Projectgareth rushgrove | morethanseven.net http://www.flickr.com/photos/iancarroll/5027441664
    • - A Beta of a Single Domain for Government- Focus on Citizen needs; Business and Government comes later- Built in-house, at the new Government Digital Service- Not just a site, the start of a platformThe Projectgareth rushgrove | morethanseven.net http://www.flickr.com/photos/iancarroll/5027441664
    • The Teamgareth rushgrove | morethanseven.net http://www.flickr.com/photos/dafyddbach/6829592009
    • - 1 Product Manager- 2 Project Managers/Fixers- Roughly 10 Developers and Designers- Roughly 20 Editors- Occasional other colleagues and friendsThe Teamgareth rushgrove | morethanseven.net
    • 31st January On Time, Under BudgetShipgareth rushgrove | morethanseven.net
    • - Three individual sessions: process, technology, content- Each between one and two hours- Focused on institutional (over individual) learning- Run by someone not directly involved in the project- Used more than 500 post-it notesThe Retrospectivesgareth rushgrove | morethanseven.net
    • What We Likedgareth rushgrove | morethanseven.net http://www.flickr.com/photos/benterrett/6792016319/
    • 1. Nice Peoplegareth rushgrove | morethanseven.net http://www.flickr.com/photos/phae_/6891988049
    • 2. Dashboardsgareth rushgrove | morethanseven.net
    • - Great places to experiment with new technology- Can never have too many screens- Good way of highlighting problems quickly- Great conversation starters * More information on our dashboard collection at http://digital.cabinet-office.gov.uk/blog/radiating-information2. Dashboards*gareth rushgrove | morethanseven.net
    • 3. Really Continuous Integrationgareth rushgrove | morethanseven.net
    • - Visibility of test results- Continuous deployment to a ‘preview’ environment- Log of what was deployed when and by whom- Ad-hoc task automation - cache purges, error page updating- Jenkins makes an excellent platform3. Really Continuous Integrationgareth rushgrove | morethanseven.net
    • 4. Coding in the Opengareth rushgrove | morethanseven.net
    • - Nearly all code public on GitHub- Already accepted a pull request from outside Government- Asked “why private?” rather than “why public?”- Interest from Quebec, New York and Brazil and more4. Coding in the Opengareth rushgrove | morethanseven.net
    • What We Would Changegareth rushgrove | morethanseven.net http://www.flickr.com/photos/benterrett/6792023445
    • 5. Working Environmentgareth rushgrove | morethanseven.net
    • - Project team should have a focussed physical space- Limit disruption and noise as much as possible- Keep monitors, cables, power supplies as identical as possible5. Working Environmentgareth rushgrove | morethanseven.net
    • 6. Tighten Up Processesgareth rushgrove | morethanseven.net http://www.flickr.com/photos/wryobservations/6876480163
    • - Stories should be written cross-team- Define value for every story- Estimate story size separately from sprint planning- Consider support and maintenance process from the start6. Tighten Up Processesgareth rushgrove | morethanseven.net
    • 7. System Complexitygareth rushgrove | morethanseven.net
    • - Invest time in getting a clear shared view of the model- Use Domain Driven Design or a similar formal tool- Dont be afraid to continually review- Hindsight is a wonderful thing, use it7. System Complexitygareth rushgrove | morethanseven.net
    • 8. Development Environmentgareth rushgrove | morethanseven.net http://www.flickr.com/photos/benterrett/6800713009/
    • - More automation of a standard environment- Invest time in better, simpler, shared view- Ongoing effort, not just upfront cost8. Development Environmentgareth rushgrove | morethanseven.net
    • 9. Knowledge Sharinggareth rushgrove | morethanseven.net http://www.flickr.com/photos/jamie_p_arnold/6806731039
    • - Limit Work-In-Progress to force more collaboration- More pairing- New things should be sold to others- Create a physical environment that makes sharing easier9. Knowledge Sharinggareth rushgrove | morethanseven.net
    • - Nice People- Dashboards- Continuous Integration/Deployment- Open Source- Working Environment- Process- Complexity- Development Environment- Knowledge SharingYour Next Projectgareth rushgrove | morethanseven.net
    • - Web - https://www.gov.uk- Github - https://github.com/alphagov- Blog - http://digital.cabinet-office.gov.uk- Feedback - https://getsatisfaction.com/govukMore Information on GOV.UKgareth rushgrove | morethanseven.net
    • We’re Hiringgareth rushgrove | morethanseven.net http://www.flickr.com/photos/benterrett/6852348725/
    • Questions?gareth rushgrove | morethanseven.net http://flickr.com/photos/psd/102332391/