Convention Driven Design : benefits to Offer

This article could have the title "Benefits of Convention-driven over a configuration-driven design", but I want to keep it simple as Configuration driven design has already provided a lot of facilities to the developers and software architects. I'm not driving my thoughts to ignore the facilities of a Configuration Driven Design, rather I'm just trying to list a few of the benefits that I found useful while working with Convention Driven Design:

• I found it easier to jump-start with frameworks those follows Convention Driven Design.
• Reduce initial efforts of developers while starting coding with it.
• Code seems to be self explanatory. E.g. Suppose for ASP.Net MVC the name of the controller & method can be found quite easily from the URL.
• Convention helps the developer to keep the code clean. E.g. Developers do not need to decide where to keep the View code and where to keep the Controller. Its already decided by the convention and developers get rid of checking the mapping of location and the URL.
• Managing and Refactoring of Code is Easier.