I suppose they could call it Dev Ops but then you'd get all these validation errors from lame systems so then there'd be a fight between the C crown wanted dev_ops, the wev developer crowd wanting dev-ops, VB guys wanting DEV_OPS, the SQL crowd chanting for [Dev Ops] and the C# guys pushing for devOps.
You're never going to win.
Now shall we debate the term "Internet of Things"? I'll need something stronger in my glass if we do.
I have no idea how it is in the rest of the world, but here at the company I work at, if you have a IT related problem, you fix it yourself. If it requires an IT professional (for, lets say a password) you try to live with it. Yes, for any IT related problems to get resolved there is a long, very long waiting period. When you do get service, you better hope that the issue can be resolved immediately, otherwise you fall into the hole of trying to get this IT person helping you with your problem to complete what he started.
"Program testing can be used to show the presence of bugs, but never to show their absence."
When I say that there's no such thing as a DevOps team is in the sense that you don't add a DevOps team to your existing team; instead, you change the culture of your existing team in order to go from a group-of-people-sitting-in-the-same-room to a Team.
Regarding the name... yeah, it's far from clear; sounds better than SCRUM tho
The phrasing of the question make it effectively a loaded one. I seriously doubt that many people who responded are genuinely DevOps, it is more likely they want to identify with phrases like "You're IT Special Forces".