Follow Scrum, Lean / Kanban, or eXtreme Programming to the letter, and let your team focus on the product.
This.
But invest in learning how to do it right. Hire agile coaches to help and listen to them. "Agile theater" helps no one and only breeds hostility to any attempt at improving the process.
Everything you're saying is good and valid points. And yes, the future may be bleak for Linux like the present is for Android.
But at the same time, I'm tapping out this very comment on a rooted phone with an unlockable bootloader without any of the Google apps and in fact running zero proprietary apps.
I think the option to use Linux the unenshittified way in which it was always intended to be used will be there for the foreseeable future the way it, quite frankly, still is for Android despite Google's best efforts at killing open mobile computing.
So, I'm not a recent convert to Linux. I've been using it pretty much exclusively for over 20 years now. And almost entirely Gentoo and Arch.
And I'll tell you... the Gentoo community is hard core. The sort of hard core that will not tolerate any enshittification. They'll make sure Gentoo stays pure.
And I'm not just talking about "free from corporate influence". If Gentoo announced that moving forward, only SystemD would be supported as an init system (and I don't think that's likely any time soon), a big part of the community would fork Gentoo and declare they could take OpenRC (or runit or whatever) away when they could pry it from their cold dead hands.
No matter what enshittified Linux distros come to exist in the future, that lifeline of purists will always provide a way to buck enshittification. And that's a lifeline that the Windows and Mac ecosystems don't have.
So, while I have little doubt that enshittified Linux distros will exist (indeed already do exist -- after all what is Android but enshittified Linux?), I think opting out of said enshittification will continue to be an option for the foreseeable future.
Two caveats:
I do think the likelihood is that the opting-out-of-enshittification option will largely skew toward a more technical/hacker/power-user sort of user base.
Some things that aren't exactly "Linux" (or within the Linux ecosystem) may well enshittify in ways that negatively impact Linux users. For instance, I'd imagine web standards will get more and more captured by corporate interests. WEI will probably return as a web standard. That sort of thing. And while that's not so much about Linux, it will affect Linux users.
How long is this kind of shit going to go on before we start having a serious conversation about making "limit dependencies" a widely-agreed-upon fundamental security practice? Right along with "validate your inputs" and "encrypt sensitive data" and such.
If you're a software engineer, memorizing an ASCII table (particularly the hex numbers of each character code) is definitely helpful. If for no other reason than so that you can read things that are randomly written in binary without having to consult a table.
Something not really otherwise terribly useful that nonetheless helped me keep my sanity: learn how to convert to base64 in your head. At work, we had really boring 8-hours-a-day training for a couple of weeks. To pass the time, I came up with random strings to base64 encode in my head. "Hat is 48 61 7a. The first six bits are 010010 which in base64 is an S. The next six bits would be 000110 which in base64 is G." Etc. I'd write down the base64 strings character by character as I derived them and then check my results for errors when I got back to my desk.
This.
But invest in learning how to do it right. Hire agile coaches to help and listen to them. "Agile theater" helps no one and only breeds hostility to any attempt at improving the process.