openerp-community team mailing list archive
Mailing list archive
Re: Issue Trend Monitoring :: Community Governance :: Benchmarking
the point is a very successful management technic called benchmarking.
Wikipedia can explain this better.
But the bottom line is, that visualisation (that's why beauty is important)
and visualized comparation is capable of generating tacit motivaton without
the need to say or express something in addition to the benchmark.
Furthermore it creates common references, which gain momentum & validity in
function of their psychological 'easiness'. (again why beauty matters)
This all does it's magic quite tacitly, that's probably why it's not that
easy to graps. The foundations entirely lie in the realm of psychology and
managerial system dynamics.
However it's one of the more effective management techniques - that don't
need necesarily a boss...
Kind of the same idea of the odoo gamification stuff.
Think of shorting a feedback cycle until it is entirely incorporated into
the brain of the one you want to give feedback to.
El jun 23, 2014 11:14 PM, "Nhomar Hernández" <nhomar@xxxxxxxxx> escribió:
> I don't understand exactly what is the point David?.
> FYI, we had this kind of info available from launchpad
> (not as "cool" as github) but we had it.
> 2014-06-23 21:32 GMT-04:30 David Arnold - El Alemán <david@xxxxxxxxxxx>:
>> if we compare the statistics in odoo on issue categorizing and issue
>> resolution compared to other high volume projects, a benchmark
>> automatically might come to our mind.
>> I'm personally not able to set something up, but I want to drop this, in
>> order to strategically help crafting a healthy system dynamic between
>> contributers and publisher.
>> I found something here:
>> I'm confident the publisher would agree, to host a community benchmark
>> against the publisher repos. This might rise stress levels and quality
>> equally. I think odoo has changed name and moved to github, also, to
>> become something better...
>> However the community, which obviously is also very serious about it's
>> work, could implement such kind of statistics and occasionally benchmarks.
>> (look at number of forks, people, who merged and relation between open
>> and closed issues, see also total issues to open issues ratio on the issues
>> As a wise decision maker, I would look at such statistics as shortcutting
>> much unavailable information about the real project dynamics.
>> *Best* David
>> Mailing list: https://launchpad.net/~openerp-community
>> Post to : openerp-community@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openerp-community
>> More help : https://help.launchpad.net/ListHelp
> Saludos Cordiales
> Nhomar G. Hernandez M.
> Skype: nhomar00
> Web-Blog: http://geronimo.com.ve
> Servicios IT: http://vauxoo.com
> Linux-Counter: 467724
> twitter @nhomar