Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
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
Login to see the comments