Thanks Stephane. Most interesting. Although it seems to be a very negatively written blog, one wonders what it is trying to prove. Two whole sections devoted to challenges and failure, yet little about the benefits that projects achieve!
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Here I am again because it is a very interesting discussion. I am in the line with Chintan and Suhail. One thing is that we use method and methodology word as the same but it is not the same. So, we need to talk about method. A method is a way to do things. So, we allways have a method. It could be defined formally or informarly, but we allways have a method. Suhail has pointed out very well the diferences and Chintan has pointed out the critical item. Project management, as all of us know, is tis the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. So, I fully agree with Chintian on the basic that we allways will follow a method, formal or informal, to do things. And associated with the method is the life cycle which is the way all method steps are chaining. Saving Changes...
Thanks Stephane. Most interesting. Although it seems to be a very negatively written blog, one wonders what it is trying to prove. Two whole sections devoted to challenges and failure, yet little about the benefits that projects achieve! Saving Changes...
I disagree with Chintan that Methodology is not important. Whether you are following a particular methodology or not, before you get into the actual project work, you always need to have a mechanism, which you said you tailor for every project. This is adhoc project management and will give rise to accidental project managers. The day you start organizing, you will start developing a methodology. I still persist that it is not necessary that you follow a particular generic methodology, you can create your own and then tailor it from project to project. But with no methodology at all, what are you tailoring from project to project?
...
2 replies by Chintan Jariwala, PMP, CSM and Rami Kaibni
Jan 20, 2016 12:21 PM
Rami Kaibni
...
I totally agree with you Suhail for example in Construction, you can't start the execution if you do not have construction methodologies in place which are called: Method Statements.
Jan 21, 2016 1:11 AM
Chintan Jariwala, PMP, CSM
...
Suhail, It depends in the nature of the work you do. In our case. What you see as an Accidental Project Management is Agile for me. I tend to bend my rules as per the situation & scenario. I follow the Project Management concepts religiously but not Project Management methodology in the same way.
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Jan 20, 2016 11:18 AM
Replying to Suhail Iqbal
...
I disagree with Chintan that Methodology is not important. Whether you are following a particular methodology or not, before you get into the actual project work, you always need to have a mechanism, which you said you tailor for every project. This is adhoc project management and will give rise to accidental project managers. The day you start organizing, you will start developing a methodology. I still persist that it is not necessary that you follow a particular generic methodology, you can create your own and then tailor it from project to project. But with no methodology at all, what are you tailoring from project to project?
I totally agree with you Suhail for example in Construction, you can't start the execution if you do not have construction methodologies in place which are called: Method Statements. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
I fully support Chintan statement and let me explain what. Something which is most of the time missing is the organizational life cycle phase where the organization is right now. So, if you are iniside the gowth phase, there is not reason to define a method but it is critical to use project management to achieve the objectives. The organization life cycle is something that most of the people forgot and then fail when try to implement something. For example a PMO. Saving Changes...
Sergio, I understand you are looking at the statement from the definition of method, methodology and practices. But if Chintan means what he is writing, then he is not correct. If he means a method, then I tend to agree with you. Saving Changes...
Chintan Jariwala, PMP, CSMProject Manager, IT Business Analyst| Sailfin Technologies India Pvt LtdSurat, Gujarat, India
Jan 20, 2016 7:17 AM
Replying to Stéphane Parent
...
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?
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). Saving Changes...
Chintan Jariwala, PMP, CSMProject Manager, IT Business Analyst| Sailfin Technologies India Pvt LtdSurat, Gujarat, India
Jan 20, 2016 11:18 AM
Replying to Suhail Iqbal
...
I disagree with Chintan that Methodology is not important. Whether you are following a particular methodology or not, before you get into the actual project work, you always need to have a mechanism, which you said you tailor for every project. This is adhoc project management and will give rise to accidental project managers. The day you start organizing, you will start developing a methodology. I still persist that it is not necessary that you follow a particular generic methodology, you can create your own and then tailor it from project to project. But with no methodology at all, what are you tailoring from project to project?
Suhail, It depends in the nature of the work you do. In our case. What you see as an Accidental Project Management is Agile for me. I tend to bend my rules as per the situation & scenario. I follow the Project Management concepts religiously but not Project Management methodology in the same way. Saving Changes...
That is the problem Chintan. The thing you mean by methodology is not a methodology. When I say methodology I do not mean PMBOK because it is not a methodology but a framework. You actually have a flexible methodology which allows you to pick Agile for some projects, maybe waterfall for others. You are following your own methodology and within that methodology your methods differs. Kindly revise your concepts about a methodology, because you are calling something else by this name. Saving Changes...
Community Champion
