Continuous Delivery is not just a pipeline
When sharing the last article about Story Mapping on LinkedIn, I wrote we should learn this technique before learning Jenkins.
It leads to my understanding of continuous delivery.
Years ago, when I was applying for a job, I got the question, “What is CI/CD/CD”. And the obvious answer was about the DevOps pipeline.
On the other hand, in 2010, together with my colleagues, we were deploying the new version of our desktop Delphi application manually through an FTP server 3 times a day.
When I compare daily manual FTP deployments to a fully automated CD Jenkins pipeline, which is being used to bring an application to the production environment every 2 weeks…
… I think we had better “continuous delivery” in our manual FTP scenario.
Let's create a quote:
"You can do continuous delivery without continuous delivery,
but also you may not do continuous delivery with continuous delivery."
That was the purpose of learning Story Mapping before learning Jenkins.
To deliver continuously, we must learn (among others) to slice the work first.
Still… it is a no-brainer to have an automated delivery pipeline.
We only need to differentiate the tooling from mindset and ways of working.