Skip to main content

MPlaza Test - Multiple Scrum Teams

Last post 09:32 am July 8, 2016 by David Crecente
4 replies
11:36 am July 6, 2016

Hi all,
I have a doubt with a question from MPlaza mock exam.

If you are interested in this mocked tests, you shouldn't keep reading...

Question:
Nine (9) Scrum Teams are working on a single product. Which of the following is the best way of planning Sprints?

Answers:
* The Product Owner and all team members meet and create one Sprint Backlog for the project. All teams will share that Sprint Backlog for the next Sprint.
* The Product Owner meets with representatives from each team to compose the Sprint Goal and select items from the Product Backlog. Then each representative works with his/her team to create their Sprint Backlog.
* Everyone meets in the same time to check the Product Backlog and to receive information from the Product Owner. Then they coordinate dependencies, shift team members as needed, and create their Sprint Backlogs.

Which one do you think is correct?

After reading the Nexus Guide, I thought the second one was correct.

Thank you in advance.


07:36 pm July 6, 2016

Hey David -

The question you're referring to is a modification of a question that used to be in the "Scrum at Scale" online assessment (not available directly from scrum.org anymore) and I have to say was one of the most mind-stretching ones I've come across in all the assessments :)

https://www.scrum.org/Forums/aft/1172 - see the discussion starting near the middle of the thread

Anyway, as for the specific one that you linked, I'd eliminate A and B for the following reasons:

A) In Nexus all teams have their individual Sprint Backlogs that form the Nexus Sprint Backlog. There is no single, shared Sprint Backlog. Subtle, I know.

B) Again this is subtle, but in Nexus there is Nexus Sprint Goal and individual Sprint Goals for each team respectively. There is no single Sprint Goal.

Hope this helps!


07:22 am July 7, 2016

Hi again,
I thought the second one also have Sprint Goals per Team. But I think you are rigth. Nexus guide say


....Each Scrum Team then plans its own Sprint....

So, selected items + Sprint Goal

The second answer say


Then each representative works with his/her team to create their Sprint Backlog.

. So, there a single Sprint Goal is missed.

I can't imagine 5 people per Team so, 45 people (nine Teams) speaking with a Product Owner.

Do you think shift team members as needed is a standard practice.in a Nexus?.

I thought in Scrum Teams as cross-functional Teams, but if some team members are moved may be these team members have some special skills needed in several Teams.

Thanks again.


05:28 pm July 7, 2016


Do you think shift team members as needed is a standard practice.in a Nexus?.

I thought in Scrum Teams as cross-functional Teams, but if some team members are moved may be these team members have some special skills needed in several Teams.



That's a great question not only in the context of Nexus but Scrum alone as well. Check out the following link, discussion starting at the very bottom of the thread.

http://www.scrum.org/Forums/aft/1172


09:32 am July 8, 2016

Very useful.

Thank you.


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.