Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous Delivery - Three Epics to Get You Started | Lars Kruse | LTG-25

1,160 views

Published on

Presentation held at Lean Tribe Gathering 25 in Gothenburg feb 19 2015.

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Continuous Delivery - Three Epics to Get You Started | Lars Kruse | LTG-25

  1. 1. Continuous Delivery Three Epics To Get You Started Lars Kruse (lak@praqma.com) Partner & Co-founder, Praqma
  2. 2. Agile Manifesto ● Four doctrines, twelve Principles # 1 # 7
  3. 3. Continuous Delivery Maturity Model
  4. 4. Models used at... ● Grundfos ● Danfoss ● Brüel og Kjær Sound & Vibration ● Atmel (Norge) ● Novelda (Norge) ● Møller Gruppen (Norge) ● Cryptera ● CodeSealer ● Politiet ● Volvo (Sverige) ● Schneider-Electric ● Danmarks Radio ● CA Techno
  5. 5. Software Factory ● Unplanned work ● Queued work # 8 # 10
  6. 6. Software Factory ● Unplanned work ● Queued work Urgency ImportanceLow High High Not urgent and not important Not urgent but very important Very urgent but not important Very urgent and very important
  7. 7. Software Factory ● Unplanned work ● Queued work q qL = λW Little’s Law
  8. 8. The Andon Cord Build Quality In The Andon is a system, that empowers a team member to stop the line ...so you don’t pass a defect on to your next process and ultimately there is no way a customer will receive a defect. I you’re gonna empower people you’ll have to be strong enough and committed enough to follow your rules and come up and thank your team member for stopping the line and ask “what can I do to help”?
  9. 9. VCS Developer I’m done! Work item Continuous delivery Pipeline Automation Platform Done done ...nope! CoDe Story-line
  10. 10. Components and products
  11. 11. Three Epics To Get You Started Infrastructure ● Establish understanding of CoDe ● Setup tool-stack ● Assign roles Proof of concept ● Build a pipeline ● Implement status quo ● Include new features ● Adjust team processes Proof of technology ● Size hardware correctly ● Pay off technical debt ● Evaluate - replace/consolidate Engage stakeholders Show results Prepare for roll- out www.josra.org/blog/code-epics.html
  12. 12. www.code-conf.com Continuous Delivery Conferences

×