2016-04-26

Delivery of Things World 2016 - Day 2

... continuing with my notes from the second day:
  • From oil tankers to speedboats by Jonathan Smart, Head of Development Services at Barclays (keynote):
    • They had 400 internal standards (lots of regulation) and used waterfall.
    • They are currently in the process into an agile organization. 800+ teams working with agile practices, 3x more stories finished than a year before. He showed a graph indicating a strong correlation that apps being deployed more often lead to less production incidents.
    • Cultural changes may take years.
    • Don't scale agile. Descale the work first.
    • Shu Ha Ri.
    • Disciplined Agile used as scaling framework (here and here you can find more information about this framework).
    • Implement communities of practice.
    • Story telling, training and coaching are essential.
    • Leadership training.
    • Head for technical excellence.
    • Agile architecture (no monolithic architecture).
    • DevOps is a practice, not a product.
    • They implemented a simple control tool: Answer 20 questions (before: hundreds), the number of control points were reduced from 7 to 2.
    • Blending not clashing (one size does not fit all): Be agile in adoption, sometimes different speed in adoption is required.
    • Embrace continual change.
  • Transforming application delivery for Continuous Innovation by Jonny Wooldridge, CTO at The Cambridge Satchel Company (keynote):
    • "It's all about the code."
    • Heavily invested in increasing excellence & craftsmanship with their move towards agility.
    • Legacy applications can impede moving towards agility.
    • Define and decouple your "pace layers".
    • Watch out for corporate equilibrium: Enterprise equilibrium (wrong technology, wrong people, wrong frameworks, wrong 3rd party suppliers) tends to drive DevOps adoption backwards.
    • Build new initiatives the right way (reduce complexity, reduce legacy code).
    • Kill dependencies.
    • Focus on APIs.
    • Don't create new legacy (i.e. don't use legacy approaches just because they are quickly available, you have to actively invest into agile). 
  • Accelerating DevOps adoption: Patton and Gandhi by Stephen Fishman, Senior Director, Platforms & Services at Autotrader (keynote):
    • Never be ashamed to ask for excellence.
    • Religiously strive for collegiality.
    • How to persuade people being skeptic about agile transformations:
      • Step 0: Assume positive intent.
      • Step 1: Empathize.
      • Step 2: Point to higher ground.
      • Step 3: Wait.
      • Step 4: Repeat.
  • World Café Sessions (smaller groups of about 20 people discussed a certain topic for about 30 minutes; we had some good discussions about the integration of developers and ops people, the introduction of continuous delivery and agile methods):
    • Analyzing Continuous Delivery: What are the advantages - big and small - that you can look forward to once you have Continuous Delivery in place? by Lars Bendix, Professor of Software Engineering, Department of Computer Science at Lund Institute of Technology.
    • Ericsson Eurolab: World of DevOpsCraft by Almudena Rodriguez Pardo, Senior Scrum Developer, ICT Development Center Eurolab Aachen at Ericsson and by Norma Acevedo, Product Deployment Manager at Ericsson.
    • Don’t build a golden prison – Dos and Don’ts for working with DevOps by Udo Pigorsch, DevOps System Manager at Axel Springer SE.
    • Continuous Quality and Continuous Delivery: How to have both by Tobias Kutzer, Senior Solution Architect at Worksoft.
    • Data-Driven DevOps to Improve Velocity, Quality, and Impact / Using Continuous Delivery to build products customers actually use by Andi Mann, Chief Technology Advocate at Splunk.
  • Screwing Up For Less by Stephen Hardisty, Director of Engineering at Rocket Internet (keynote):
    • If people feeling comfortable, they get careless (see "risk homeostasis", also here).
    • Embrace feature toggles.
    • Make problems more obvious (i.e. visibility, wall screens).
    • Automate all the things.
    • Managers: No shouting! (I.e. no blaming.)
    • Reduce risk by using technologies that are already established in your organization.
  • Balancing the 3 pillars of DevOps - Managing people, process, and technology change to grow a DevOps culture with Stephen Hardisty, Director of Engineering at Rocket Internet, Jonny Wooldridge, CTO at The Cambridge Satchel Company and Dave Nolan, CTO at AppearHere (panel discussion):
    • Topics addressed:
      • Hire people with the right mindset.
      • Establish culture and mindset.
      • The right tools.
      • Trust in the change.
      • Gain speed and reduce time to market.
Panel discussion

No comments:

Post a Comment