I disagree with Peter on projectmanager.com blog, when he suggests only to use the common-sense, essentially meaning to re-invent the wheel every time. The project management methodologies do make a difference. Though there is no sure way to measure exactly how much does it affect, but it does. The reason why we cannot quantify it is because all projects are different with different levels of uncertainty. Methodologies provide us a template to follow but project to project tailoring might be required. Saving Changes...
PANKAJ KUMAR JOSHIGeneral Manager| Transrail Lighting LimitedNainital, Uttrakhand, India
Yes PM methodology works. It is working in a system which informs you when you forget any process. However it doesn't mean that one should not use his common sense and just blindly follow it. You should always invent new ways and your ways to execute project. Share your own experience and by this way you support to increase PM knowledge of society. Saving Changes...
m grayIndependent Professional PM| ND_I LimitedCalgary, Alberta, Canada
I'd reiterate the comments above, but to take the discussion one step further, I suggest that regardless of project size, a good risk management method will improve project success rates. Large projects will also benefit from a gate review process methodology. Use common sense to choose methodologies from the toolbox that suit the type and size of the project being delivered. Saving Changes...
Bala S DuvvuriProject Manager| ShellBangalore, Karnataka, India
Looking at the historical data and similar projects will always help for the success of the project.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I second the input of the gentlemen and specifically Suhail's. Methodologies could be used as guidelines and will be beneficial if used efficiently and effectively by tailoring them to the specific projects need and of course common sense and experience plays a fairly good role here.
From Construction Point of View, I find the below very important:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The problem here is: what project management methodologies? What PMI stated is not a methodology. So, the article fails to indicate that. All related to PMI statistics is not about methodologies is about the use of project management. Is not the same. Saving Changes...
Very rightly brought out by Sergio, PMI does not give any methodology at all, PMBOK is a framework which is just a structure or guideline which is generic in nature for project management practices. In light of these generic guideline by PMI or other sources, there exist many methodologies developed by a number of organizations which are being followed. IBM and ORACLE have their corporate guideline or methodology, at commercial level MPMM and many others have come up with their methodologies. Even PRINCE2 was established initially as a methodology which later grew into a structure or framework. Therefore PRINCE2 still has elements of a methodology. A framework is not very specific in nature and is generic guideline, where a methodology gives out steps to do a project. Saving Changes...
Has anyone actually found the main item he is referring to ""The Complete Collection of Project Management Statistics" in 2015 by Emily Bonnie? Without that it's pretty hard to comment on this article. Saving Changes...
Chintan Jariwala, PMP, CSMProject Manager, IT Business Analyst| Sailfin Technologies India Pvt LtdSurat, Gujarat, India
Project Management is important. Methodology is not. We never used a specific methodology in our projects. It has been always tailor made for every project based on the experience level of resources, time frame, cost etc. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
I'm curious, Chintan. If you don't have a methodology, what is it that you tailor? If you prefer, what is your starting point?
...
1 reply by Chintan Jariwala, PMP, CSM
Jan 21, 2016 1:05 AM
Chintan Jariwala, PMP, CSM
...
Steve, It's nothing new. In my org which is a technology consultant to Multi Billion Dollar BPO & Tech Giant, We generally work on Programs & I am one of the project managers in that. We, the Project Managers, are not the one who decides the Target Date & even resources level & quality.
With our limited authority on above factors, We initially start with Waterfall & start the Analysis phase where we analyse the requirement at hand. Mostly, We work with both Waterfall & Agile ( Scrum but not 100% ) in same project. If the requirement of the functionality is clear, We use Waterfall. If not, Agile ( Iteration 0 to elicit requirement & then sprints).
Community Champion
