Hey PavanKumar Belagatti ,
What I feel is, might be that guy got a wrong definition of DevOps and he is assuming that "DevOps only do deployments". As Siddarthan Sarumathi Pandian mentioned that waterfall is a top to bottom approach we might see very minimal deployment activity. DevOps hold the responsibility of quick shipment & monitoring of your environment and while facing challenges DevOps team should have to take a quick action on it. When i think from as a end user they don't want to wait for 1 day for a new fixes or a feature and that deliverable are very important. And sharing the quick fix is not the end of story we also have to keep an eye on that, if something went wrong what all action can be taken up , what's the role back plan and these all responsibilities DevOps usually takes up. Even in waterfall if you have given a build and you have monitor as well and issue happens in production immediate action is needed. Also we are getting everyday some new stuffs in terms of technology so the migration of new environment, technology scalibility, new operation plan also is now pitched by DevOps team and which is also applicable for Waterfall model this what i feel. If we will dig more there will be hell lot of evidence we will get why we can have DeOps for all the Software Model.