Is Prince2 an Agile model or a traditional project management model?

I see PRINCE2 as a subset of PMI, I've worked with both.

PRINCE2 is a traditional project management model, it's sequential. The separation that exist between themes, principles and processes creates no iterative nor incremental behaviour at all. In fact, none of the different stages the project goes through has a resemblance to Agile, they are all sequential, too.

The repetition of some phases does not make it Agile as they only happen because they divide the work to be done in different subphases but there is no iteration, no incremental approach, nor any customer interaction happens until the end.

The documents (work packages, project mandate, etc.) that are produced on each phase are literally the same standard "deliverables" that can be found in all other waterfall practices, like PMI for example.

Themes, principles and processes are interlinked but only to act like a way of enriching each other during the phases the project goes through, working as a way to explain how to tackle the different procedures that will happen and which are the different documents or artifacts to produce on each stage but there is no sense of incremental development of any type.

Stage after stage the product is generated and finally, testing and acceptation by the client happens. A very waterfall approach. Therefore, the PRINCE2 model suffers the same problems that any other waterfall approach would do: problems are found too late and they're very difficult to be amended without redoing long parts of the work, etc.

[250 words]