Project Management: Methodologies Vs. Standards
Most of the times I had conversations with mates and when it comes to the critical area of PM methodologies, we used to argue not just on picking the best methodology to manage a project as per to its circumstances but also when some guys over there are merging between the concepts of both methodology and a standard. So, here comes my testimony for history:
Generally, methodology is simply a set of various methods, processes and practices that are repeatedly carried out to deliver a project means some organized and explained steps which you can follow to manage a project from day one till the end. These steps are always described in depth to answer whatever question comes to your mind on which, how, who, and sometimes it may answer where as well. Your methodology makes your approach of the projects you undertake.
On the other hand, I may describe the standards as the knowledge proved to be the best practices in the industry in which the project belongs. Standards are the beam light that provides guidance through dark times of your project. Here we go, for me I used to stick to PMBOK standards, others may stick to PRINCE2, ITIIL or whatever it takes to get your project successfully delivered, not to forget if your employer has got rules within the company processes and procedures that may conflict in some areas to any of the above mentioned standards. But…
Should we all adopt the same methodology for all projects? From my own point of view, I don’t think this is the best way to go; imagine a small project where you decided to follow your favorite methodology which is complicated enough to manage a huge 10 years project, no one can claim it’s not right since methodologies were designed to manage any project regardless of its scale but imagine the time you may save if you managed such a project based on waterfall, while thinking of this please remember that time is money.
I still remember some discussions with colleagues when some of them are highly insist to stick to the same methodology regardless the project objectives, timeline or cost accounting for the control you have when you are playing in your own area of expert then they can enhance their efficiencies with their own approach and increase the chances of the project to success. However, it’s your own decision to make.
Coming Next: IT Project Management Methodologies, Pros and Cons
Posted on June 20, 2012, in Project Management and tagged Agile, ITIL, Methodology, PM, PMBOK, PRINCE2, project, Project Management, Standard. Bookmark the permalink. 1 Comment.
great post as usual
well, i believe that each project is unique somehow, for sure we should make use of our lessons learned. so the methodologies are not a set of certain blocks, but it must be flexible to accept changes and new styles of executing.
so we should think out of the box when it comes to the methodology and we should trust ourselves, this may inspire us to came up with a new methodology, why not?
i think this would be great for the team if they develop their own methodology based on their experience.
as for the standards, we can call it the points that we should earn to win the game according to the project scope, objectives, and constraints.
the project manager can follow, or can create a certain methodology in order to maintain a successful process to ensure that the outputs will meet the stakeholders’ standards.
thank you sooo much Karim for sharing your valuable experience.