Supply chain management resources


The Ratio of Analysts to Programmers

"Good specifications will improve programmerhappened for quite some time. The last time
productivity far better than any programmingI heard of a systems analyst graduating to a
tool  or  technique."major management position was Dan Boone who
was made President and COO of Armco Steel in
- Bryce's LawINTRODUCTIONIn terms of systemsthe late 1970's.If systems analysis is
development, during the 1960's and earlyperformed correctly, programmer productivity
1970's you were either a Systems Analyst or ashould improve as analysts should be
Programmer. Period. At the time, there wereproviding good specifications for application
substantially more analysts than programmersassignments. In the absence of systems
(at least a 2:1 ratio). This was due, inanalysts, considerable time is lost by the
part, to the fact that computing was justprogrammer who has to second-guess what the
coming into its own in the corporate worldend-user wants. Inevitably, this leads to
and there were still people around who couldrewriting software over and over again. Good
look at systems in its entirety. However,data and processing specs, as provided by a
there was a screaming need for people tosystems analyst, will improve programmer
program computers and, as such, this becameproductivity far better than any programming
the boom years of programming. If you knewtool or technique. This means programmers
COBOL, Fortran, or PL/1 you could just aboutare the beneficiaries of good systems
right your own ticket. Salaries were good,analysis.This brings up an interesting point,
and you could intimidate your employer simplywhat should be the ratio of Systems Analysts
by what you knew (you had to commit somethingto Programmers in a development organization?
like murder to get fired). The emphasis onFrankly, I believe there should be twice as
programming became so great that authorsmany analysts than programmers. By
rushed out voluminous books to increaseconcentrating on the upfront work,
programmer productivity, hence the birth ofprogramming is simplified. Let me illustrate
the Structured Programming movement of thethe point by using the following triangles
late 1970's, which was followed shortlyrepresenting the total amount of effort in a
thereafter by the CASE movement (Computerproject (as an aside, I picked this up from
Aided Software Engineering).While programmingmy customers in Japan who share my opinion),
was growing in stature, Systems Analysis wassee: triangle on the left represents the
in sharp decline. Trade groups such as thetraditional approach whereby there is twice
Association for Systems Management (ASM) sawthe number of programmers to systems
their membership dwindle to nothing and wereanalysts. Under this approach, considerably
forced to close their doors. The last of themore time is spent producing software to
old Systems Analysts either retired or weresatisfy poorly defined requirements. The
put out to pasture by corporations in theJapanese point out the bottom of the triangle
1980's. New job titles emerged, such asis actually bottomless as it means more time
Software Engineer and Analyst/Programmer.is needed to complete a project. Compare it
This latter title is a bit of a misnomer asto the triangle on the right where there are
the emphasis was on programming and nottwice as many analysts to programmers. Under
systems analysis.Although programmingthis scenario, more time is spent analyzing
excelled, a noticeable void began to appearthe problem, designing the system, and
in terms of people who could see systems inproducing better programming specs.
its totality. Writing a good program is oneConsequently, the programmers do not have to
thing, getting it to interface with othersecond-guess what has to be performed and can
programs to form a whole system is somethinggo about their work more productively.The
entirely different. By the turn of theproblem with the diagram on the right though
century, the industry started to talk aboutis that Systems Analysis is considered to be
such things as "Enterprise Architecture,"somewhat of a nebulous concept to management.
"Business Processes," "Business Rules,"Programming, on the other hand, is more
"Business Analysis," etc. Further, newtangible and easier for people to grasp; you
conferences, trade groups, and job titlesare either writing code and producing a
began to emerge. Today, programmers areprogram or you are not. Therefore, the
considered a dime a dozen and the stock of amindset in management is that you are not
true analyst is on the rise.All of this isbeing productive unless you are coding, hence
indicative of the industry trying to reinventthe inclination to shortcut systems analysis.
systems theory. In reality there is nothingThis is a key reason why Systems Analysis
new here as systems analysis is systemscollapsed in the 1980's. And this is why it
analysis. But as companies implement theseis necessary to provide training so
concepts and job titles again, they are a bitmanagement appreciates the need for systems
uncertain as to where they fit in and theiranalysis. Frankly, I have found management
relationship to other Information Technologycan be very supportive if it is presented to
functions.CHARACTERISTICSA Systems Analystthem properly.CONCLUSIONWhether you call them
goes by many names these days; e.g., BusinessSystems Analysts, Business Analysts, Systems
Analyst, Enterprise Architect, SystemsEngineers, or Enterprise Architects, it is
Engineer (my personal preference), etc.very encouraging to see this vital function
Nonetheless, we are talking about a personbeing reintroduced to companies. As far as I
whose mission is to study the informationam concerned, it was inevitable. I guess
requirements of a business and design a totalcompanies finally figured out you cannot
system solution to satisfy them. Further,satisfy your systems problems simply by using
the analyst is responsible for specifying thebetter programming tools and techniques.We
software requirements and, as such, isare also beginning to see the resurgence of
considered the intermediary with therelated trade groups to replace such groups
programming staff. The personalas the Association for Systems Management
characteristics of the analyst are(ASM), for example:The International
considerably different than the programmer.Institute of Business AnalysisThe IIBA
Whereas the programmer tends to be moreappears to be picking up where ASM left off,
introverted and focused on technology, theincluding certification. Whereas ASM
analyst tends to be more business orienteddeveloped and offered the Certified Systems
and extroverted. Analysts possess goodProfessional (CSP) certification years ago,
communications skills (verbal and written) toIIBA wants to create something similar.All of
effectively work with both the end-users andthis is indicative of how the industry is
the programming staff. They know how totrying to reinvent systems theory. Whereas
conduct an interview and make a presentationsuch systems work was well known up until the
(salesmanship). In addition, they tend to1980's it was forgotten over the last twenty
look at the bigger picture as opposed to justyears due to the emphasis on programming.
a portion of it, and possess anFortunately, companies have finally realized
entrepreneurial spirit.The analystthe importance of systems work and are trying
understands the business problems of theto get their houses in order. I guess what
end-user and is intimate with the operationgoes around, comes around.Tim Bryce is the
of the user's department. In other words,Managing Director of M. Bryce & Associates
the analyst can comfortably walk in the shoes(MBA) of Palm Harbor, Florida, a management
of the end-user. If they are doing their jobconsulting firm specializing in Information
properly, analysts make excellent candidatesResource Management (IRM). Mr. Bryce has
to assume responsibility in the managementover 30 years of experience in the field. He
hierarchy. But because analysts were inis available for training and consulting on
decline for so many years, this hasn'tan international basis.



1 A B C D 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 94 95 96