The Ratio of Analysts to Programmers

"Good specifications will improve programmertime I heard of a systems analyst graduating to a
productivity far better than any programming tool ormajor management position was Dan Boone who
technique."was made President and COO of Armco Steel in the
- Bryce's LawINTRODUCTIONIn terms of systemslate 1970's.If systems analysis is performed correctly,
development, during the 1960's and early 1970's youprogrammer productivity should improve as analysts
were either a Systems Analyst or a Programmer.should be providing good specifications for application
Period. At the time, there were substantially moreassignments. In the absence of systems analysts,
analysts than programmers (at least a 2:1 ratio). Thisconsiderable time is lost by the programmer who has
was due, in part, to the fact that computing wasto second-guess what the end-user wants. Inevitably,
just coming into its own in the corporate world andthis leads to rewriting software over and over again.
there were still people around who could look atGood data and processing specs, as provided by a
systems in its entirety. However, there was asystems analyst, will improve programmer
screaming need for people to program computersproductivity far better than any programming tool or
and, as such, this became the boom years oftechnique. This means programmers are the
programming. If you knew COBOL, Fortran, or PL/1beneficiaries of good systems analysis.This brings up
you could just about right your own ticket. Salariesan interesting point, what should be the ratio of
were good, and you could intimidate your employerSystems Analysts to Programmers in a development
simply by what you knew (you had to commitorganization? Frankly, I believe there should be twice
something like murder to get fired). The emphasis onas many analysts than programmers. By
programming became so great that authors rushedconcentrating on the upfront work, programming is
out voluminous books to increase programmersimplified. Let me illustrate the point by using the
productivity, hence the birth of the Structuredfollowing triangles representing the total amount of
Programming movement of the late 1970's, whicheffort in a project (as an aside, I picked this up from
was followed shortly thereafter by the CASEmy customers in Japan who share my opinion), see:
movement (Computer Aided Softwaretriangle on the left represents the traditional approach
Engineering).While programming was growing inwhereby there is twice the number of programmers
stature, Systems Analysis was in sharp decline. Tradeto systems analysts. Under this approach,
groups such as the Association for Systemsconsiderably more time is spent producing software
Management (ASM) saw their membership dwindle toto satisfy poorly defined requirements. The Japanese
nothing and were forced to close their doors. Thepoint out the bottom of the triangle is actually
last of the old Systems Analysts either retired orbottomless as it means more time is needed to
were put out to pasture by corporations in thecomplete a project. Compare it to the triangle on the
1980's. New job titles emerged, such as Softwareright where there are twice as many analysts to
Engineer and Analyst/Programmer. This latter title is aprogrammers. Under this scenario, more time is spent
bit of a misnomer as the emphasis was onanalyzing the problem, designing the system, and
programming and not systems analysis.Althoughproducing better programming specs. Consequently,
programming excelled, a noticeable void began tothe programmers do not have to second-guess what
appear in terms of people who could see systems inhas to be performed and can go about their work
its totality. Writing a good program is one thing,more productively.The problem with the diagram on
getting it to interface with other programs to form athe right though is that Systems Analysis is
whole system is something entirely different. By theconsidered to be somewhat of a nebulous concept
turn of the century, the industry started to talkto management. Programming, on the other hand, is
about such things as "Enterprise Architecture,"more tangible and easier for people to grasp; you are
"Business Processes," "Business Rules," "Businesseither writing code and producing a program or you
Analysis," etc. Further, new conferences, tradeare not. Therefore, the mindset in management is
groups, and job titles began to emerge. Today,that you are not being productive unless you are
programmers are considered a dime a dozen and thecoding, hence the inclination to shortcut systems
stock of a true analyst is on the rise.All of this isanalysis. This is a key reason why Systems Analysis
indicative of the industry trying to reinvent systemscollapsed in the 1980's. And this is why it is necessary
theory. In reality there is nothing new here asto provide training so management appreciates the
systems analysis is systems analysis. But asneed for systems analysis. Frankly, I have found
companies implement these concepts and job titlesmanagement can be very supportive if it is
again, they are a bit uncertain as to where they fit inpresented to them properly.CONCLUSIONWhether
and their relationship to other Information Technologyyou call them Systems Analysts, Business Analysts,
functions.CHARACTERISTICSA Systems AnalystSystems Engineers, or Enterprise Architects, it is very
goes by many names these days; e.g., Businessencouraging to see this vital function being
Analyst, Enterprise Architect, Systems Engineer (myreintroduced to companies. As far as I am
personal preference), etc. Nonetheless, we are talkingconcerned, it was inevitable. I guess companies finally
about a person whose mission is to study thefigured out you cannot satisfy your systems
information requirements of a business and design aproblems simply by using better programming tools
total system solution to satisfy them. Further, theand techniques.We are also beginning to see the
analyst is responsible for specifying the softwareresurgence of related trade groups to replace such
requirements and, as such, is considered thegroups as the Association for Systems Management
intermediary with the programming staff. The(ASM), for example:The International Institute of
personal characteristics of the analyst areBusiness AnalysisThe IIBA appears to be picking up
considerably different than the programmer. Whereaswhere ASM left off, including certification. Whereas
the programmer tends to be more introverted andASM developed and offered the Certified Systems
focused on technology, the analyst tends to be moreProfessional (CSP) certification years ago, IIBA wants
business oriented and extroverted. Analysts possessto create something similar.All of this is indicative of
good communications skills (verbal and written) tohow the industry is trying to reinvent systems
effectively work with both the end-users and thetheory. Whereas such systems work was well
programming staff. They know how to conduct anknown up until the 1980's it was forgotten over the
interview and make a presentation (salesmanship). Inlast twenty years due to the emphasis on
addition, they tend to look at the bigger picture asprogramming. Fortunately, companies have finally
opposed to just a portion of it, and possess anrealized the importance of systems work and are
entrepreneurial spirit.The analyst understands thetrying to get their houses in order. I guess what goes
business problems of the end-user and is intimatearound, comes around.Tim Bryce is the Managing
with the operation of the user's department. In otherDirector of M. Bryce & Associates (MBA) of Palm
words, the analyst can comfortably walk in the shoesHarbor, Florida, a management consulting firm
of the end-user. If they are doing their job properly,specializing in Information Resource Management
analysts make excellent candidates to assume(IRM). Mr. Bryce has over 30 years of experience in
responsibility in the management hierarchy. Butthe field. He is available for training and consulting on
because analysts were in decline for so many years,an international basis.
this hasn't happened for quite some time. The last