Development process  is used for all of software projects  because it shows you a road for development. It can be used in different forms such as Pair-Programming , RUP , SCRUM , .... you always use it ,maybe you don't think about it but you do it unconsciously, even you can customize it for yourself (i recommend ) , and that is more important which documents i should create and archive.

But which of those is more suitable !? in my point of view there are infinite aspects which lead to choose one instead of others, or make your road-map among them, so it doesn't mean it is Bad, that is Good or this is Excellent , it means this process is more suitable for you instead of others.



I am going to write some these aspects which can help you to choose your best one , or it is better :
(all of following items are my personal experience in software development  , so maybe you don't believe them)

Project size
Project cost ( applicable )
Project time ( dead-line )
Project domain model complexity
Project architecture complexity
Team size
Team knowledge on domain
Team knowledge on architecture
Team arrangement
Distribution of individual skills
Team knowledge on your development process
Stakeholder knowledge on domain
Volume/Frequency of change requirements
Project will be continued or not !?
...
And let team understand why development process or some documents are important.