| || |
Best Tool to Manage Multiple Development Teams
I have recently been signed on as a QA Director for a relatively small company. One of my first tasks is to identify tools that we should be using in regards to test management. After a limited one week assessment, I would like to get your thoughts on the best tool (or tools) to use for the following:
- Requirements management
- Workflow management
- Defect Tracking and reporting
The biggest problem that I am seeing, is that we outsource all of our development out of house, but all our QA is going to be done in house. We have about 5-6 different development houses in different parts of the world, and all of them use different development environments/methodologies and their own defect tracking mechanisms(TFS and JIRA). We also lack any unified process for things, which is another problem altogether, but hoping that a tool might allow flexibility for each development house to use their own methods.
In house, we have TFS, and I believe it has the above mentioned functionality, but before I start standardizing on this, does anyone have any experience and insight into things I should be considering to help manage this?
Our company is based in multiple locations. And to manage teams in multiple locations, we have been strictly using the project management software from Replicon. The tool is also capable of keeping track of time and tasks. Overall its a complete business solutions. I think so it will work for you pretty well. Check it out here.
I'm in a similar environment and we've been having success with utilizing TFS and Test Manager to bring work items together and across teams. You'll have to get buy-in from other managers to support this standard as well. TFS and Test manger does have some quirks but I think that it supports Agile methodologies well and definitely helps the team collaborate efficiently.
Best tool for us has really been just a bunch of post-it notes on a large whiteboard.
(with an intern who's job it is to make the Jira tickets reflect the state of the whiteboard so the outside stake holders can see.)