lessons learnt from agile in local government
DESCRIPTION
Presentation from UKGovCamp 2011 #ukgc11 about lessons learnt from going Agile in local government.TRANSCRIPT
![Page 1: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/1.jpg)
Lessons learnt from going Agile in local
governmentMichele Ide-Smith
![Page 2: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/2.jpg)
BeforeO It took ages to get development
underwayO Stakeholders were impatient to see
resultsO Developers felt micro-managedO Lots of long, tedious meetingsO Projects dragged on, and on, and onO There was unfinished functionalityO Stakeholders didn’t get what they
expected
![Page 3: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/3.jpg)
The waterfall model
![Page 4: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/4.jpg)
AfterO Projects show results much more quicklyO Clear expectation of time and cost up
frontO Stakeholders are informed and involvedO Requirements can and do changeO Developers have more autonomyO Functionality gets finished and deployed
(mostly)
![Page 5: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/5.jpg)
![Page 6: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/6.jpg)
Scrum method
![Page 7: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/7.jpg)
Example backlog
![Page 8: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/8.jpg)
Example burndowns
![Page 9: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/9.jpg)
Top lessons learnt
1. No silos – everyone must buy in to Agile
2. Estimation is still important3. Agile might not suit all dev projects4. Sprints need dedicated resource5. Don’t skimp on planning6. Build multi-disciplinary teams7. Nuture collaboration
![Page 10: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/10.jpg)
1. No silosO Projects have dependenciesO Sprints require tight coordination of
resources and other workstreams (inputs/outputs)
O Get buy-in to using Agile methods across the organisation through early education
O Avoid unnecessary blockers!
![Page 11: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/11.jpg)
2. Estimation is still important
O Developers break down user stories into tasks
O Estimation using complexity pointsO Developers must learn their velocity
(progress in each sprint)O Or their burndown (backlog progress)
will resemble a flatline
![Page 12: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/12.jpg)
3. Agile may not suit all dev projects
O Agile works well for mature productsO Can lead to quick progress and great
resultsO New projects with unknowns carry
more riskO Still possible to have an unfinished
product
![Page 13: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/13.jpg)
4. Sprints need dedicated resource
O Scrum roles need dedicated resourceO Other work commitments are
blockers!O Product owners should attend daily
stand ups, planning and review meetings
![Page 14: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/14.jpg)
5. Don’t skimp on planning
O Plan ahead of development SprintsO Sometimes called ‘Sprint Zero’O Set up environments for dev and
testingO Conduct user researchO Start design workO Technical feasibility
![Page 15: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/15.jpg)
6. Build multi-disciplinary teams
O Think about the complete user journey
O How will software be implemented in a mature, working website?
O Include content writers, UX’ers and sys admins in the team
![Page 16: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/16.jpg)
7. Nurture collaboration
O Avoid sending long emailsO Co-locate developers, product
owners, consultants, UX’ers and content writers
O Otherwise, use phone conferencing and virtual meetings
O Stick designs up on wall space or windows
![Page 17: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/17.jpg)
BarriersO Cultural: silos, lack of management
buy-inO Lack of dedicated resource during
sprintsO Lack of dedicated meeting rooms for
daily stand-ups and other meetingsO Little or no wall space for
collaborating on and reviewing designs
![Page 18: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/18.jpg)
Remember the 12th Agile principle
“At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.”
![Page 19: Lessons learnt from agile in local government](https://reader037.vdocuments.net/reader037/viewer/2022110303/54c815d04a7959220b8b45a0/html5/thumbnails/19.jpg)
For more info:O My going Agile blog postO My barriers to Agile web design postO Agile manifesto and principlesO Scrum Alliance