EffectiveStaticContract

Revision as of 19:43, 12 August 2007 by TedErnst (talk | contribs) (further refactoring)



The StaticContract is the only part of ConsensusPolling that does not change while a decision-making process is underway. This does not mean that participants cannot still have their concerns met with regards to GoThresholds or DoneTimer. Here's how:

GoThreshold

GoThresholds
Reason for being unhappy Solution
One or more GoThresholds is too high, and we will never be done because there isn't enough interest in this topic. A new ConsensusPoll is started with the lower GoThreshold(s).
One or more GoThresholds is too low. With low thresholds, participants may decide not to do outreach, thus missing important voices that need to be included in the process. Whoever realizes this problem sets her status to NotYet , with a comment about participation. For every person that does this, 9 more participants would need to be recruited to get the whole process to 90%.

What do we do if we are not happy with the DoneTimer ?

DoneTimer
Reason for being unhappy with the DoneTimer Solution
If the process feels like it's taking too long, and the document keeps getting edited (which resets the DoneTimer) If the document keeps getting better, than patience is the answer. If not, the ClotureThreshold comes in.
If people are still at status YES , and the document is about to pass even though it has significantly changed since these people lack checked in Someone can simply edit the document to reset the timer, as many times as necessary while people are being contacted to re-check the document and their status.
  • When the DoneTimer is running, any participants can edit the document to reset the timer. This will delay the expiry time of the DoneTimer, providing more time for the participants to realize that the GoThresholds have been reached.


Retrieved from "http://aboutus.com/index.php?title=EffectiveStaticContract&oldid=8821524"