Put money where your vote is!
Posted: May 04 2011
What I dislike about current Feature Management:
1. Voting virtually doesn't count at all:
- features with as little as 1 vote are targeted for implementing: https://www.multicharts.com/pm/viewissu ... _no=MC-139 while features with 17 votes are not targeted for implementing: https://www.multicharts.com/pm/viewissu ... e_no=MC-38
This is pure non-sense and leads to frustration.
2. MC claims that while selecting features for implementation they are ''using our subjective criteria. It is a complex process. We do take the number of votes into account, however it is not a major factor'' - I suspect MC emplyees might even internally disagree of what their subjectve criteria are.
3. Implementing features takes ages!:
(i) even those which I consider unimportant for myself
(ii) even those which other traders consider unimprtant for themselves.
This state of (i) non-effectiveness and (ii) selecting unimportant features cannot go forever.
Proposed changes to Project Management:
MC, in order to help you sort out the correct order of feature implementation I come up with an idea:
1. You put a reasonable price tag for each feature.
2. Traders will or will not commit to pay the price.
3. Traders' (sponsors') name are publicly visible to ensure transparency.
4. Once the comittment hits 100% of the price you wait 2 weeks for the commited funds to be transferred to your account.
5. Once you receive 100% of the price, you start coding.
6. A trader (sponsr) who contributed the most funds for a particular feature will have a right to decide on the final shape of the feature, e.g. if a feature is ''implementing key shortcuts'' the trader will decide on the shortcut combination.
This is voting with money. Features with higher % of funding will have a higher pririty.
This idea is explained by the attached picture. This idea is copylefted and copywronged by Tresor and can be traded to you in exchange for implementing ONE of the three features:
https://www.multicharts.com/pm/viewissu ... e_no=MC-70
https://www.multicharts.com/pm/viewissu ... e_no=MC-87
https://www.multicharts.com/pm/viewissu ... e_no=MC-97
1. Voting virtually doesn't count at all:
- features with as little as 1 vote are targeted for implementing: https://www.multicharts.com/pm/viewissu ... _no=MC-139 while features with 17 votes are not targeted for implementing: https://www.multicharts.com/pm/viewissu ... e_no=MC-38
This is pure non-sense and leads to frustration.
2. MC claims that while selecting features for implementation they are ''using our subjective criteria. It is a complex process. We do take the number of votes into account, however it is not a major factor'' - I suspect MC emplyees might even internally disagree of what their subjectve criteria are.
3. Implementing features takes ages!:
(i) even those which I consider unimportant for myself
(ii) even those which other traders consider unimprtant for themselves.
This state of (i) non-effectiveness and (ii) selecting unimportant features cannot go forever.
Proposed changes to Project Management:
MC, in order to help you sort out the correct order of feature implementation I come up with an idea:
1. You put a reasonable price tag for each feature.
2. Traders will or will not commit to pay the price.
3. Traders' (sponsors') name are publicly visible to ensure transparency.
4. Once the comittment hits 100% of the price you wait 2 weeks for the commited funds to be transferred to your account.
5. Once you receive 100% of the price, you start coding.
6. A trader (sponsr) who contributed the most funds for a particular feature will have a right to decide on the final shape of the feature, e.g. if a feature is ''implementing key shortcuts'' the trader will decide on the shortcut combination.
This is voting with money. Features with higher % of funding will have a higher pririty.
This idea is explained by the attached picture. This idea is copylefted and copywronged by Tresor and can be traded to you in exchange for implementing ONE of the three features:
https://www.multicharts.com/pm/viewissu ... e_no=MC-70
https://www.multicharts.com/pm/viewissu ... e_no=MC-87
https://www.multicharts.com/pm/viewissu ... e_no=MC-97