Transcript
Page 1: Large + successful + government + IT + Agile = Census

Large + successful + government + IT + Agile = Census

Leon Maritz

June 2014

Page 2: Large + successful + government + IT + Agile = Census

I’m going to cover

• Census• Scrum Basics• Census in 3 Stages• Summary of Agile Successes• Census Successes• Census Adoption

Page 3: Large + successful + government + IT + Agile = Census
Page 4: Large + successful + government + IT + Agile = Census

Census Overview

• Recruitment• Training• Distribution• Online• Collection• Analysis• Output

Page 5: Large + successful + government + IT + Agile = Census

Census is large

6.4 million census forms to

1.8 million homes

Page 6: Large + successful + government + IT + Agile = Census

Census is large

About $72 million

Page 7: Large + successful + government + IT + Agile = Census

Census is large

7,000 trained collectors

Page 8: Large + successful + government + IT + Agile = Census

Census is large

Large IT system

Page 9: Large + successful + government + IT + Agile = Census

* *

Page 10: Large + successful + government + IT + Agile = Census

Scrum Basics

Page 11: Large + successful + government + IT + Agile = Census

IT Development in 3 StagesEarthquakes

Stage 1 Apr 2009 to Sep 4, 2010 (Census 2011)

Stage 2 Sep 4, 2010 to Feb 22, 2011

Stage 3 After Feb 22, 2011 (Census 2013)

Page 12: Large + successful + government + IT + Agile = Census

Stage 1 Apr 2009 to 4 Sep 2010

Page 13: Large + successful + government + IT + Agile = Census

* *

Page 14: Large + successful + government + IT + Agile = Census

Daily Stand-ups

Page 15: Large + successful + government + IT + Agile = Census

* *

Page 16: Large + successful + government + IT + Agile = Census

* *

Page 17: Large + successful + government + IT + Agile = Census

Retrospective

• What went well• What didn’t go that well• Improvements• Acknowledgements

Page 18: Large + successful + government + IT + Agile = Census

What went well

• Training - Scrum master and Product Owner• Agile Champion• Backlog Review• Quick feedback – thin slices • Inspect and adapt

Page 19: Large + successful + government + IT + Agile = Census

What didn’t go so well

• Estimation – software upgrade, Technical debt • Over projection on Sprint Backlog• Separate seating per role• Release to UAT as definition of Done

Page 20: Large + successful + government + IT + Agile = Census

What the business thought

• I like the approachability• I like the more open communication• I like the transparency

Page 21: Large + successful + government + IT + Agile = Census

Stage 2 Sep 4, 2010 to Feb 22, 2011

Page 22: Large + successful + government + IT + Agile = Census

• Need Feb building pictures

Page 23: Large + successful + government + IT + Agile = Census

What went well

• Co-location• Definition of Done changing to In Production• We learnt to estimate better

Page 24: Large + successful + government + IT + Agile = Census

What didn’t go so well

• Multiple Product Owners• Stories bigger than 13• Disruption due to Earthquake

Page 25: Large + successful + government + IT + Agile = Census

What the business thought

• I like being at the stand-ups• I like the fact that the messenger does not

influence the priority of a story

Page 26: Large + successful + government + IT + Agile = Census

Stage 3 After Feb 22, 2011

Page 27: Large + successful + government + IT + Agile = Census

Need picture of Level 3

Page 28: Large + successful + government + IT + Agile = Census

* *

Page 29: Large + successful + government + IT + Agile = Census

* *

Page 30: Large + successful + government + IT + Agile = Census

Kanban – Visual Card

• Visualize the workflow• Limit work in Progress• Manage flow• Make process policies explicit• Improve collaboratively

Page 31: Large + successful + government + IT + Agile = Census

What went well

• Evolution is ok• Kanban• Team Trust• Working from home• Government Cloud

Page 32: Large + successful + government + IT + Agile = Census

What didn’t go so well

• User stories over 13

Page 33: Large + successful + government + IT + Agile = Census

What the business thought

• I like fast track• I like being able to propose a user story at any

time

Page 34: Large + successful + government + IT + Agile = Census

Summary of Agile Successes• Transparency• Collaboration• Co-location• Continuous improvement• Multiple Product Owners• Self organized teams

Page 35: Large + successful + government + IT + Agile = Census

Remaining Opportunities

• Deployments• Automate

Page 36: Large + successful + government + IT + Agile = Census

Census Success

• Successful census - 5 march 2013• Streamlined recruitment• Better training

• Government cloud• Quickstats

Page 37: Large + successful + government + IT + Agile = Census

Census Agile Adoption

• Census adopted Scrum for future census• Doing daily stand-ups• Census do Retrospectives• Census involved in Agile community of practice

Page 38: Large + successful + government + IT + Agile = Census

Large + successful + government + IT + Agile = Census

We are happy to help

Page 39: Large + successful + government + IT + Agile = Census
Page 40: Large + successful + government + IT + Agile = Census

What do we mean by benchmarking?

• Investigate the two sets of Agile implementations• How we differ and why?• What should we take from the process?• How can we share our experience?

Page 41: Large + successful + government + IT + Agile = Census

Why the Government

• Similar challenges• Same mandate - collaborate• We work for the same client

Page 42: Large + successful + government + IT + Agile = Census

Why is Agile a good place to start?

• Continuous improvement is built into Agile• Suggests looking outward for improvements• Promotes openness and courage• Provides common ground to establish

connections

Page 43: Large + successful + government + IT + Agile = Census

43

Long Term Vision

Page 44: Large + successful + government + IT + Agile = Census

Q & A


Recommended