Implementing QA process in Software Factory with limited staff
I've recently started working in Software Factory (basically, small but abundant projects) and I noticed that QA processes are very hard to maintain and implement. To keep a long story short, we have so many open projects at the same time that it becomes impossible to keep track of everything, develop metrics, reports. There's just two of us in the QA department, and roughly thirty developers, so imagine the workload we have to go through. We try to stay in close contact with every developer, going from desk to desk and getting updates from them, but this sometimes helps and sometimes just confuses us even more (one developer says one thing, another says something else, the System Analyst tells you another, so on and so forth).
My question is: how can we implement a process flexible enough to adapt to each project's needs? We found that sometimes we work in a sort of Agile methodology and other times we use Waterfall or more traditional methods. We want to have ONE process which we can apply to everything, and also be able to instruct developers on how to follow it (most of them have no clue about testing life cycles or methodologies).
It looks like a lot of stuff is haphazard in your company. Trying to manage with 2 QA resources is tough and I am sure you must already have asked for more QA resources.
Regarding the methodologies, you may want to talk to your management and get buy-in from everyone and start implementing one SDLC methodology.