[Maria_micro]

Moving towards a culture of CI/CD means that your team needs to move toward agility, so implementing agile methodology will help your team move faster into the mindset of CI/CD. Of course the tooling to use is the most important part. Our tool Microtica (http://microtica.com) can help you automate the entire software delivery process. Try it out and let me know what you think.

[danieka]

This feels backward, I don’t get how CI/CD is dependant on agile.

CI/CD can enable some agile practices for sure, but CI/CD provides a lot of value without implementing any of the agile methodologies. But having CI makes it easier to practice TDD and enforce coding standards. And having a test environment running the latest code should tighten the feedback loop between developer and stakeholder. These are good things no matter how you organise your work. So start with a CI/CD pipeline and then go from there. You may or may not want to adopted ideas from the agile toolbox.

Ps. This isn’t directed at you Maria_micro, more at the implied agile methodologies. “I saw the greatest minds of my generation destroyed by [grooming meetings]”.

[Maria_micro]

True story! But the problem i see here is a bad implementation of agile that unfortunately a majority of teams have. That's why they are stuck on meetings forever and ever. Been there done that :) Agile practices (the real ones) are similar to DevOps ones, and CI/CD is a major part of them. Automation will bring you far along.

[danieka]

Also, don’t use Github Actions. They lowered the amount of free minutes and the developer experience is inferior to CircleCI or even Jenkins.

[hvgoldie]

thank you!