Please login or join to subscribe to this thread
DevOps is not predicated on agile/adaptive lifecycles. It can improve the efficiency and effectiveness of value delivery to any type of lifecycle.
DevOps is a new buzzword created to name the same problem some organizations are trying to solve from 1956. That problem is created mainly for the lack of Configuration Management process. So, as Kiron stated above, there is not reference in DevOps to Agile environments. I am in charge of implementing DevOps. I was the only person in my actual work place that from the very begining said: if you do not consider configuration management, if you do not consider quality (assurance and control) then forget about to implement DevOps. Thanks God or any other force that Governs the Universe, no matter that, I am still working in the same place......
Waterfall projects have a predefined schedule for development, deployment, testing and implementation phases. Incorporating DevOps model in waterfall approach can help speed up the deployment, testing and implementation by integrating them into one phase.
- A few pilot waterfall projects with low or medium complexity can be identified which will use the DevOps model.
- Instead of 3 different teams supporting the phases a few team members with necessary cross - technical skills can team up with the developers to build, deploy and test the application/service/platform in minimum time and in an efficient way.
- It will help to identify critical defects sooner and fixing them faster thereby reducing the shipping time of the product which adheres to the quality requirement of the product/project.
- Once the pilot projects are implemented a detailed comparison and analysis with other similar waterfall project results can help determine the benefits, risks and disadvantages of incorporating DevOps.
DevOps builds alignment between Dev & Ops teams. So be it Waterfall / Agile / Hybrid projects, DevOps can fit in anywhere. The culture of collaborative responsibility has to be built among various teams who work in developing / maintaining the product/project/service.
Now DevSecOps is also being practised for working together with Security teams as well.
I have a slightly contrary view to my above senior colleagues. Devops will give you control on your deployment and ops pieces for any project hitting your production or UAT environment. Though I am coming from the Agile background, initial 10 years of my experience are from the waterfall so I can relate with your pain.
My simple but a bit longer answer to this. You may not extract the best value out of deploying DevOps in a waterfall setup,. Wait for it.. I have relevant points to state this.
1. As your waterfall is taking months to navigate through each phase, the automation of the CI / CD to enable DevOps will not be fully optimized.
2. Only when the testing stage is reached and you are deploying your code to SIT / UAT / PROD environments, the CI CD will play the role then.
3. This will ensure you have the right build going in for testing and no monkey business is conducted on an existing build, like all manual effort to prepare a build is now covered under automated CI/CD, this saves you a lot of headaches
4. but if your projects are long and each of the phases run into 6-8 months of effort then DevOps is not your way to go. I agree with Sergio, that you can patch your process by a simple and effective configuration management or versioning control system and you're done.
Please login or join to reply