Like many ISV companies, my company has a QA (Quality Assurance) organization. Notionally they are the team that serves as the final defense before the software goes out the door to ensure that it meets whatever standards of quality are appropriate. As a team independent of the developers, we expect them to see clearly what the product does and whether it is appropriate or not.
I’ve been thinking about this for a while now. It occurs to me that this is one quality function, but it still leaves a lot Quality issues open and unresolved. I suppose that in a purist sense, SQA is there to work in partnership with the development organization. But I am beginning to think that this is not enough.
{ 1 comment… read it below or add one }
You should never oppose quality engineers to developers: both of them should have the same targets and both should clearly understand the tasks of each other.
I think it’s the only was to build a strong software development team.