BriteIdeas - Voting on a Change Request

From BriteWiki
Jump to: navigation, search

Community development priorities are established by votes in BriteIdeas. To vote on a Community change request, go to the Community screen and review the list of community change requests. Use the black arrows next to each item to up or down-vote a change request. As you vote, the Score of the change request will update. This score is what determines the item's rank in the Community list.

16 Anatomy of Voting.jpg

Explanation of Votes

Votes represent the production capacity for BriteCore. All clients receive 20 votes in BriteIdeas. This number is set somewhat arbitrarily and fixed across clients as a means of controlling the overall volume of the combined queues. Votes are weighted according to three factors: Support Dollars, Ownership of IWS, and New Business Referrals. Clients can use their votes to move items up or down in the Community development queue.

Standard Weight
Support Dollars Each company receives 20 votes
Recurring Revenue 1x – 2.5x from smallest to largest annual support (Current range is $25k - $200k)
Ownership 1.1x – 1.25x based on shares
Direct Referrals 1.1x voting weight for 12 months following contract execution for the referred client


Examples
  • Company A pays $25k in annual support (1x), owns 130 units of IWS (1.25x), and has given us 2 direct referrals (1.1+1.1) == x4.45
  • Company B pays $120k in annual support (1.8x), owns no shares, and has given no referrals == x1.8
  • Company C pays $200k in annual support (2.5x), owns 50 units of IWS (1.1x), and has given 3 direct referrals in the prior year (1.1+1.1+1.1) == x6.9

Calculating the Score

Community change requests are prioritized by score. Scores are determined by the number of votes they receive, times the weight of each vote. For example, if a client with a 1x weight and a client with a 3x weight both put two votes on a single request, that request will have a score of 8. This number also takes into account any down votes made by members of the community. Building off of our previous example, if a change request has a score of 8 and a client with a 2x weight uses 4 votes to down-vote the change, then that change request will now have a score of 0 since -2 x 4 = -8.

Gauging Popularity

Hearts represent the popularity of the change request and are calculated based on a percentage of votes (see illustration below). For example, if there are five fully colored hearts next to a change request, then that means it is universally loved by the community––no one has down-voted it. If a request is not universally loved (someone in the community has down-voted that request), then we know we need to investigate why that request has been down-voted before it's "Locked" for development.

Number of Hearts Popularity
1 Heart.png 20%
2 Hearts.png 40%
3 Hearts.png 60%
4 Hearts.png 80%
5 Hearts.png 100%


Related Links