September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
Methodology is more broad than procedure. Procedure can be liken to a Work Breakdown Structure, Methodology has to do with the approach.
Thanks Chidiebere. It would be correct then, to say that the methodology is the collection of procedures?
First of all, methodology is incorrect used. The right word is method, not methodology. When you work with this type of things you have to take into account the architecture, where between layers you have to have low coupling and high cohesion. The architecture is as follows: think into a pyramid. In the basement, the approach (agile, lean, etc), on top the process model (predictive, adaptative, hybrid). on top process cycle based on model (waterfall, iterative, incremental, iterative-incremental, etc), on top the method based on process cyle (SDLC, V, Dsdm, Xp, etc) on top the tool to support the method . You can mix all this to create your own way to create products by running projects. Procedure is a point inside the process.
And to add to Sergio and Chidiebere's great feedback, PMI does not provide methods. Rather it provides a toolkit to help PMs tailor their approach to specific project contexts. PMOs or similar bodies can pick & choose options from within the PMBOK to construct a framework or method to support standardization of PM practices within their organizations.
What @Kiron stated above is critical to understand. Unfortunatelly most of the problems when organizations or people try to use the PMI way to run projects/programs are because people do not understand that.
I agree with Sergio
Processes and procedures are acted upon through method(s) within a given framework.
Please login or join to reply