Skip to main content

Difference between Framework and Methodology

Difference between Framework and Methodology

Definition of methodology
The Treasury Enterprise Architecture Framework defines a methodology as:
"A documented approach for performing activities in a coherent, consistent, accountable, and repeatable manner."

The definition of methodology in oxford dictionary is “A system of methods used in a particular area of study or activity” which is still confusing because it still defines methodology as methods.

I found a better definition in Cambridge dictionary, which is “ a system of ways of doing, teaching, or studying something”. In other words, it means that a methodology is a systematic way of doing something.

Now as you can see the term is made of two parts. Method and ology and as we know any word ends with “ology” means a subject of study or; a branch of knowledge. Therefore, by knowing the meaning of method we can easily understand term methodology

Method definition in oxford dictionary is” A particular procedure for accomplishing or approaching something, especially a systematic or established one” so based on that we can define methodology as the knowledge of procedures or systematic ways of doing something. So it must be systematic and follows procedures.




Definition of framework



The Federal Enterprise Architecture Framework defines a framework as:
"A logical structure for classifying and organizing complex information."
Now let’s move to the term Framework. The term came from “frame (n.) + work (n.)” which was used first in 1640s. Oxford defines framework as “A basic structure underlying a system, concept, or text”.

Framework provides us with a guideline or frame that we can work under.
Generally, within the software lifecycle realm, a framework is a picture or a model that guides you to understand which artefacts you should produce when.  It doesn't tell you what to do though.  For example, typically the waterfall framework begins with analysis as the first stage of software development.  But it doesn't tell you how to do that analysis.  Even if the framework is detailed enough to specify the template you should use, it won't tell you how to populate the template.  Often though, a framework won't go into that much detail, giving you lots of flexibility to choose how you're going to do that stage.


Difference

so let’s put this understanding in the context of project management. A methodology is much more prescriptive, it should tell us what steps to take, in what order and how to perform those steps but, most importantly, the reasons ‘why’ those steps should be taken, in particular order.”
Methodology has certain way of doing something like a systematic process and in order to get the required results you need to follow these steps in the methodology. Disadvantage of methodology is the limitation it has for any innovation or creativity since you need to follow pre-defined steps and procedures but at the same time it provides consistency
On the other hand, a framework allows you to be loose and flexible; it provides enough room for creativity. But at the same time, it has some level of ambiguity inherited in it, because in framework, you are not guided through specific steps or process to produce a certain result instead you are left to find your own way through.
A framework is a general guideline that an organization can adopt, it could include many components. For example, PMBOK guide presents processes and knowledge areas and offers guidelines on how to develop a scope statement, communication plan …etc but you do not have to do everything mentioned in the PMBOK for each project, it’s like a guideline for you to select only the parts that you feel will help you to manage your project.
Now after we have a better understanding of framework and methodology, the question is which one is better?
I believe that if you are working for a small organization and managing small scaled projects or working in creative industry, it’s better to adopt a framework which provides room for creativity. But if you are working for large organizations and managing large scaled projects it makes more sense to adopt a methodology to be used for all projects. Because if large organization has a framework only to guide its employees, the employees will inevitably make different choices although they are using the same framework and there will be definitely a lack of consistency and poor monitoring procedures.
A good example of a methodology is PRINCE2 and for framework is PMBOK.

x
Labels:

Comments

Post a Comment

Popular posts from this blog

Difference between Risk Mitigation & Contingency Plan

Difference between Risk Mitigation & Contingency Plan Every risk based on score, both Mitigation & Contingency plans are prepared Risk Mitigation Plan Risk Contingency Plan Planning of identifying  actions which should take in advance irrespective of, risk is occurred or not. Plan actions and monitor through some certain warning signs. These actions are taken only the risk occurs. spend time and money in advance for the given risk condition Not spend time or money in advance, but keep them ready, and invest them when needed By applying a mitigation plan, chances of occurrences might reduce, risk score can reduce etc., Applying of contingency plan, will not change the probability or impact of the current risk, but plan to control the impact as risk event looks like occurring. This works as the first level of defense for the high exposure risks This works as a fallback plan for the high exposure risks.
Post a Comment
Read more

Process Areas - CMMi DEV Vs SVC

Process Areas - CMMi DEV Vs SVC CMMi Dev CMMi Svc CMMi DEV + SVC 1 CM - Configuration Management CM - Configuration Management CM - Configuration Management 2 MA - Measurement and Analysis MA - Measurement and Analysis MA - Measurement and Analysis 3 REQM - Requirements Management REQM - Requirements Management REQM - Requirements Management 4 SAM - Supplier Agreement Management SAM - Supplier Agreement Management SAM - Supplier Agreement Management 5 DAR - Decision Analysis and Resolution DAR - Decision Analysis and Resolution DAR - Decision Analysis and Resolution 6 OPD - Organizational Process Definition OPD - Organizational Process Definition OPD - Organizational Process Definition 7 OPF - Organizational Process Focus OPF - Organizational Process Focus OPF - Organizational Process Focus 8 OT - Organizational Training OT - Organizational Training OT - Organizational Training 9 RSKM - Risk Management RSKM - Risk Management RSKM - Risk Management 10 PMC - Project Moni...
Post a Comment
Read more

CMMi Generic Goals & Practices

CMMi Generic Goals & Practices Overview This section describes in detail all the generic goals and generic practices of CMMI—model components that directly address process institutionalization. As you address each process area, refer to this section for the details of all generic practices. Generic practice elaborations appear after generic practices to provide guidance on how the generic practice can be applied uniquely to process areas. Process Institutionalization Institutionalization  is an important concept in process improvement. When mentioned in the generic goal and generic practice descriptions, institutionalization implies that the process is ingrained in the way the work is performed and there is commitment and consistency to performing (i.e., executing) the process. An institutionalized process is more likely to be retained during times of stress. When the requirements and objectives for the process change, however, the implementation of the...
Post a Comment
Read more