I just tested out Pointing Poker and it seems to do everything I need.
One person starts a session and sends the others a link. The votes get revealed to everyone at the same time when the last person votes or when someone clicks "show votes."
And what's really cool is that you can set custom values. My team uses a second deck of poker cards with team member names to figure out who should do something when nobody volunteers. I could set up a "human player" deck in pointing poker if it is needed.
(there's nothing like a snowstorm to cause you to figure out how to run a distributed sprint planning meeting on very little notice!)
Graham Church wrote:Our team just published the poker app we made. Maybe it can be some use - PlanITpoker. We add new features to it now and again in our spare time so if you have any suggestions let us know.
I tried it out and it says "waiting for moderator". As the person who created the room, am I not the moderator?
I actually had tried clicking Start. I just tried again and the problem was that I hadn't created a story. When my team uses the cards online, we just want to estimate without writing down what it is for so this didn't occur to me.
After I realized this wasn't about developing a gambling website I had to figure out what it was about
This concept of "anchoring" seems flawed. In wikipedia under anchoring there are a couple of examples of induced bias using Gandhi's age, and the number of doctors in the phone book. It seems like anchoring would only affect non-experts, and that the estimate of a non-expert wouldn't mean much anyway. In the experiments no subjects are experts on Gandhi's age or on how many doctors are in the phone book. Their estimate shouldn't matter. On the other hand if they are an expert, anchoring would not sway them away from the right number, which they know.
It's really to be tempted by what others on the team thing. Programming estimates are opinions whereas Gandhi's age is fact.
Also, the estimates of non-experts on the team do matter. Understanding their thought process often reveals hidden assumptions (or lack of knowledge) that when discussed makes for stronger teammates. And increases shared understanding of the work to be done.