Methodologies vs techniques & tools
The term methodology is being bandied about by just about every software development vendor and consultant imaginable. You would be hard pressed to find a vendor who, in addition to their usual tool offering, doesn't promise a methodology to solve all of your development problems. But like many things in this industry, the terminology is getting sloppy and it is becoming apparent the true definition of methodology is being bastardized.
There are fundamentally two interpretations: as a term referring to the process; by which work is performed, and; as a term referring to a particular design technique. To truly understand methodologies; you must know the difference. METHODOLOGIES AS PROCESS MANAGEMENT and METHODOLOGY AS A DESIGN TECHNIQUE
METHODOLOGIES AS PROCESS MANAGEMENT: Methodology is defined as, a process which ends with the delivery of a product or a completely defined result. Under this perspective, a methodology defines the 5-W's; it defines WHO, is to perform WHAT work, WHEN, WHERE, and WHY. Here, a methodology defines the division of labor and synchronization of work effort. With this approach, the development effort is divided into smaller more manageable pieces.
METHODOLOGY AS A DESIGN TECHNIQUE: A methodology supported by the software design people defines HOW a particular task is to be performed. HOW to accomplish specific activities of work. From this context, the term methodology; is a misnomer which should be replaced by the term technique, a more apt description.
METHODOLOGY AS A DESIGN TECHNIQUE Techniques may differ from company to company, and there is not always a single way to perform a task. Improved techniques can mean realizing the same result with savings in time and money. The same is true in the information systems world. Whereas there are generic stages of work for designing and developing a system, there are a multitude of techniques for performing the work.
METHODOLOGY AS A DESIGN TECHNIQUE Productivity is not simply a matter of how fast a task can be performed, it's a matter of performing the right task at the right time. This is what underlies the concept of productivity. Whereas efficiency; concentrates on speed of delivery, effectiveness is concerned with doing the right thing at the right time; the two are not synonymous. There is nothing more unproductive than to build something efficiently that should never have been built in the first place. Zero percent effectiveness times 1000% efficiency equals zero productivity. PRODUCTIVITY = EFFECTIVENESS x EFFICIENCY
A true methodology addresses the effectiveness side of the equation (Who, What, When, Where, Why), and a technique addresses the efficiency side (How to). Whereas a methodology defines the work environment, the technique defines how the work is to be performed. The two are obviously complementary and one does not eliminate the need for the other. But comparing one with another is like comparing apples with oranges, they are simply not the same. PRODUCTIVITY = EFFECTIVENESS x EFFICIENCY
METHODOLOGY CRITERIA Since a methodology is critical to the success or failure of a development environment, it is important to be able to differentiate between a methodology, technique and tool. The generic properties of a methodology include: DEFINES THE STAGES OF WORK (a work breakdown structure normally consisting of phases, activities and tasks). The stages of work defines the 5-W's; (Who, What, When, Where, Why). The synchronization of work is needed to define direction and is provided by the precedent relationships between the various steps in the methodology. Defined duties and responsibilities provides insight for performing the work and methodology standardization improves communications between workers.
METHODOLOGY CRITERIA
MEASURABLE - The stages of work can be evaluated in terms of how long it takes to perform them and how much they cost to perform. Further, criteria is provided to substantiate completion of deliverables thereby assuring the development of a quality product.
TECHNIQUE AND TOOL INDEPENDENT - various techniques and tools can be deployed as required.
PROJECT MANAGEMENT INDEPENDENT - can work with or without a Project Management system. For example, an Assembly Line can still function without Production Control, but not vice versa. If the methodology you are evaluating does not match this simple criteria, it is not a methodology and probably some form of technique.
TYPES OF METHODOLOGIES
Of the process management methodologies, there are fundamentally three types: LINEAR WATERFALL; SPIRAL DEVELOPMENT and PRODUCT DEVELOPMENT
LINEAR WATERFALL; METHODOLOGY Sometimes referred to as Life Cycle - this is perhaps the best known of the methodologies. Various interpretations of this approach have been published for several years, both commercially and public domain. Fundamentally, it a sequential process where the design of an application moves from the general to the specific; for example: The problem with this approach has been its orientation towards computer software and not on total systems. But the biggest pitfall has been its sequential orientation which tends to prohibit parallel development.
If you like this article, you can continue reading at https://www.slideshare.net/orlandomoreno/methodologies-vs-techniques-tools