MENU
The relationship between the Product Owner and the Developers has degraded over time.
The Developers are growing increasingly angry with the Product Owner for changing the requirements all the time and not being available enough. The Product Owner is angry with the Developers for changing requirements during implementation. What guidance should the Scrum Master offer?
(choose the best answer)
38 comments · newest first
EL
Elizabeth
10 months ago
B feels too harsh, collaboration should come from understanding, not threats.
AN
Angella
11 months ago
A is just a waste of time, they need to address the issues directly.
CA
Cathrine
11 months ago
Wait, are they really changing requirements during the sprint? That’s surprising!
JO
Josue
11 months ago
I disagree, D seems like a better option to clear the air.
MA
Maybelle
11 months ago
Sounds like C is the best choice. Communication is key!
PE
Pearlie
12 months ago
I feel like option C makes the most sense. Understanding why requirements change could lead to better collaboration between the team and the Product Owner.
RO
Rodrigo
12 months ago
I'm a bit uncertain about whether involving a project manager is a good idea. It feels like it might undermine the Product Owner's role.
GO
Golda
12 months ago
I think we practiced a similar scenario, and addressing the issues during a Sprint Retrospective could really help clarify things.
UL
Ulysses
1 year ago
I remember we discussed the importance of communication in Scrum, but I'm not sure if taking everyone off-site is really the best solution.
BO
Bonita
1 year ago
I'm a bit worried about option B - getting the managers involved could just make things worse and create more resentment. The Scrum Master should try to address this within the Scrum framework first before escalating to higher-ups.
TA
Tawny
1 year ago
Option C sounds like the most practical approach here. Getting the Developers and Product Owner to openly discuss the reasons behind the requirement changes and the impact on value is key to resolving this conflict.
JA
Javier
1 year ago
This seems like a classic Scrum issue that the Scrum Master should address. I'd go with option C - addressing the root causes of the requirement changes during the Sprint Retrospective.
FR
Franchesca
1 year ago
I'm not sure about this one. The options seem a bit extreme. Taking everyone off-site or bringing in an external mediator seems like overkill. Maybe the Scrum Master could try facilitating a discussion first before resorting to drastic measures.
EL
Elvis
1 year ago
Hmm, this is a tricky one. I'm not entirely sure about the specific options on the Release phase list. I'll have to think it through carefully.
ED
Edelmira
1 year ago
I think option A sounds familiar since we went over user activity settings in class, but I'm not entirely sure if it's the default behavior.
ST
Stefany
1 year ago
I've got a good feeling about C. Q-in-Q is the only one here that's designed for single service per port, if I remember correctly.
SI
Simona
1 year ago
I bet the Developers are just itching to change the requirements again, just to spite the Product Owner. This sounds like a classic case of 'the inmates running the asylum'.
EL
Elza
1 year ago
C) Address why requirements change during the Sprint Retrospective. Ask the Developers and the Product Owner to talk about why the requirements are changing and consider the impact on value during this discussion.
TR
Trevor
1 year ago
A) Take everyone to a 2-day off-site event to relax and re-align. It is liberating to take people's minds away from work.
DE
Derick
1 year ago
Asking the functional managers to intervene? That's like throwing gasoline on a fire. The Scrum Master should be the one to guide the team, not some higher-ups.
AN
An
1 year ago
D) Ask for a project manager or other external resource to mediate and temporarily take over for the Product Owner.
SE
Sena
1 year ago
A) Take everyone to a 2-day off-site event to relax and re-align. It is liberating to take people's minds away from work.
DA
Dahlia
1 year ago
C) Address why requirements change during the Sprint Retrospective. Ask the Developers and the Product Owner to talk about why the requirements are changing and consider the impact on value during this discussion.
RO
Rolland
1 year ago
Bringing in a project manager to take over the Product Owner's role? That's just passing the buck. The Scrum Master needs to facilitate better communication between the team members.
RO
Roxane
1 year ago
C) Address why requirements change during the Sprint Retrospective. Ask the Developers and the Product Owner to talk about why the requirements are changing and consider the impact on value during this discussion.
MA
Mariann
1 year ago
Bringing in a project manager to take over the Product Owner's role? That's just passing the buck.
AD
Adell
1 year ago
B) Ask each person's functional manager to instruct their employees that they must collaborate better, or be removed from the team.
DO
Dortha
1 year ago
C) Address why requirements change during the Sprint Retrospective. Ask the Developers and the Product Owner to talk about why the requirements are changing and consider the impact on value during this discussion.
CA
Carylon
1 year ago
Hold a 2-day off-site event? Sounds like a vacation to me! I'm all for it, as long as the company's footing the bill.
JA
Jannette
1 year ago
Hold a 2-day off-site event? Sounds like a vacation to me! I'm all for it, as long as the company's footing the bill.
RU
Ruthann
1 year ago
A) Take everyone to a 2-day off-site event to relax and re-align. It is liberating to take people's minds away from work.
WI
Winfred
2 years ago
Yeah, option C seems like the best approach to improve the relationship between the Product Owner and the Developers.
LI
Lisbeth
2 years ago
The Scrum Master should definitely address the root cause of the issue during the Sprint Retrospective. It's the best way to get everyone on the same page and find a collaborative solution.
GE
Gerald
1 year ago
C) Address why requirements change during the Sprint Retrospective. Ask the Developers and the Product Owner to talk about why the requirements are changing and consider the impact on value during this discussion.
RO
Romana
1 year ago
A) Take everyone to a 2-day off-site event to relax and re-align. It is liberating to take people's minds away from work.
TR
Tresa
1 year ago
C) Address why requirements change during the Sprint Retrospective. Ask the Developers and the Product Owner to talk about why the requirements are changing and consider the impact on value during this discussion.
SA
Salome
2 years ago
I agree with Valda. We need to understand why the requirements are changing and how it impacts the value.
VA
Valda
2 years ago
I think we should choose option C. It's important to address the root cause of the issue.