Scaling cd at the enterprise velocity2015 taco_bakker_markheistek
23
Scaling Continuous Delivery at the enterprise Taco Bakker Mark Heistek
-
Upload
mark-heistek -
Category
Technology
-
view
347 -
download
0
Transcript of Scaling cd at the enterprise velocity2015 taco_bakker_markheistek
Scaling Continuous Delivery at the enterprise
Taco Bakker Mark Heistek
About Taco Bakker
Ce
rtif
ied
Scr
um
ma
ste
r
CD tooling
Chairman of Release Automation
User Group Lean Six Sigma
About Mark Heistek
Father of two children
Sport fanatic
Our starting position
IT is a commodity; everyone can do IT
Internal customers
IT is a cost center
Quality through process adherence
Lots of manual work & handovers
Multiple sourcing partners
Scattered IT landscape
Non-functionals provided by infra
Where did we want to go? Higher quality Higher productivity Frequent releases (feedbackloop)
Our DevOps and Continuous Delivery evolution
Start of our own Java community
Engineering culture
May 2010
Full reorganization i.e. 180 full DevOps teams
Engineers hunger to take responsibility
May 2013
Oct 2009
New IT Mgt team
The will to change
Nov 2011
Discussion – who runs production.
Clear demarcation responsibilities infra and appl
Sep 2014
Need full automation infra & scalable systems
Build private cloud
Start full automation of IT processes
Continuous delivery pipeline – Jez Humble
May 2011
Oct 2010
Start of Mobile app development
1st Scrum team and start agile development
Ideas
Build
Product
Measure
Learn
Data
Stay ahead of competitors! Continuously learn and adapt
team vs enterprise
Team vs Enterprise
Best solution, cool factor, little rules, Lot of learning, build it yourself, high maintenance, little collaboration
Standardization, collaboration, re-use
tools
Team vs Enterprise
Best solution, cool factor, little rules, Lot of learning, build it yourself, high maintenance, little collaboration
Standardization, collaboration, re-use
High license costs, maintenance, version management, knowledge share, life cycle management issues
Low license costs, best practices, less maintenance, knowledge by community
Security
Team vs Enterprise
Best solution, cool factor, cowboy Lot of learning, build it yourself, maintenance No collaboration
Standardization, collaboration, re-use
High license costs, maintenance, version management, knowledge share, life cycle management issues
Low license costs, best practices, less maintenance, knowledge by community
Work around rules and regulations Make rules and regulations part of the pipeline
Ideas
Build
Product
Measure
Learn
Data
So HOW do we do this for Continuous Delivery @ING?
Feature Request list from IT user communities
Standard Continuous Delivery pipeline for ING
CD expert team collaborating with IT
communities
Metrics from all parts of the CD Pipeline
Collect all data through an Eventbus and store it
in a database
Analyze all data and present it to IT engineers
and IT Managers
How Automated
team maturity Automated
test analytics
Automated Acceptance
criteria
Control the pipeline
Eventbus
Database
System health monitoring
Automated Acceptance
Criteria
Automated Team
Maturity
Automated Test
analytics
Automated Acceptance Criteria
Automated team maturity
System health. Availability of the pipeline
Principles:
• All hardware, middleware and application
components are constantly monitored
• Automated alerts are generated
whenever a deviation occurs
New techniques are used to maximize the resilience of the CD pipeline
Higher quality √ Higher productivity √ Frequent releases (feedbackloop) √
Where are we now?
Taco Bakker @tsbakker65 Mark Heistek @markheistek
Thank you!
@tsbakker65
@markheistek
