I don't exactly understand your criticism on best practices.
You seem to imply that UML or other project management software are considered best practices. I have never heard that. Or rather the opposite. Not using UML is currently considered as best practice.
Yeah I studied UML during uni. It took a long time to 'click' and when it did I learned some useful concepts from it. Only then did OOP really make sense.
However it's way too laborious using it for everything and it becomes a burden when things get complicated. For simple things it just doesn't really help because they're simple anyway.
As a learning tool I think it was great. In production? Well I use it every day. The book props up my keyboard on my desk which happens to be 2cm too low :)
UML done "right" is when you relegate it to simply being a shared vocabulary used when you have a need to communicate details, the same way "everyone" understands a basic flow chart.
Having a shared vocabulary is great.
Modelling everything out with it, on the other hand, is a nightmare.
It's usually government types (DoD, FDA) pushing for this stuff, and lots of it. The thinking appears to be, "The more the paperwork, the better the product".
You seem to imply that UML or other project management software are considered best practices. I have never heard that. Or rather the opposite. Not using UML is currently considered as best practice.
But maybe it depends who you ask.