comment on

I would imagine that the ideal ratio of testers to developers would depend on the development strategy used.

In an XP strategy that emphasizes test-driven development, developers write tests first and all developers are in effect testers as well, at least at the unit level. In this process, relatively few pure testers are needed to test integration of components and systems.

By contrast, a traditional software development process does the requirements analysis, architetecture development and coding at the beginning and testing doesn't ramp up until significant portions of the system are coded. This process needs more testers, who both look at low and high level behavior. Because testing comes in at later phase, the proportion of testers needed may also change over time.

-Mark

In reply to Re: Quality, Developers and Testers: Organisational Issues by kvale
in thread Quality, Developers and Testers: Organisational Issues by eyepopslikeamosquito

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks