RE anecdotal evidence: in my experience, if you start asking people to
bring evidence to support their complaint, they will do so more often later
and over time. People appreciate it when you want to find a success metric
for their issue.
RE low respondents:
Try keeping the survey as light as poss
*tl;dr:* Metrics targeted exactly to the specific things we want to change
may be more helpful than general opinion surveys.
David was extremely helpful in clarifying my thinking on how I should
measure the effectiveness of the VE process work I've been doing. So I
want to brain-dump before it ev
On Tue, Aug 11, 2015 at 10:40 AM, Kevin Smith wrote:
>
> On Mon, Aug 10, 2015 at 10:20 AM, Bryan Davis wrote:
>>
>> This "burden" is not unique to the WMF or FLOSS systems. This is one
>> of the reasons that a typical software development organization with
>> stable funding grows its developer te
To me, the basic problem is that all these classifications are based on
relatively subjective judgments of what is good (vs. debt), necessary or
optional. Reasonable people can and do disagree on this.
To establish meaningful numbers, we would need to classify work with a
reasonably uniform set of
Just to throw my 2 cents in here.
I am a huge fan for data analysis and categorization of work. It empowers
us to make more informed decisions.
I'm objectively opposed to apriori buffering or assumed capacity for
certain amounts of work. There have been some comments on the thread about
how much
On Mon, Aug 10, 2015 at 10:20 AM, Bryan Davis wrote:
> I think I would personally invert Kevin's assertion and say that most
> teams are (or should be) spending a non-trivial amount of time
> performing both maintenance and responsive correction work. Hopefully
> this doesn't rise above a reasona
