Agile x Waterfall

As you may know there are 3 mainly different approaches when talking about software development: Agile, Waterfall and both of them mixed up.
The first opportunity I had, it was to work with Waterfall model. It was a medium project and the complexity of documentations took all the time and the code wasn't so good. After gaining some experience I could realize that Waterfall is really good for projects with well defined rules and a lot of contracts. It takes a long time to be finished, believe me.

This year I had a new opportunity, to start to work in a mixed up project, it means: Agile + Waterfall.
Mixed projects are based on analysis, architecture, design, etc supported by Agile methodology, including interactions and minimal deliveries by functionalities.
You must be asking about my intention while writing this post. All I wanna pass is that if you're starting a new project for minor customers, Agile is a good option, because you can focus on development and delivering mininal packages of functionalities according to costumer's need, many times based on priority. I think it's important because you don't need to create a lot of documentations. This kind of formality are normally a requirement for large costumers, institutions, government among others. All you have to do is to focus on development

You can go to Google and check some of these words: Lean, Scrum  and XP (Extreme Programming) for example.

That's the experience I'm living these days. What do you think?