Statistics New Zealand has been evolving their use of Agile practices since 2008. They initially used Scrum for some IT projects in 2008 and saw positive feedback. By 2010-2011, Agile was accepted within IT and training plans were implemented. Agile then spread to other teams within and outside of IT. From 2012 onward, they evolved to use Kanban and other Agile variations and Agile became more embedded in their processes. Their goal now is to continue maturing their Agile practices, introduce Agile coaching, educate their organization more, and share what they've learned about Agile externally with other government agencies.

1. The Evolution of Agile at Statistics
New Zealand
How our Agile evolution can be shared across Government agencies.
Presenters: Chanelle Becker & Joanne McGee
October 2013

2. Introductions
2

3. Statistics 2020 Te Kāpehu Whetū
“How we're creating the Statistical System of the Future”
3

4. Agile Maturity Journey
2009
2008 Use of
Scrum in
2010 2011
Agile
Agile Pilot
in Census
2011.
other
projects.
Positive
feedback
from teams
Agile spread
to other
teams in and
outside of
IT.
accepted
within IT.
Formal training
plans
implemented.
2012
Evolution into
Kanban and
other
variations.
Agile becomes
more
embedded.
2013
4

5. In the beginning………
Thanks Citi bank
5

6. Early 2008: from bad to worse
6

7. WHAT did we need to do to change?
7

8. The Stats:
8

9. "OK, maybe we
didn't get all the
bells and
whistles, but..."
"they were just
nice to haves".
"The team
have a great
satisfaction
and sense of
ownership"
Feedback
"Next time I
would try to get
more involved
in daily standups"
"The Agile
framework is
"well set up
to deal with
changes"
"What
surprised me
was the team
camaraderie"..
"the team
bond better"
"It's
important to
understand
the whole
culture"
"Constantly
having to
prioritise"...
"have to make
the hard calls"
"You never
lose sight of
the end
goal"
"The IT
Team and
the Business
Area worked
as a team"
“Split
locations a
challenge”
"A real
sense of
engagement
with the IT
team"
9

10. Feedback on our Process
Communication
up 87%
Delivering up
87%
Risk reduction
up 87%
Team fun up
86%
10

11. High Level Statistics NZ Agile SDLC
Each of the yellow boxes are shown in greater detail:
• giving the roles (who does what),
• order of execution (when to do it) and
• outcomes (what will be produced).
Agile Software Development Life Cycle
(IT Development Process)
Last step of Business Planning
Process
1
Concept
2
Initiate
3
Sprint Zero
4
Agile
Development
(Sprint 1-n)
5
Project Go
Live
6
Project
Closure
7
Support
11

12. Stats NZ E2E Enterprise Architecture
Blueprint
12

13. Business Interviews 2010/11
Key Programmes /
Projects
1. BEST
2. SDDM
3. Redesign of the
Accommodation
Survey
4. Business Toolbox
5. Selective Editing
6. Implementation of
ANZSIC06
7. 2011 Census
Development
8. Info Share Project
13

14. @ Stats Today
14

15. 15

16. • Agile is our primary method for
delivery - used for 80% of our
Programmes / projects
• Delivered all our IT projects
• Agile is being adopted by our
business units
• Able to deliver to our strategic
values
• Modernise the way we deliver
“stuff”
16

17. Census of Populations

18. 18

19. Fun!!!
19

20. Creative !!
20

22. What we’re doing now …
Undertaking a maturity
assessment
Roadmap to take Stats NZ
to the next level
• Introduce Agile Coaching
• Continue to educate our organisation
• Focus on AOG opportunities
22

23. Our Agile Journey – where to next ??
2009
2012
2008 Use of
2013
Evolution into
Kanban and
Scrum in
2010 2011
Start to share
Agile
Agile Pilot
in Census
2011.
other
projects.
Positive
feedback
from teams
Agile spread
to other
teams in and
outside of
IT.
accepted
within IT.
Formal training
plans
implemented.
other
variations.
Agile becomes
more
embedded.
Agile
externally
within
the wider
Government
sector
23

24. Long Term Vision

25. The Concept

26. Why the Government?
• Similar challenges
• Same mandate – collaborate
• We work for the same client

28. 28