But there isn't one. I used to be rah-rah Agile/Scrum, but as time goes on I see plenty of issues with it as well. One of the most effective teams I have been on in my career used a waterfall approach. At the end of the day, I think the team matters far more than the development strategy (and that might be your problem too).

That being said, I would have a hard time recommending a waterfall approach today. I haven't seen anybody recommend doing that for years. The good parts of Agile are iterative development, prioritization, goal setting, teamwork, and customer input. I think you can incorporate most of those into a "waterfall-like" environment without calling it Agile and be just fine.