Back to Forum

Cross functional teams

Last post 01:26 am January 4, 2018 by Charles Bradley
2 replies
Jason Pearce
09:34 pm January 3, 2018

I was reading a book by Jeff Sutherland, who co-created Srum, and he mentions the old way of technology projects where:



1. Project requirements were documented 

2. Passed to architecture team

3. Passed to implementation/development team

4. Passed to testing team

5. Passed to customer



My organisation is very much like this, there are no cross-functional teams, everyone operates in their silos!



How SHOULD this be organised? Each cross functional team should contain members of the architecture/development/QA team from requirements gathering to release?

Ian Mitchell
01:22 am January 4, 2018

To be cross-functional, a team must have all of the competencies and resources needed to create a release-ready product increment every Sprint. They should also be able to refine work so it is ready for Sprint Planning.

How those competencies and resources are distributed amongst team members is an implementation matter, but everyone should be able to collaborate effectively and with minimal waste.

Charles Bradley
01:26 am January 4, 2018

One easy way is to take one person from each of those teams and form a Scrum Team with them.  (maybe double or triple up on programmers)

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.