Project Management

Please login or join to subscribe to this thread

Agile Project Management: Managing Team Disagreements

linkedin twitter facebook  
avatar
Pavan Maddi
Community Champion
Buona Vista, Singapore
During a daily stand-up meeting in a Scrum project, a team member raises a concern that a user story does not align with the project's overall goals. The team is divided on whether to include it in the sprint. What is the best approach to resolve this disagreement?

A. Ask the team member to escalate the issue to the product owner
B. Review the project's product backlog and prioritize the user story
C. Consult the Scrum team's working agreement and values
D. Put it to a vote and let the majority decide
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Pavan -

This is a poor question - debating the story's merits should have been done during sprint planning or even as part of the normal backlog refinement/lookahead planning which the PO and team would conduct on an ongoing basis.

However, if for some reason this concern fell through the cracks, the team member should have a chat with the PO.

Kiron
...
1 reply by Pavan Maddi
Oct 24, 2024 7:18 AM
Pavan Maddi
...

Thank you for your feedback! @Kiron



You make a valid point that debating the story's merits should have been done during sprint planning or backlog refinement. I understand that the concern should have been addressed earlier, and it's important to ensure that the team is aligned on the project's goals.

However, since the concern was raised during the daily stand-up meeting, the team needs to address it promptly. In this case, I believe that consulting the Scrum team's working agreement and values (Option C) could be a useful step in resolving the disagreement.

Additionally, I agree that the team member should have a chat with the Product Owner (PO) to clarify the story's alignment and prioritize it accordingly. This approach respects the PO's responsibility for the product backlog and ensures that the team is working on the most valuable tasks.

Thank you for your insight, and I'll keep in mind the importance of ongoing backlog refinement and the PO's role in prioritization

avatar
Pavan Maddi
Community Champion
Buona Vista, Singapore
Oct 24, 2024 7:05 AM
Replying to Kiron Bondale
...
Pavan -

This is a poor question - debating the story's merits should have been done during sprint planning or even as part of the normal backlog refinement/lookahead planning which the PO and team would conduct on an ongoing basis.

However, if for some reason this concern fell through the cracks, the team member should have a chat with the PO.

Kiron

Thank you for your feedback! @Kiron



You make a valid point that debating the story's merits should have been done during sprint planning or backlog refinement. I understand that the concern should have been addressed earlier, and it's important to ensure that the team is aligned on the project's goals.

However, since the concern was raised during the daily stand-up meeting, the team needs to address it promptly. In this case, I believe that consulting the Scrum team's working agreement and values (Option C) could be a useful step in resolving the disagreement.

Additionally, I agree that the team member should have a chat with the Product Owner (PO) to clarify the story's alignment and prioritize it accordingly. This approach respects the PO's responsibility for the product backlog and ensures that the team is working on the most valuable tasks.

Thank you for your insight, and I'll keep in mind the importance of ongoing backlog refinement and the PO's role in prioritization

Please login or join to reply

Content ID:
ADVERTISEMENTS

Not that there's anything wrong with that.

- Jerry Seinfeld

ADVERTISEMENT

Sponsors