So I'm going to be starting a Job here in a few weeks, I've been doing QA for about 6 years now. Pretty much your standard Test Plans/Testing with a little normal SysAdmin stuff that sometimes comes with the task.
I've had some good ideas implemented in companies, as far as tracking requirements/test plans/issues differently, and they seem successful.
However, this new position will be me laying down the foundation for QA. Right now things are done in what seems to be as needed as far as QA goes, requirements are gathered and sometimes kept in different locations, same with test plans (which are done by developers right now).
So my job will be sort of centralizing this, or developing a Flexible way of QA'ing the Software (Web/Mobile development).
So it seems the challenge will be centralizing everything, while creating test plans/ or ways of testing similar requirements that is flexible enough to span projects.
I've had a few ideas, however, all my previous test work was windows based (So test plans in TFS or Microsoft Test Manager). I wanted to get some ideas from everyone here, or anyone that has started a QA department from scratch. I was also going to see if there were any books on the subject.
My thoughts were mainly keeping projects separated for issue tracking (not sure of the software we will use yet). And keeping test plans for common I guess "actions/elements" that are repeated between different customers and executing those. Eventually maybe using selenium to save those "common" elements as test scripts.
But I've never set something up like this before solo, so I've been doing quite a bit of reading. Any books/suggestions would be appreciated!