from inception to production
play

From Inception to Production A Continuous Delivery Story - Ian - PowerPoint PPT Presentation

From Inception to Production A Continuous Delivery Story - Ian Randall Fearlessly*, continuously delivering value * but not irresponsibly pushpay https://www.nzx.com/companies/PPH/announcements/299761 Tools People & PRactices Just


  1. From Inception to Production A Continuous Delivery Story - Ian Randall

  2. Fearlessly*, continuously delivering value * but not irresponsibly

  3. pushpay https://www.nzx.com/companies/PPH/announcements/299761

  4. Tools People & PRactices Just culture & blameless postmortems

  5. Our journey begins...

  6. Why? Shared vision over the value to the business

  7. Who? Product Qa Dev

  8. You can’t test the quality in at the end

  9. Building a feature Dev Qa “How will I Build this thing?” “How will I break this thing?”

  10. Building a larger feature Long-lived feature feature switches branches

  11. The delta

  12. Building a larger feature Long-lived feature feature switches branches ● Delta gets too big ● Small deltas ● No feedback ● Regular feedback ● DRY code ● Technical debt

  13. Feature switches Configuration per environment

  14. Feature switches URL manipulation to toggle switches on/off in QA (DO NOT do this in Production)

  15. Feature switches - Deliver daily increments of (non-running) code - Light up a slice of feature - Measure - Re-think road-map to complete feature

  16. WOMM

  17. Code review - Every line of code gets reviewed - Code must be reviewed and WOMMed before merging. - “Roll Forwards To Victory”

  18. Code review Do Don’t Validate approach Be rude. Performance, Security, Operability Seriously, don’t be rude. Cohesion, Coupling and Connascence Sweat the small stuff, like bracing, spaces Be honest and positive.

  19. Cross-pollination - Someone else does it all again! - Pollinator is not (necessarily) involved with feature

  20. Just culture http://sidneydekker.com/just-culture/

  21. Just culture Retributive - clarity around acceptable vs unacceptable behaviour Restorative - “safe-to-fail”

  22. Fear of breaking things will paralyze your organization.

  23. Toyota’s five whys

  24. Blameless Postmortems https://codeascraft.com/2012/05/22/blameless-postmortems/

  25. When? - Opportunity to learn - Something that impacted production - Near-miss

  26. How? - Asynchronously in a wiki - Coordinated in Slack channel #morgue - Co-ordinated by person(s) closest to the incident

  27. What? - Scenario and impact - Timeline - Discussion - Mitigations

  28. Fearlessly*, continuously delivering value * but not irresponsibly

  29. This shit be hard, yo. - Ian randall, 2017 @kiwipom

Recommend


More recommend