Back to Forum

Team design in scaled scrum / nexus

Last post 08:02 am February 13, 2017 by Matthias Müller
2 replies
Matthias Müller
09:50 am February 10, 2017

Hi,

I have a question regarding the team design within a scaled scrum / nexus. We are thinking about using nexus for a scaled scrum project with about 4 teams.

Our current discussion is about how to do the "team design", so if we should split the teams along the different business processes supported within the system or along the different architecture layers, e.g. one team responsible for the UI, one for the backend, and so on.

I really would appreciate your thoughts and experiences on this topic.

Ian Mitchell
08:54 pm February 10, 2017

Each Development Team within a Nexus ought to be a fully-fledged Scrum Development Team.

Given that a Scrum Development Team ought to be able to provide a potentially releasable, feature-complete increment each Sprint, which of the options you have described would be the most preferable? Perhaps most importantly, can you see how an orientation around feature-teams would help to mitigate integration risk?

Matthias Müller
08:02 am February 13, 2017

Hi Ian,

Given your thoughts It's quite obvious to split along the business processes.

Thanks!

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.