Managing Your Portfolio – Leaping those “Change” Moments

As PMO Portfolio, Programs, and Projects struggle to get the most out of their IT resources, capacity management and risk management issues essentially start rearing their heads once the portfolio is in the execution phase. …

Read the full story »
COMMUNICATION

Do you have the right tools to communicate well in your job?

JUSTCOMMIT

Don’t click here if you like to procrastinate.

METHODOLOGY

Too many methods. Do you know which method is right for your environment?

PROFESSIONALISM

Tips and general lessons learned for applying professionalism to your environment.

SOCIAL RESPONSIBILITY

The purpose of this category is to describe how you can use your Project Management skills to manage social responsibility.

Home » METHODOLOGY

Which methodology works best?

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

Personally, 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 start up companies,  I’ve found that today’s successful PMs need a belt of mythologies 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 mythologies 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 code when 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 mythologies as possible, assess your current project and environment, and put the best one in play.

Did you like this? Share it: