What can Enterprise IT ops look like in a world eaten by software? How do you cope with vendor releases every few days when your release cycle takes weeks? This is the story of how IT engineering and ops teams in a global bank collaborated with an XP team and learned to changed the way they work.

1. High Performance Ops for Enterprise PaaS
Dan Young | EngineerBetter | @dan0young
Adventures with small batch sizes in a big bank

2. The context
Global Bank
Thousands of Devs
Lots of Cloud Foundry
Traditional Ops
Image credit: thethreesisters

3. The beginning
Change is costly
Manual ops heroics
2-3 week release cycle
Big batches & high risk
Lots of rework

4. Our hopes
Influence attitudes to change
Faster cycle time
Happier, scalable team
Lower risk

5. Key technical ingredients
Cloud Foundry (commercial distro)
BOSH
Concourse CI
A well known public cloud

6. Results so far
Continuous Delivery
100% Reproducibility
Platform upgrades itself
First apps approved

7. Operations = Development
Cloud Foundry is itself Apps
Pairing, TDD, CI
Platform as a Product
Infrastructure as is Code
Communicate all the things

8. What have we learnt so far?
Kill dev/stage/prod naming
Build times are the enemy
‘Non-blocking pairs’ pattern
Self-reliance changes org dynamics

9. Co-located team
Small batch comms
Peer pressure is magic
Leaders create more leaders
Change radiating through people

10. Your story is yours alone.
Agile solves reveals problems
No secret recipes
No maturity models
Just continuous learning
http://yipa.org/training/online/on-demand/telling-your-impact-story/

11. @dan0young
dan.young@engineerbetter.com