search

microsoft / vsts-extension-retrospectives

An Azure DevOps extension for efficient retrospectives
MIT License
180 stars 80 forks source link

restrict the visibility of a team retro only for team members #145

Closed rschue closed 7 months ago

rschue commented 3 years ago

If we have internal and external workers in a Teamproject with separate teams for different areas e.g. one for the external workers. We dont't want that the external workers see the Retro from the internal workers.

justdait commented 3 years ago

This is a big issue. Retrospectives should be private to the core team so they have psychological safety. Stakeholders should not be able to access the retrospective boards.

iivel commented 3 years ago

Any chance of a simpky checking that the user is a member of the team before loading the board? I removed the all teams from the dropdown, but there's a lot of code in there for loading up "something" evennif it was a retro the user wasn't part of.

justdait commented 3 years ago

Could this be prioritized? In an environment where you have multiple teams working in their own product space, you want to be able to give all Product Owners access to all the different teams to help manage cross-team dependencies. However, you only want the retrospectives to be visible to the core team members. This is 101 stuff for team psychological safety. If this is not resolved teams will then use retrospective tools outwith DevOps which is counterintuitive when you are trying to develop the system to be one version of the truth.

jwedel commented 2 years ago

I also think that retros should be private to the team by default, a nice option would be to make it public optionally. It is really important for the team to speak openly and do not fear any managers look at what they wrote.