Tag Info

New answers tagged

1

Niels van Reijmersdal and Dhiman already mentioned the most important point. I'd like to give a look into my experience as my situation was quite similar to yours now some years ago. I'm on a small freetime project (a browser game) and in the past years we tried to build up at a QA too which is a bit more problematic with only users who do the "work" in ...


2

Working with spreadsheets is not bad and strange, it all depends upon the scope and type of tracking you want to do, if you have a limited scope of test cases, issues and requirements, then you can stick to the excel sheets but in long run you will need some tracker which will make your work a lot easier and will itself perform some of your tasks which do in ...


2

One team, one system. Do not create separate spreadsheets, be transparent instead. I would Keep track of your whole project in a single tool. Jira is build to be defect/issue tracker. This is what it was original designed for. Just use it! :) Before development for requirements, during development for defects and communication, after development for ...



Top 50 recent answers are included