8. - 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 platform
The Project
gareth rushgrove | morethanseven.net http://www.flickr.com/photos/iancarroll/5027441664
10. - 1 Product Manager
- 2 Project Managers/Fixers
- Roughly 10 Developers and Designers
- Roughly 20 Editors
- Occasional other colleagues and friends
The Team
gareth rushgrove | morethanseven.net
11. 31st January
On Time, Under Budget
Ship
gareth rushgrove | morethanseven.net
12. - 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 notes
The Retrospectives
gareth rushgrove | morethanseven.net
13. What We Liked
gareth rushgrove | morethanseven.net http://www.flickr.com/photos/benterrett/6792016319/
14. 1. Nice People
gareth rushgrove | morethanseven.net http://www.flickr.com/photos/phae_/6891988049
16. - 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-information
2. Dashboards*
gareth rushgrove | morethanseven.net
18. - 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 platform
3. Really Continuous Integration
gareth rushgrove | morethanseven.net
19. 4. Coding in the Open
gareth rushgrove | morethanseven.net
20. - 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 more
4. Coding in the Open
gareth rushgrove | morethanseven.net
21. What We Would Change
gareth rushgrove | morethanseven.net http://www.flickr.com/photos/benterrett/6792023445
23. - Project team should have a focussed physical space
- Limit disruption and noise as much as possible
- Keep monitors, cables, power supplies as identical as possible
5. Working Environment
gareth rushgrove | morethanseven.net
24. 6. Tighten Up Processes
gareth rushgrove | morethanseven.net http://www.flickr.com/photos/wryobservations/6876480163
25. - 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 start
6. Tighten Up Processes
gareth rushgrove | morethanseven.net
27. - Invest time in getting a clear shared view of the model
- Use Domain Driven Design or a similar formal tool
- Don't be afraid to continually review
- Hindsight is a wonderful thing, use it
7. System Complexity
gareth rushgrove | morethanseven.net
29. - More automation of a standard environment
- Invest time in better, simpler, shared view
- Ongoing effort, not just upfront cost
8. Development Environment
gareth rushgrove | morethanseven.net
31. - Limit Work-In-Progress to force more collaboration
- More pairing
- New things should be sold to others
- Create a physical environment that makes sharing easier
9. Knowledge Sharing
gareth rushgrove | morethanseven.net
32. - Nice People
- Dashboards
- Continuous Integration/Deployment
- Open Source
- Working Environment
- Process
- Complexity
- Development Environment
- Knowledge Sharing
Your Next Project
gareth rushgrove | morethanseven.net
33. - Web - https://www.gov.uk
- Github - https://github.com/alphagov
- Blog - http://digital.cabinet-office.gov.uk
- Feedback - https://getsatisfaction.com/govuk
More Information on GOV.UK
gareth rushgrove | morethanseven.net