Methodologies versus Techniques and Tools

"Having a Project Management system without a				effectively applied.TECHNIQUES, as mentioned,
methodology is like				represent ways for performing specific tasks
attaching a speedometer to an orange crate; it				("how to"). A variety of techniques may be used on
measures nothing."				the Assembly Line.
- Bryce's LawINTRODUCTIONThe term				Obviously, it would be counter-productive to use a
"methodology" is being bandied about by just about				technique at the wrong
every				time on the Assembly Line. This means the effective
software development vendor and consultant				use of techniques
imaginable. You would be				is dependent upon a defined Assembly Line.TOOLS
hard pressed to find a vendor who, in addition to their				implement techniques. Tools provide mechanical
usual tool				leverage for performing
offering, doesn't promise a methodology to solve all of				a specific task. In this sense, it is an extension of a
your development				technique, and like
problems. But like many things in this industry, the				the technique, tools must be deployed at the proper
terminology is				locations along the
getting sloppy and it is becoming apparent the true				Assembly Line. This is the reason why many
definition of				software engineering tools are failing;
"methodology" is being bastardized.IN THE				not because they are bad tools, but simply because
BEGINNINGThe term "methodology" became popular in				companies have not defined
information systems in the				their Assembly Lines (methodologies) and haven't
early 1970's, initially as a response to the question,				specified when the techniques
"What is it?" Milt				and tools are to be used.What this highlights is that a
Bryce first applied the term to systems development				methodology is the focal point within a
in 1971, to describe his				development environment. Without a defined
Information Systems Engineering process. Bryce				methodology, Project Management
referred to "methodology" as				will be ineffective, and design techniques and
a process which ends with the delivery of a product				software development tools
or a completely defined				will be misapplied. Productivity will be
result.Later on, during the structured programming				low.METHODOLOGY CRITERIASince a methodology
movement, a different				is critical to the success or failure of a
interpretation of the word emerged from software				development environment, it is important to be able to
gurus such as Yourdon,				differentiate
Gane/Sarson, Orr, Finklestein, Martin, Warnier/Orr, etc.				between a methodology, technique and tool. The
Instead of				generic properties of
describing the overall process by which development				a methodology include:
occurs, the structured				DEFINES THE STAGES OF WORK (a work
programming people began to use the term				breakdown structure normally
"methodology" to describe their				consisting of phases, activities and tasks). The stages
techniques for designing software (e., functional				of work
decomposition, data				defines the "5-W's" (Who, What, When, Where, Why).
driven design, object oriented design, etc.).				The synchronization
Consequently, software				of work is needed to define direction and is provided
development tools, which represent automated				by the precedent
extensions of these techniques,				relationships between the various steps in the
began to tout their products as "methodology"				methodology. Defined
enablers.This division in the use of the term				duties and responsibilities provides insight for
"methodology" is a major source				performing the work
of confusion to the industry. Not all "methodologies"				and methodology standardization improves
are created equally.				communications between workers.MEASURABLE -
There are fundamentally two interpretations: as a				The stages of work can be evaluated in terms of
term referring to the				how long
"process" by which work is performed, and; as a term				it takes to perform them and how much they cost to
referring to a				perform. Further,
particular design technique. To truly understand				criteria is provided to substantiate completion of
"methodologies" you				deliverables
must know the difference.METHODOLOGIES AS				thereby assuring the development of a quality
"PROCESS MANAGEMENT"We at MBA define a				product.TECHNIQUE AND TOOL INDEPENDENT -
methodology as, "a process which ends with the				various techniques and tools can be
delivery				deployed as required.PROJECT MANAGEMENT
of a product or a completely defined result." Under this				INDEPENDENT - can work with or without a Project
perspective,				Management system. For example, an Assembly Line
a methodology defines the "5-W's"; it defines WHO, is				can still function
to perform WHAT work,				without Production Control, but not vice versa.
WHEN, WHERE, and WHY. If this sounds like an				If the methodology you are evaluating does not match
engineering/manufacturing				this simple
process, it is. MBA contends information resources				criteria, it is not a methodology and probably some
can be designed and				form of technique.TYPES OF METHODOLOGIESOf
developed in the same manner as any other product.				the "process management" methodologies, there are
Here, a methodology				fundamentally
defines the division of labor and synchronization of				three types:LINEAR "WATERFALL"
work effort. With				METHODOLOGY (sometimes referred to as "Life
this approach, the development effort is divided into				Cycle") -
smaller more				this is perhaps the best known of the methodologies.
manageable pieces just as in an assembly line				Various interpretations
process. Construction				of this approach have been published for several
projects represent another example (e,g., shipbuilding,				years, both commercially and
office/home				public domain. Fundamentally, it a sequential process
construction, etc.), where the work is carefully divided				where the design of an
into stages with				application moves from the general to the specific; for
precedent relationships.METHODOLOGY AS A				example:1. FEASIBILITY STUDY
DESIGN TECHNIQUEAs opposed to the "5-W's"				2. DESIGN
interpretation by MBA, a methodology				3. PROGRAMMING
supported by the software design people defines				4. TESTING
HOW a particular task				5. REVIEWThe problem with this approach has been
is to be performed. For example, the forte of design				its orientation towards computer
techniques such				software and not on total systems. But the biggest
as "object oriented programming," "structured				pitfall has been its
programming," or "information				sequential orientation which tends to prohibit parallel
engineering" is on HOW to accomplish specific				development.SPIRAL DEVELOPMENT - this approach
activities of work. From				is based on the premise the development
this context, the term "methodology" is a misnomer				process is evolutionary in nature (which, in fact, it is).
which should be				The concept is
replaced by the term "technique," a more apt				to initially design a program, then add additional phases
description.Techniques may differ from company to				of work to
company, and there is not always				constantly revise the program to enhance its features.
a single way to perform a task. For example, in the				From a Project
automotive industry,				Management perspective, the problem with this
fenders have always been a part of the car, but they				approach is that the project
have not always been				never ends.PRODUCT DEVELOPMENT - as
attached the same way. Originally, fenders were				proposed by MBA, this approach uses elements of
bolted to the body of the				the other two methodologies, with the added nuance
car. Years later, an automotive worker welded the				of using a product
fender to the car. Today,				orientation as the basis for the development process.
welding robotics perform the task. The task, attaching				Under this approach,
the fender to the car,				a system is viewed as a product. Consequently, it can
hasn't changed, but the techniques to do it have.				be designed in the same
Improved techniques can				manner as any other product. For example, when a
mean realizing the same result with savings in time				product is being designed
and money.The same is true in the information				(such as an automobile), the overall assemblies are
systems world. Whereas there are				first designed (such as
generic stages of work for designing and developing				the body, chassis, engine, etc.). After this phase, each
a system, there are a				assembly is designed
multitude of techniques for performing the work. For				by teams of engineers who refine the design of each
example, there are				assembly into sub-assemblies
significant differences between "structured				and parts. All of this occurs as parallel phases. MBA
programming" and "object				advocates the same
oriented programming," yet the result is fundamentally				approach for systems development. An initial phase is
the same, the				used to design
development of an executable program. The				the architecture of the system, followed by
difference is the chosen approach				succeeding parallel phases to
of implementation (there are pros and cons for both				refine the design. This is the best approach for parallel
techniques). Whereas				development.INDUSTRIAL ENGINEERINGIn an
"Software Engineering" represents a phase of work in				engineering/manufacturing environment, the
a development project,				responsibility for
"structured programming" and "object oriented				defining the work environment is normally delegated to
programming" represent				an "Industrial
techniques that can be used to perform the				Engineer." It is the Industrial Engineer's responsibility to
phase.Does this mean there are overlaps or conflicts in				define the
the use of the				Assembly Line, the types of people and skill sets
different types of "methodologies"? Not quite. But to				required to perform the
appreciate the				work, and the deployment of techniques and tools to
difference, one must understand the concept of				be used on the
"Productivity" (as				Assembly Lines. Industrial Engineering is a recognized
we have discussed in other "PRIDE" Special Subject				profession in
Bulletins).PRODUCTIVITY = EFFECTIVENESS X				the engineering/manufacturing world. A comparable
EFFICIENCYProductivity is not simply a matter of how				position is required
fast a task can be performed,				in the information systems world.Unfortunately, most
it's a matter of performing the right task at the right				development methodologies purchased today are
time. This is what				evaluated by the wrong people. Quite often, the
underlies the concept of productivity. Whereas				evaluation of a methodology
"efficiency" concentrates				is delegated to programmers or technicians who are
on speed of delivery, "effectiveness" is concerned				more enamored with the
with doing the right				latest software design technique or tool than in
thing at the right time; the two are not synonymous.				defining a managed development
For example, performing				environment. This is like Henry Ford allowing the UAW
a weld using robotics may be a far more efficient				to invent the concept
means than performing the				of the Assembly Line. They simply have the wrong
task manually, but it is useless if you are welding the				perspective. Someone who
wrong thing. There				specializes in installing headlights doesn't necessarily
is nothing more unproductive than to build something				have the expertise to
efficiently that should				develop Assembly Lines. True, their input can be
never have been built in the first place. Zero percent				helpful when evaluating a
effectiveness				technique or a tool, but not for an overall development
times 1000% efficiency equals zero productivity.A true				environment. This is
methodology addresses the effectiveness side of the				one area where American businesses have
equation				abdicated complete control.CONCLUSIONThere are
(Who, What, When, Where, Why), and a technique				essentially two interpretations for the term
addresses the efficiency				"methodology" in
side (How to). Whereas a methodology defines the				the IT industry. One interpretation is as a disciplined
work environment, the				process for developing
technique defines how the work is to be performed.				information resources, from inception to conclusion.
The two are obviously				Another is as a technique
complementary and one does not eliminate the need				for performing a specific task of work. These are
for the other. But				subtle but significant
comparing one with another is like comparing apples				differences, particularly if a company is analyzing their
with oranges, they are				development
simply not the same.FACTORY CONCEPTWithin an				environment. As companies have learned, it is not
engineering/manufacturing facility you will typically find:				simply a matter of
An Assembly Line where products are developed in				purchasing the latest software engineering tool to
stages.Production Control monitoring the assembly line				overcome their productivity
for delays or				problems. Studies show such tools are failing to have
accelerations in production.Techniques for performing				an effect in this area,
work.Tools providing mechanical leverage.				primarily because they are being misapplied by the
These elements can be found in any development				users. People looking for
environment, including				programming tools to bring order out of chaos are
the IT world. What is interesting is the relationship				going to be sorely
between the elements:ASSEMBLY LINE - at the heart				disappointed. This is not their forte. Rather, they
of the factory is the Assembly Line process				represent an efficient
where products are developed in stages by workers				approach for implementing design techniques. The
with different skills				intent of a true methodology
for the different stages of work. In IT terminology, this				is to define the work environment, thereby providing
is the				the ability to effectively
"methodology."PRODUCTION CONTROL monitors				deploy tools and techniques. To implement a
the assembly line using dials and gauges.				methodology, a development
Production Control is not an entity by itself; it is totally				organization needs to reorient themselves into an
dependent on				"Information Factory"
the existence of the Assembly Line in order to				environment, where systems and software (products)
measure performance.				are developed in the
In IT terminology, this is Project Management.				same manner as any other engineering/manufacturing
However, this brings up				facility.Tim Bryce is the Managing Director of M. Bryce
an important point; without a defined methodology,				& Associates (MBA)
Project Management is				of Palm Harbor, Florida and has 30 years of
an exercise in futility. It measures nothing. Only if a				experience in the field.
defined mode				He is available for training and consulting on an
of operation exists can dials and gauges be				international basis.

Clawar

Methodologies versus Techniques and Tools