Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

What are the pros and cons of outsourcing development and testing to two different companies?

EDIT: Why do you prefer outsourcing development and testing to different companies or to the same company?

share|improve this question

closed as too broad by GlenH7, Wayne M, MichaelT, Dan Pichelman, gnat Jul 27 at 19:33

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

4 Answers 4

up vote 6 down vote accepted

Pros:

  1. The two teams are independent (and rivals) so there is no posibility of the testing team colluding with the development team or being "influenced" by the developers.
  2. If your testing requires some specialized testing requirements that the development company does not have, a specialized testing company can do that.

Cons:

  1. Communication gap due to isolation of both teams.
  2. Greater time lag due to the distance between the testing and development teams
  3. If there is a misunderstanding between the two teams over interpretation of a requirement or acceptance criteria, things are difficult to reslove
share|improve this answer

Pros:

  • You will get honest output from both the parties as both of them will try to prove their worth (provided they both are competent)

Cons:

  • You will have to give understanding of the system to both the parties.
  • Additional overhead of communication through out the life cycle of project.
  • More cost as the whole project is not with one company
share|improve this answer
    
Are you sure about the last point in Cons? –  Tech Jerk May 5 '11 at 5:51

Pros:

pretty obvious

Cons:

Time : Unless you lay down the ground rules right at the start, things have a very high possibility of getting out of hand and very much delayed

Management : You will have to finally make the trade off between time/feature and bug fixing To keep the project on schedule.

Imagine having to deal with 2 perfectionists on the opposite ends

share|improve this answer

Add to the good input above

Pro/Con When it all turns to custurd you have 2 parties to sue.

Cons Requirements changes need to be communicated and agreed by 2 parties simultaniously.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.