StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>This is what our teams call "conflict resolution". Every time we put together a team on a project, part of our team charter is to get everybody to agree to a <strong>conflict resolution model</strong>. We use this to ensure that in the case where we do not have 100% consensus, we have a model that everyone has agreed to to resolve the difference.</p> <p>In your case, your model starts by having a discussion and re-estimation to attempt to get folks onto the same number. When that fails, most of your team seemed to believe that taking the mean/average/most voted as the estimation was correct. By your question, I tend to think you had not agreed with that approach.</p> <p>On some of our teams, we have used a "competition" model, like rock-paper-scissors, to determine a victor. Sometimes it's always "highest wins" so that if the person who grabs the story is the person who needs more time they have the points to do it. Sometimes it's "majority rules", as seems to be the case on your team.</p> <p>I would suggest to your scrum master or product owner to have the team agree on a single model that everybody agrees to so that everybody knows what they are getting into. Something like the following.</p> <p><strong>Model:</strong></p> <ol> <li><strong>Step One:</strong> Discuss for 2 minutes and re-estimate.</li> <li><strong>Step Two:</strong> If still deadlocked, choose majority.</li> <li><strong>Step Three:</strong> If no clear majority, choose higher value.</li> </ol> <p>Obviously, this probably isn't the model you'll use, but it's an example of how you can go about getting your team to agree to something that always has an outcome and still allows the basic principle of talking it out first. The most important thing is that everybody knows what the model is, and everybody agrees to it.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload