Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: Quality, Developers and Testers: Organisational Issues

by jplindstrom (Monsignor)
on Jun 11, 2005 at 11:29 UTC ( #465791=note: print w/ replies, xml ) Need Help??


in reply to Quality, Developers and Testers: Organisational Issues

It all depends on your situation, how complex the software setup is, how the development is being done, whether the software is operated in-house or by an external party or delived to end-users, etc. Do the testers work closely together with development? Are there separate test systems that needs to be taken care of etc. Is there custom hardware involved?

But in my experience one tester to ten developers seems a bit low.

Something that have worked well for us is to have the testers and developers at the same level, both reporting to the project manager. Each iteration the software is stabilised and programmer tested before an internal release to the testers. They then deploy the software in their own environment.

To get this to work, it's important to practice the release process during the early iterations (short iterations with almost no features) to get all the not-so-obvious problems out of the way. It also helps the testers to get familiar with the basics of the software, and to identify where some things may need more operations documentation.

/J


Comment on Re: Quality, Developers and Testers: Organisational Issues
Re^2: Quality, Developers and Testers: Organisational Issues
by abhinavvaid (Acolyte) on Jun 15, 2005 at 12:00 UTC
    I completely agree. It really depends on the situation and complexity of the application and also the deployment scenario. I don't think that there can be any formulae that can define the ratio. What matters the most is what is tested and what is not tested and proper communication on the same. As is already known "When Microsoft can release an OS with 55000 known bugs, it clearly defines the management's perspective, which depends on the market conditions etc. Ideally there should be a separation between the developement and test teams, so that neither influences the other. And as said above (to practice the release process during the early iterations), so that maximum bugs are caught in the early phases, even regular code reviews can help a lot.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://465791]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (7)
As of 2014-08-27 11:19 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The best computer themed movie is:











    Results (237 votes), past polls