View
154
Download
0
Category
Preview:
Citation preview
Our Journey
NaaS
June 2013:
We need a
Continuous
Integration server so
want to install
Jenkins. Can you
help?
1 July 2013:
Where’s your business case?
25th July 2013:
Here’s the business
case.
20th of August 2013:
Is it in your work plan?
27th August 2013:
Workplan - Building
and maintaining a CI
server for the
centralized software
development team.
The time frame is Oct-
13
28th August 2013:
You must provide an
architecture diagram for the
Jenkins Server in context.
5th September 2013:
Here’s the
architecture diagram.
26th September 2013:
Could you please provide more details
on the links to the Internet. For each of
the traffic flows – what direction; IPs;
traffic type/ports?
4th October 2013:
Here’s the info.
1 Nov 2013:
Happy for the team to undertake the build of this server,
however, before we do, do you have any form of plan
and/or requirements indicating the software required;
interaction between desktops; or connection to other
servers or the Internet that sheds light on the solution?
Depending on the requirements/software etc you may
also need to engaged SDS for software purchases, the
ITSA and possibly others. You need to write a PID.
3rd December 2013:
We are working on
the PID.
11th December 2013:
This is getting big - we need to have a
meeting about requirements and
everything but we don’t have time until
after Xmas. How about 21st January
2014?
3rd December 2013:
We are working on
the PID.
11th December 2013:
This is getting big - we need to have a
meeting about requirements and
everything but we don’t have time until
after Xmas. How about 21st January
2014?
21th January 2014:
You need to specify your requirements
and, in particular, conduct a threat and
risk assessment (TRA)!
4th March 2014:
Requirements
overview produced,
solution architecture
and TRA in progress
15th March 2014:
You must also develop a Release Plan…..!
2014 “cuts”
On Vogons:
“They are one of the most unpleasant races in the
Galaxy. Not actually evil, but bad-tempered,
bureaucratic, officious and callous. They wouldn't
even lift a finger to save their own grandmothers
from the Ravenous Bugblatter Beast of Traal
without orders – signed in triplicate, sent in, sent
back, queried, lost, found, subjected to public
inquiry, lost again, and finally buried in soft peat
for three months and recycled as firelighters.”
Not empowering
Not collaborative
Not iterative
Not value focused Not innovative
Empowerment
Linda Rising, 2015
Our Journey
Vision: Multi-disciplinary science teams with the embedded scientific data and computing capability to
self-serve to cloud and national research infrastructure platforms (Antony Stinziani 2015)
Quote: The most successful organisations in this new era will be those that are able to continuously
evolve, continuously innovate and harness the creativity of their employees (Cameron Gough 2015).
Goals Actions
Delivering Better Services Outsource Commodity ICT and focus on
scientific data and computing.
Empowered People Build an Agile Culture with ICT capability
and capacity embedded into science teams
Advanced Geoscience Focus on Digital Science in support of GA’s
outcomes.
● 4 staff embedded for 3 months at Digital Delivery Centre (AusPost) in 2015
● Agile Programme Manager & Iteration Managers
● The Autobots: DevOps Team - Continuous Delivery to Cloud
● Agile Digital Science Delivery Teams
● Agile Workshops, Showcases and Program Increment Day
● Canberra Infracoders Meetup!
● Digital Science Strategy
AusPost Australian Tax Office Digital Transformation Office
Infracoders Science Divisions …..
Digital science means a radical transformation of the nature of science and innovation due to the
integration of ICT in the research process and the internet culture of openness and sharing.
It is more open, more global and collaborative, more creative, and closer to society. It relies ICT-based
services and tools for data- and computing-intensive research in virtual and collaborative environments.
Digital science makes it possible not only to perform research more efficiently but to transform science.
Access the right mix of skills
Improve Planning and
Program Delivery
Establish an Agile way of working
Establish a quantitative
science platform Formalise Digital Science
Leadership
Recruiting
● Senior Developer (Technical Lead)
● Applications Architect
● DevOps Engineer
● Director of ICT Service Delivery
See https://recruitment.aurion.com/ga-jobs/ or talk to any of the GA folk.
The journey has just begun
Extra materialE
Access the right mix of skills
● Advertise GA Widely
● Crowdsourcing
● Collaboration (AMSI, DTO)
● Competitions
● STEM
HOW: Innovative approaches and savings from outsourcing
- More details in a moment
Establish an agile way of working
Approach is
● Value Focused
● Collaborative
● Adaptable
Multidisciplinary Science Teams are
● Autonomous
● Mobile
● Aligned
HOW:
● Agile Case Studies - e.g. in the
Integrated Digital Earth of Australia
(IDEA).
● Follow DTO leadership
Establish a quantitative science
platform
● Seamlessly leverage the full continuum of
platforms
● Flexible environments
● Fit for purpose
HOW:
● Rally up behind Data Platforms
● Focus on Open Source, cross
platform based on Linux.
● Not Microsoft, Matlab, etc
Improve Planning and Program Delivery
● Multi-year Science Program through Capacity Funding
● Time Boxing allocation of capacity
● Empower teams to prioritise own work throughout year
● Align documentation directly with value
● Procurement to support innovation
HOW:
● Influence Corporate Review
● Change ICT processes
Formalise Digital Science Leadership
● Digital science will underpin most outcomes in the future so
requires agency wide leadership.
● Chief Scientist to Chair
● Vision for future strategic scientific products and activities
in Geoscience Australia.
HOW:
● Help Chief Scientist
What is Agile?
Principles
Embracing Change
Collaboration
Empowerment
Quality at Source
Automation
Focus on Value
Instead of all at once
Incrementally
Agile Manifesto (2001)
We have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Linda Rising, 2015
Recommended