Minimum-CD
Adding reference to work in small batches
In some way, for beginner people and organizzation that come from a non agile practice /mindset, is not clear that working in small batches, (using for example user stories) is a foundation practice to get CD work.
This is also the first way of DevOps : system Thinking and flow: without working in small batches we can't have flow, and we can't have the fully advantages of Continuous Delivery.
This misunderstanding, is something I was on, when I started our devOps / CD transformation, and is something that I still struggle to make my colleagues understand.
I agree. I've some ideas on how we can expand this, but I'd love to hear your suggestions as well.
Hi Bryan, thank you for the feedback.
I was thinking of adding a point in the CD list in the first position, something like this:
- Divide work in small batches to Feed the pipeline in order to create a smoth and continuous flow of work
- Continuous integration
- The application pipeline is the only path to deploy to production.
- ....
adding a link to the words small batches to a paragraph that explain the concepts and goals behind it:
- why we need smal batches
- why we need flow
- some link to some on line resource that explain how to divide work in small batches (User story splitting).
This is my proposal, what do you think about? What is you idea?
Because we want to keep the core practices generic and "we are doing this yes/no", the idea I had was to include a Tips section under "Beyond the Basics" to add things like that so the "why" can be clear.
I see that references to work in small batches and commit at laest daily are in the definition of CI. That's OK , but I think it is important to high light it in some way in the main CD definition.
We should discuss how we can document recommendations that align with the practices but in another section to keep the main page concise.