Principles of Continuous Delivery

I recently watched a presentation from Dave Farley outlining the “Why” of Continuous Delivery. In the presentation, Dave delivered a slide that outlines the guiding principles of the continuous delivery movement:

  1. Create a repeatable, reliable process for releasing software.
  2. Automate almost everything.
  3. Keep everything under version control.
  4. If it hurts, do it more often - bring the pain forward.
  5. Build quality in.
  6. Done means released.
  7. Everybody is responsible for the release process.
  8. Improve continuously.

Keep these in your back pocket while you’re in the trenches, improving tools, making process decisions, and getting lost in the weeds. They should be your guiding light as an executive, product owner, manager, engineer, or tester in the world of software development.

 
4
Kudos
 
4
Kudos

Now read this

ReadyTalk Pipeline DSL

If you’ve used Jenkins for any amount of time you might like its configurability and extensiblity but also understand that this flexibility poses serious drawbacks to his continued use. I feel as though Jenkins suffers mostly from a lack... Continue →