distributed icon indicating copy to clipboard operation
distributed copied to clipboard

Setup number of votes per column

Open markuspoerschke opened this issue 7 years ago • 8 comments

Maybe it is useful to allow voting on cards per column. In our case the retrospective has the following process:

  1. Everyone is allowed to write 4 Cards for "Went well" or "To improved"
  2. Then we will read the cards together and every person can explain
  3. Then we "cluster" the cards using the "merge" function
  4. Then we vote on the cards
  5. We talk about the most voted tasks and derive 3 action items
  6. At this point the votes per column takes place. We want to "commit" on the Action items. Here it would be great to have 3 more votes for the last column.

One possible solution might be to "clear the votes" so everyone gets more votes (I think this is #112).

markuspoerschke avatar Apr 28 '17 12:04 markuspoerschke

Humm I understand what you are talking about. I never saw this use case before. Usually all the retrospectives that I did, if you create a "action item", that means it needs to be done. There is no votes.

I think this functionality will increase the complexity of the tool and maybe it is not that necessary. Don't you think having 7 votes, and them you guys manage how many per columns is enough?

Thanks, Glauber

glauberramos avatar Apr 28 '17 15:04 glauberramos

Actually you are right. Because it would make sense only for documentation purposes. Maybe we can keep it as an idea.

markuspoerschke avatar Apr 28 '17 16:04 markuspoerschke

@markuspoerschke let's see if more people are interested in this. If we see more demand we can maybe turn it latter into a feature. Thanks for the contribution anyway.

glauberramos avatar Apr 29 '17 07:04 glauberramos

I like the idea of voting by column. Especially if you go beyond the 3basic columns

SQrL143 avatar May 06 '17 06:05 SQrL143

@DaddyBA I really think this is not necessary for now. It will add more complexity to the tool, more configuration, more code, etc.

The main goal of this tool is to keep it simple to improve the user experience. That's why it has been working with many teams across many countries and its been used by so many people.

I can maybe keep it open and see if more people will complain about it. But I have a feedback tool that I collect suggestions from people, and so far only 2 or 3 asked this functionality. It is not a very common suggestion, so probably people are not missing it too much.

glauberramos avatar May 08 '17 15:05 glauberramos

How comparable is 2or3 through the feedback button. Sounds like you have 4or5 confirmed interested parties. Typically only about 1/7 or less of population complains. This might be higher demand than it appears 😀

SQrL143 avatar May 08 '17 18:05 SQrL143

That's a good point. But I will keep it on "Idea - not priority" until I am more confident that we should implement that. I really don't want to make Fun Retro a complicated tool to use. I feel most of the success it had so far was because it is a simple and easy to use tool. Does it make sense?

Thanks, Glauber

glauberramos avatar May 08 '17 19:05 glauberramos

Sounds good!

Thank you

Bryan Shannon

On May 8, 2017, at 2:27 PM, Glauber Ramos [email protected] wrote:

That's a good point. But I will keep it on "Idea - not priority" until I am more confident that we should implement that. I really don't want to make Fun Retro a complicated tool to use. I feel most of the success it had so far was because it is a simple and easy to use tool. Does it make sense?

Thanks, Glauber

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

SQrL143 avatar May 08 '17 19:05 SQrL143