Feeds:
Posts
Comments

Posts Tagged ‘programmer’

Cem Kaner, a professor at the Florida Institute of Technology, has done research on the ratio of software testers to software developers. His presentation entitled “Managing the Proportion of Testers to Other Developers” is partially based on a meeting of the Software Test Managers Roundtable (STMR 3) in Fall 2001.

FIT

FIT

The study found that:
– There were very small ratios (1-to-7 and less) and very
large ratios (5-to-1).
– Some of each worked and some of each failed.
– Many remembered successful projects with ratios lower than 1-to-1 more favorably than successful projects with larger ratios.

Read the paper to find out why is there such a range of successful ratios, and why test managers be happy with relatively low ratios?

See: http://www.kaner.com/pdfs/pnsqc_ratios.pdf and http://www.kaner.com/

Read Full Post »

According to Tim Bryce (Managing Director of M. Bryce & Associates),

If systems analysis is performed correctly, programmer productivity should improve as analysts should be providing good specifications for application assignments. In the absence of systems analysts, considerable time is lost by the programmer who has to second-guess what the end-user wants. Inevitably, this leads to rewriting software over and over again. Good data and processing specs, as provided by a systems analyst, will improve programmer productivity far better than any programming tool or technique. This means programmers are the beneficiaries of good systems analysis.

This brings up an interesting point, what should be the ratio of Systems Analysts to Programmers in a development organization? Frankly, I believe there should be twice as many analysts than programmers. By concentrating on the upfront work, programming is simplified.

Source: Bryce, Tim, “The Ratio of Analysts to Programmers”, Toolbox for IT, August 24, 2006.

Read Full Post »

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: