The organising principles of agile are based around the needs of developers. So processes and systems are broken down into units of functionality and fed to development teams along a pipeline of delivery.
I meet them on a regular basis, tech-savvy teens who've been coding websites from an early age. They'll often seek my advice about breaking into the industry. Should they continue their studies or jump straight into the labour market? I usually tell them that ability trumps education and I don't put much faith on the current raft of tech degrees. So I'd prefer to see three years of experience than three years of study.
Every few weeks I see a discussion emerge that tries to dismiss the need for specialists in our industry, or refute their existence entirely. It usually goes along the lines of "I'm a [insert discipline] and I do my own [insert activity] so [insert specialism] is unnecessary or doesn't exist".
I meet a lot of in-house designers in the course of my travels and the same frustrations keep bubbling up - "how can I convince the company I work for to take my expertise seriously". It seems that companies have a pathology of hiring highly talented people but taking away the decision making abilities they need to do their job.
A lot of the discussions I have about our profession end with somebody saying "Well everything is design at the end of the day". This is a great way of ending a conversation when you're bored and have a bus to catch. It's the designers equivalent of Godwins law.
User research is an extremely powerful tool (or set of tools) for understanding customer needs and behaviours. As digital projects grow in size and complexity, the risk of building the wrong thing becomes an increasing danger. So it makes sense to spend a portion of your budget to ensure that you've done the due diligence and are investing wisely.