no need for meetings, PMs or frameworks if it's a small shop
Waterfall development is the most appropriate way to develop software, most of the times. CRUDs developed by startups don't change requirements often, their clueless managers that change their minds as they get to understand what they should already know before starting the project.
This is only true if you work on unimportant projects where delays and failures are acceptable.
And SCRUM only for important project you can release crap full of bugs and wrong use cases every 2 weeks.
Please, point out non-trivial successful (delivered on time, on budget, and with all initially planned features) Waterfall projects that did not modify Waterfall into something sensible (that is, incorporated feedback loops and probably executed as a series of iterations rather than one 5-year long project with hard distinctions between each phase).
Most people are incompetent at what they do. That includes managers at software companies.