Whenever any CIO, CTO wants to introduce DevOps practices within organisation, they face lots of push backs and low adoption rate. DevOps is not about setting up all the tools and stitching them together in one go. Its cultural shift for all. Every one from business to development to operations needs to understand ROI and agree on adoption.
We suggest Start slow from each level and Go Long.
Steps to take for DevOps Readiness:
- Automate repetitive tasks with small scripts first rather than putting Bulky tools. Examples for small product teams:
- Developers can first Implement Git pre-commit hooks for static code analysis locally
- Developers can implement Git Post-commit hooks for Build generation.
- Operations can write shell scripts to rake git pull on servers if they are doing manually every time.
- Operations can write shell scripts to monitor infra and send email notifications to relevant team members.
- QA can implement automated test scripts for Load and Security Tests.
- Everyone should look for any possibility for quick automations tasks that reduces repetitive tasks.
- Start introducing tools best fit for job on all levels that costs nothing initially. Examples:
- Static code analysis can be done with SonarQube, it’s free and quick to setup.
- Peer code review can be done with ReviewBoard, it’s open source.
- You can still all pieces of DevOps and build Pipelines with Jenkins
- Jenkins have lots of ready to use plugins for quick integrations like, AWS Code Deploy, if you are using AWS Infrastructure Code Deploy is free to use.
- Separate Dev, QA and Production environments to avoid any not tested deployments.
- Implement tools like Nagios and GreyLogs for monitoring.
This will give you start of your DevOps journey. For DevOps consultancy or end-to-end implementation, feel free to contact us.