39. 39
@ClareMacraeUK@ClareMacraeUK
Know the objections
• Have advocated more frequent releases for years
• So I knew all our “it’s impossible” reasons
• Invaluable for planning change
• Invaluable for reassuring those most worried
42. 42
@ClareMacraeUK@ClareMacraeUK
Meet all the teams
• State the Goal: “Make Releases Boring”
• Explain, explain, explain
• Reassurance - it will be OK, it’s not new!
• Feature toggles - only release what's ready
44. 44
@ClareMacraeUK@ClareMacraeUK
Redefine Releases
• From When we fix bugs, finish features & test
• To When we ship it
• Only has to be better than the last release
• Knowing that there's another release soon gives
confidence to focus on the few critical things
45. 45
@ClareMacraeUK@ClareMacraeUK
Change our Planning
• No-one to test feature? Then defer the feature!
• Critical that this first update release succeeded
• Each dev team reviewed changes made in code
that their products depends
• So manual testing efforts focused by risk
• First “extra” release after 2 months, not 3
50. 50
@ClareMacraeUK@ClareMacraeUK
Why did it work?
• All the development, testing and automation
changes were necessary to improve our releases
• But not sufficient
• I truly believe our critical missing link was the
belief & repeated expectation that we would
succeed
53. 53
@ClareMacraeUK@ClareMacraeUK
Lessons learned
• If you think you can achieve something, you will
• Put as little as possible into first changed release
• Use current tools
• Discover what most needs to be improved
54. 54
@ClareMacraeUK@ClareMacraeUK
Lessons learned
• How to turn around massive monolithic processes?
• Prioritise automated testing – however crude
• Showcase the benefits of innovations – working
things – to win support – don’t ask!
• Just do it!
• Or… Just get started!
55. 55
@ClareMacraeUK@ClareMacraeUK
References
• My Monolith is Melting – Meredith Williams,
PIPELINE 2015
– https://vimeo.com/123620783
• On Continuous Delivery for Client Software:
– http://timothyfitz.com/2009/03/09/cd-for-client-software/
• Feature Toggles:
– https://martinfowler.com/articles/feature-toggles.html
61. 61
@ClareMacraeUK@ClareMacraeUK
What next for us?
• Eliminate time-consuming steps
• More work to eliminate manual testing
• Automate the data export process regularly
• Make it quicker to install new builds
• Suggestions welcome!
62. 62
@ClareMacraeUK@ClareMacraeUK
That Mac challenge now?
• Would not matter when the problem was
discovered
• Just get a small team together to work on the
problem
• Could release an update to users at any time
• Would still need to fix it – just without the pressure
Notes de l'éditeur
Dr Olga Kennard, founder of Cambridge Crystallographic Data Centre (CCDC)
Speaking in 2015 about the organisation’s founding in 1965
The CCDC exists to curate and distribute crystal structures into a database
What I learned from this celebration is that some of our remaining Fortran software dates back to the late 1960s and early 1970s
More than 900,000 crystal structures in the database
Fundamentally, this is what our database stores:
The shapes of molecules (atom coordinates)
Information about hydrogen bonds and other close contacts
Symmetry information, to allow repeating lattices to be generated
Major Applications: research, education, designing of new medicines