I regularly see projects asking for experience in multiple different frameworks: React, WordPress, Laravel... but personally, I've trusted Drupal since 2009 and it has never let me down. my focus has led me to understand it better than if I had switched between several different tools to do the same job. 

when it comes to methodologies, however, that's a whole other story. 

Agile is the most adaptable method, the one stakeholders are more satisfied with, with faster incremental delivery, visibility, and feedback loops. Waterfall is the choice for stable and well-defined requirements; for when work is either heavily regulated or heavy on documentation (or both); with fixed scope and constraints; and for systems that rely heavily on hardware, with costly changes. 

but here's the thing, though: which method is strictly enforced, and which one is more loosely adopted? the answer is neither. almost every development team goes with a hybrid of both, typically asking for incremental changes that lead to a complete product with a release date. 

I've been there many times. and, almost always, it was down to team maturity, product certainty, and governance. 

oh and ITIL? done that too. I was part of a team with a 100% SLA in the Pharma sector. needless to say, we never gave the FDA any cause for trouble. 

my advice for you: understand where you are, what's your goal, and how to get there. once you do, plan ahead — but understand planning means you'll find out exactly how things are not going to go. 

are you ready to take the first step?