Skip to main content

I've been asked to lend a resource to another team for a single story. Should I?

Last post 05:59 pm June 5, 2019 by Ian Mitchell
1 reply
03:13 pm June 5, 2019

Our organization has multiple scrum teams who are generally aligned with sub-divisions of our overall product. Another team has an epic planned for a coming release where they are short on resourcing to do development, but feel that they could test the resulting change.  It has been suggested that our team do the coding work, and that the epic owning team do the test work.

I don't feel that this is a viable approach.

I think that if our team is going to write the stories for the epic, that our team should be responsible for the dev, QA and overall epic acceptance.

 

Thoughts?


05:59 pm June 5, 2019

The title of your post says you’ve been asked to lend a “resource” to another team for a single story, which is different to being asked if your team can develop without testing an epic. It brings a different set of concerns. Are you able to clarify the situation?


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.