External Dependencies

Last post 03:17 pm September 22, 2016 by Simon Peters

2 replies

07:39 am September 20, 2016

Hi there, could anyone provide some guidance on how Nexus / SPS manages external dependencies once identified during Grooming / Spring Planning? I’m specifically interested in domain knowledge (people) for example is it recommended that these people are drawn into the team(s) for the duration of dependencies? Thanks.

Ian Mitchell

03:11 pm September 22, 2016

If you are referring to dependencies which are external to the Nexus itself, then the short answer is yes. A Nexus of teams must have all of the skills and resources necessary for turning product backlog into Done increments of potentially releasable work.

Simon Peters

03:17 pm September 22, 2016

Thanks Ian, appreciate the concise answer.

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.