Is using one methology for your work environment a good idea? 

Personnally, it depends on your environment – meaning the industry, company culture, people and most of all the tools one uses.  Having to work for Corporations, medium and startup companies,  I’ve found that today’s successful PMs need a belt of methologies to get projects completed on time.  Just like a mechanic or carpenter, the tools they use to fix and/or make the product really depends on whether or not they have the right tools or not. 

By combing or “customizing” some of the methologies out there such as Agile and  Six Sigm, the  SDLC process, a good PM can achieve  great results with  quality product output fairly rapidly.  Personally, I like Agile because aside from questioning everything, you tend to break things down into components for rapid deployments.  Yes, you don’t get all the quality that one hopes  for;  however, the potential erros are eaiser to manage as oppose to building something bigger at one shot and trying to figure out where to start debugging the codewhen it goes into production.

To many times, PMs try to plan for one big implementation and doing so just leads to failure through my eyes.  The art of a PM is to try to understand the business model and the product being built as much as possible. Having a great technical team with communication skills also helps because they’re able to point out issues or concerns as they see them come about.  

Yes, there are other components as well, but all i’m saying is that PMs should try to learn as many methologies as possible, assess your current project and environment, and put the best one in play.