Page 1 of 1

Forming a composite Scrum team with multiple vendors

Posted: Mon 26 Nov 2018 11:44 pm
by kevine
One of our PMs on her project has a Scrum team from vendor A. She needed another developer. So she added one from another vendor. I like this idea because it keeps vendor A honest.

I'd like to do the same, but the project is currently at design stage so I can't use the resourcing excuse.

How can I:
  1. Introduce the idea to the vendor (overcome resistance), and
  2. Structure the commercials (e.g. SOW for main vendor and T&M for the single contractor)?
I suppose another option is to introduce two competing Scrum teams, but we don't have much budget and I think handling the code merges could be difficult.

Re: Forming a composite Scrum team with multiple vendors

Posted: Wed 28 Nov 2018 4:08 pm
by dhaughey
I see no reason why a Scrum team all need to come from one vendor. I work with teams split across multiple vendors with no problem. I have different vendors for UX web development and back-end development. The financials are managed with each vendor separately and confidentially.

You need to think about the benefit of this approach because you are increasing your management and administration overhead. I understand the idea of not having all your eggs in one basket, but perhaps that's better done across different projects, rather than within an individual project.

The reason I use multiple vendors, is to take advantage of specialists in each of the disciplines, which overall, results in a better product and outcome.

Re: Forming a composite Scrum team with multiple vendors

Posted: Thu 06 Dec 2018 6:29 am
by Stephbaker
dhaughey wrote:I see no reason why a Scrum team all need to come from one vendor. I work with teams split across multiple vendors with no problem. I have different vendors for UX web development and back-end development. The financials are managed with each vendor separately and confidentially.

You need to think about the benefit of this approach because you are increasing your management and administration overhead. I understand the idea of not having all your eggs in one basket, but perhaps that's better done across different projects, rather than within an individual project.

The reason I use multiple vendors, is to take advantage of specialists in each of the disciplines, which overall, results in a better product and outcome.
Nicely written! You made me understand the whole concept so easily which I wouldn't have otherwise! Thank you