[teampractices] The Rule of Three (+1)

[Oliver Keyes]

On 20 September 2013 07:56, Federico Leva (Nemo) <nemowiki at gmail.com> wrote:

> Tomasz Finc, 17/09/2013 19:39:
>
>> [...] make
>>
>>> sure there was one representative from three departments in the
>>> discussion
>>> before consensus is reached. That usually meant Maryana (Product
>>> Manager),
>>> Jon Robson (Engineering Tech Lead), and Vibha (Design) would get together
>>> and hash things out by consensus.
>>>
>>> …
>>>
>>> [...] make sure to find at least one person in
>>>
>>> Product and one person in Design before proceeding/resolving/having the
>>> autonomy to do anything.
>>>
>>
> How many WMF teams have such a trine/trinitarian composition?
>
> Nemo
>

In terms of having representatives of at least 3 of
[design/product/engineering/community]; Mobile, VE, Core, and I believe
Platform is now getting some design resources (and now has a PM). This is a
non-exhaustive list - just those off the top of my head.

>
>
>  If you can't drag the missing person in, just ping
>>
>>> them on IRC on #wikimedia-corefeatures and relay the discussion there.
>>>
>>> The variation is that I'd like community/product analysis to be a part of
>>> this. From a logistical standpoint, it'd not practical to turn this into
>>> a
>>> rule of 4, so I'd like it to make three (plus one). This means the rule
>>> of
>>> three to resolve, and the missing leg would be informed as soon as is
>>> reasonable (and can provide their input then).  [...]
>>>
>>


-- 
Oliver Keyes
Product Analyst
Wikimedia Foundation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/teampractices/attachments/20130920/8ce2c56c/attachment.html>