Hacker News new | ask | show | jobs
by rumanator 2349 days ago
It should be noted that the "round robin" format has an important aspect which is to enable each team member to air his/her personal grievances regarding anything related to the project.
4 comments

I would rather have this kind of discussions in the retrospective. It is a dedicated time for the team to discuss pain points, and to take actions to heal them.
I think the sooner the team is aware about issues the better.
I'm going to assume the GP meant blockers rather than grievances. Grievances are more like injustices and shouldn't really be aired at standups in a healthy team.
I think putting this in terms of "grievances" isn't helpful. Blockers, problems, observations, are all useful to report.

"Worked on adding discounts to the shopping cart page. Went over to talk to Chris in billing about that, and he mentioned in passing that they are planning to move on to SAP next year."

That could be incredibly important information for the team! It doesn't come up as naturally when working through stories as in a round robin.

Grievances should relate to a ticket on the board, if not then make a ticket for it, if not that then is the grievance important?
> Grievances should relate to a ticket on the board, if not then make a ticket for it, if not that then is the grievance important?

That mindset is precisely the reason why these meetings are important, because these grievances might not necessarily reflect or deserve a ticket. They might be nothing or they might be something. What's important is that these meetings create a space where they can safely be addressed without creating any burden on the team and on the individual reporting them.

I've read somewhere that these meetings work as therapy for the team. Perhaps by putting it this way you might better understand the issues these meetings solve.

This stuff goes in a retrospective. Airing of non specific grievances, therapy, etc. A scrum should be as short as possible.
There is a simple solution to this. After the board is done someone can just ask "Has anyone got anything else to add?"
>>There is a simple solution to this. After the board is done someone can just ask "Has anyone got anything else to add?"

That doesn't cut it. Being expected to talk about stuff doesn't put you on the spot, and purposely requesting the team to address a concern makes you stand out as the one creating problems where none existed.

If team members need to be directly asked if they see problems otherwise they won't do it themselves, then there is a much bigger trust or "safety" issue at play.