The thing is that Data department have essentially swallowed the former analytics departments, and many people who have done business intelligence/business analytics now seem to fall into the data science umbrella.
This is part of the reason the term now refers to different things depending on who you talk to or which team they are a part of. Look at job postings, its extremely difficult to understand what the actual job entails these days.
It's an extension of lean manufacturing to software development, where the focus is on continuously pushing tiny packets of functionality to customers (instead of occasionally pushing huge bundles of features), to react quicker to changing demand and mistaken assumptions.
It is in no way "a sysadmin with scripting skills" -- the name for which, is, by the way, just sysadmin. Sysadmins know how to write Perl and shell and Python and have done so since forever.
> ...the name for which, is, by the way, just sysadmin
No, because some time in the past "IT support" (you know, the guys setting up Windows and Wi-Fi routers in your office) got upgraded in name to "sysadmins", and so the old "sysadmins" who knew Unix and how to code some Perl needed a new, untarnished name. Hence, "DevOps".
Fun times trying to get code you didn't write to compile without knowing any context.
Anyways, that sort of turned me off trying to move into programming and so I went back to mechanical engineering after less than a year. Maybe I should have stuck it out longer.
(In the same way that "DevOps" is just a fancy name for a "sysadmin with some light scripting skills".)