[teampractices] The Rule of Three (+1)

[Maryana Pinchuk]

+1000

I like this rule for a few specific reasons:

1) Product scope and implementation concerns are flagged right away. You
won't go down a dark path, only to have some obvious flaw emerge and thwart
all your work 2 weeks down the road.

2) Important decisions won't get lost, forgotten about, misinterpreted
three weeks later, or hashed and rehashed a thousand times if you commit to
documenting them right away and moving forward.

3) We're trying to solve hard problems, and we need diverse brain power to
solve them. No one person can see everything from all angles – certainly
not me :)

4) Most importantly: It helps everyone feel like a team conquering
challenges together, instead of disconnected workers on a conveyor belt.

I'm not exactly sure how the community piece will get added in, but I'm
open to experimenting... :)


On Tue, Sep 17, 2013 at 1:08 PM, Tomasz Finc <tfinc at wikimedia.org> wrote:

> On Tue, Sep 17, 2013 at 11:43 AM, Oliver Keyes <okeyes at wikimedia.org>
> wrote:
> > Terry mentions IRC - I think IRC and email are particularly good venues
> for
> > this, although not necessarily the only ones. They have the advantage of
> > storing institutional memory inside logs as well as synapse buckets.
>
> I'm partial to the email and the wiki as they are easily searchable
> and archivable. Most people don't know where to find IRC logs and i've
> seen them missing tons of times. Thus i treat IRC as no different then
> a hallway discussion in the office.
>
> Remember, if it didn't happen on the mailing list it didn't happen at all.
>
> --tomasz
>



-- 
Maryana Pinchuk
Product Manager, Wikimedia Foundation
wikimediafoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/teampractices/attachments/20130917/f7c948f1/attachment.html>