Skip to main content

Others teams planning affecting our sprint

Last post 02:59 pm September 18, 2018 by Sander Dur
7 replies
07:10 pm September 13, 2018

Other teams come to us in the middle of the sprint and ask to add a story. We understand that it adds business value but how can we control things from our side and let them know to organize things on their end during their sprint planning?



08:18 pm September 13, 2018

Why not get them to liaise with the Product Owner and let him or her make any decisions regarding business value?

08:56 pm September 13, 2018

Might you and the other teams need to plan together so your Sprints are not disrupted?  The Nexus Guide might offer you some help.

Do you have a Sprint Goal?  Think of the Sprint Goal as a gift of focus for your team.  As Ian said, the Product Owner needs to decide if this new, proposed Product Backlog item is more important than the Sprint Goal.  If so perhaps the Sprint needs to be cancelled, otherwise the Product Backlog item should be added to the Product Backlog for a future Sprint. 

07:46 am September 14, 2018

How do you currently visualize,understand and minimize the cross team dependencies,issues with the other team? Check if that process is working and needs any adaptation? Don't let the focus drift away from the sprint goal. The sprint goal provides you with enough flexibility to re-negotiate the scope/PBI's(without compensating the sprint goal)  as the work evolves.

Do you have a PO who takes the call on the business value and ordering of the PBI's?

01:31 pm September 14, 2018

Ask your Scrum Master to direct their requests to PO. And if it's ongoing thing, then have a look at Nexus and let's know your thoughts on suitability of the same in this scenario.

09:52 am September 17, 2018

@Kaizen Practitioner

Scrum Master shouldn't be a proxy. Let the other team to speak directly with PO. There is always a risk, that forwarding the message will make it disorted.

01:52 pm September 17, 2018

Krzysztof, I agree with KP - this isn't something for the PO or DT to fix. The SM is the one supposed to protect the team against influences/unwanted impact.


Note: We don't know whether other teams have their own POs, we don't know whether there's a single product, we don't know a lot. The OP didn't mention. If necessary, the PO could potentially be informed and invovled during sprint, and the topic should be brought up during the retrospective anyway to be reviewed (and further actioned if needed).

11:06 am September 18, 2018

Hi Ayesha,

Just a question for clearification; are these teams working on the same product as your team (Scaled Scrum/Agile)?

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

Please note that the first and last name from your 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. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, 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 may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.