"The Information Systems Development Methodology (ISDM) is designed to provide a consistent, repeatable process for developing systems. By referencing, utilizing and applying the techniques within this methodology, development teams have a standard framework necessary to efficiently and effectively scope a project, conduct analysis, define and design the solution, create the system modules and evaluate the system after its implementation."

"customer needs analysis
scope definition
requirements analysis
design
development
integration/test/acceptance
implementation-deployment"

Here is some stuff ...

http://www.myfloridacfo.com/division/dis/isdm/#.VTlLdPD-kyl 

To be practical, and to be able to estimate well, one needs to bear in mind the history, the ethos and the existing expertise available to the project.  Yes, some methodologies are better for high-risk vs low-risk projects, or for winning an air-traffic control or defense contract vs a wedding planner solution.  But normally one will find it very difficult to use a different methodology per project unless one is assembling a new team per project and the business is for some reason open to that kind of change from project to project.

In my experience, one needs to understand of a couple of methodologies as 'cook-book'; but in understanding its tools and techniques, bring your toolbox of methods and techniques and create a (self checking) methodology that fits with the project and the team involved.