How do Jamku's development team picks up features for development?

[adarshmadrecha]

This discussion thread provides overview of how we select features of development and system for prioritization.

[adarshmadrecha]

Words of CA Vatsal Bhatia, from Mumbai

There are 2 kinds of principle on which Jamku Brings updation in existing feature or new features...

1. On user demand and Voting
2. On principle of just demands (whether anybody asks for it or not), as a principle it should be there....

e.g Shortcuts addition / updation should be allowed to user... I think it was only me who asked for it, I assume, not many would be using it(it may be possible that many other users may need it in future at that time they might not need to ask for it, because it is already there)

still it was brought because it is something which is based on founding principle of Jamku... i.e. anything you want to update you can, you just do not get locked out.

Compare it with Tally, suppose you want to update a Voucher No. Series, from ABC-1001 to ABCD-1001 for a 500 vouchers, you have to mandatorily go thru GUI of tally, no option to update it in bulk...

Come to Jamku, no such problem, I ever face while using Jamku.

Jamku never explicitly stated that this is there founding principle, but working seems to be in sync with this principle and I really love this part.

After saying all this I can understand there may be pressure on developers for so many features being in pipe line, but that translates into priority (i.e. I understand it won't be done outrightly), but whether anything is to be done or not that is also a question that means it is not even in queue for development, queue may be as long as year, but it not even in queue...

Absence of this obstacle (which many developer do not understand, I have tried many such products) amaze me a lot in Jamku.