In most digital projects content is involved late. But agile methods create an opportunity to refocus content work on meeting user needs instead of publishing information. I was part of the team that developed GOV.UK, the single government website designed around user needs. Our content designers work in agile teams alongside developers, designers, researchers, and analysts. This shared ownership enables the team to create services that are simpler, clearer, and faster. Learn how to:
- adapt agile principles to the needs of content-heavy websites
- avoid the cult of volume by focusing on what your users need
- lead an agile team by encouraging people to publish early and iterate
• “the 15th week before the week in which the baby is due”
• “an amount which at least equals the lower earnings limit
which applies on the Saturday at the end of your qualifying
• “you've been employed and/or self-employed for at least
26 weeks in your 'test period' (66 weeks up to and
including the week before the week your baby is due) -
part weeks count as full weeks”
• “you earned £30 a week averaged over any 13 weeks in
your test period”
• start with the needs, not with the information"
• unite as a team (not as a discipline)"
• research continuously and make decisions with
• put the most effort into meeting the most
important needs ﬁrst"
• publish early, not perfectly"
• respond quickly to trends in feedback
GDS blog – http://gds.blog.gov.uk
Design principles – www.gov.uk/design-principles
Digital strategy – www.gov.uk/digitalstrategy
Service manual – www.gov.uk/service-manual
Performance – www.gov.uk/performance
Assisted digital – http://assisteddigital.blog.gov.uk
Digital inclusion – http://digitalinclusion.blog.gov.uk
Our code – www.github.com/alphagov