about communication and collaboration

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

about communication and collaboration

Stéphane Ducasse
Dear Pharoers

last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
I got quite frustrated by that situation, especially because we are working hard to build a better system.
So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.

For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
plan to do. Simple, easy.
Then after people of the rmod team can discuss if they want more.

We want to do the same with pharo.
Often this is not that we are not doing things. Often we are doing boring, tedious stupid but $^%&&*^ important tasks and we want that you know it.
In addition we want to share on what we are weekly working. So that you can be more engaged to
join and collaborate with us.

So we will launch an experience and see. For now we will send a notification every two weeks.

the Pharo Team
Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

Damien Pollet
I guess the test email I just triggered is busy braving the snow & blizzard outside…


On 12 March 2013 16:02, Stéphane Ducasse <[hidden email]> wrote:
Dear Pharoers

last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
I got quite frustrated by that situation, especially because we are working hard to build a better system.
So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.

For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
plan to do. Simple, easy.
Then after people of the rmod team can discuss if they want more.

We want to do the same with pharo.
Often this is not that we are not doing things. Often we are doing boring, tedious stupid but $^%&&*^ important tasks and we want that you know it.
In addition we want to share on what we are weekly working. So that you can be more engaged to
join and collaborate with us.

So we will launch an experience and see. For now we will send a notification every two weeks.

the Pharo Team



--
Damien Pollet
type less, do more [ | ] http://people.untyped.org/damien.pollet
Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

SergeStinckwich
In reply to this post by Stéphane Ducasse
On Tue, Mar 12, 2013 at 4:02 PM, Stéphane Ducasse
<[hidden email]> wrote:
> Dear Pharoers
>
> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
> I got quite frustrated by that situation, especially because we are working hard to build a better system.
> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>
> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
> plan to do. Simple, easy.
> Then after people of the rmod team can discuss if they want more.

It looks like quite an interesting idea in a research team. Do you a
have a description somewhere how it works ?
This is similar to a standup meeting ?

Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/

Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

Camillo Bruni-3
In reply to this post by Damien Pollet
very nice it gets my official stamp of approval!
On 2013-03-12, at 16:13, Damien Pollet <[hidden email]> wrote:

> I guess the test email I just triggered is busy braving the snow & blizzard
> outside…
>
>
> On 12 March 2013 16:02, Stéphane Ducasse <[hidden email]> wrote:
>
>> Dear Pharoers
>>
>> last january I visited another lab and I realised that the Pharo Team was
>> not good at systematically telling what we were doing.
>> I got quite frustrated by that situation, especially because we are
>> working hard to build a better system.
>> So we brainstormed when I came back and we want to apply the same ideas
>> that what we do for our research team.
>>
>> For our research team every monday we get a simple mail that tell us to
>> say to the others what we did and what we
>> plan to do. Simple, easy.
>> Then after people of the rmod team can discuss if they want more.
>>
>> We want to do the same with pharo.
>> Often this is not that we are not doing things. Often we are doing boring,
>> tedious stupid but $^%&&*^ important tasks and we want that you know it.
>> In addition we want to share on what we are weekly working. So that you
>> can be more engaged to
>> join and collaborate with us.
>>
>> So we will launch an experience and see. For now we will send a
>> notification every two weeks.
>>
>> the Pharo Team
>>
>
>
>
> --
> Damien Pollet
> type less, do more [ | ] http://people.untyped.org/damien.pollet


Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

EstebanLM
In reply to this post by SergeStinckwich
I just sent my list of issues as an example... yes, is some kind like a remote-standup meeting.

Esteban

On Mar 12, 2013, at 4:48 PM, Serge Stinckwich <[hidden email]> wrote:

> On Tue, Mar 12, 2013 at 4:02 PM, Stéphane Ducasse
> <[hidden email]> wrote:
>> Dear Pharoers
>>
>> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
>> I got quite frustrated by that situation, especially because we are working hard to build a better system.
>> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>>
>> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
>> plan to do. Simple, easy.
>> Then after people of the rmod team can discuss if they want more.
>
> It looks like quite an interesting idea in a research team. Do you a
> have a description somewhere how it works ?
> This is similar to a standup meeting ?
>
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://doesnotunderstand.org/
>


Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

philippeback
In reply to this post by SergeStinckwich
A bad consultant with good marketing beats a good consultant with bad marketing.

Looks like it works for a lot of things in life, light being faster
than sound. (Oh, shiny!)

"(S)he looked nice until (s)he opened his/her mouth".

Phil

2013/3/12 Serge Stinckwich <[hidden email]>:

> On Tue, Mar 12, 2013 at 4:02 PM, Stéphane Ducasse
> <[hidden email]> wrote:
>> Dear Pharoers
>>
>> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
>> I got quite frustrated by that situation, especially because we are working hard to build a better system.
>> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>>
>> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
>> plan to do. Simple, easy.
>> Then after people of the rmod team can discuss if they want more.
>
> It looks like quite an interesting idea in a research team. Do you a
> have a description somewhere how it works ?
> This is similar to a standup meeting ?
>
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://doesnotunderstand.org/
>

Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

stephane ducasse
In reply to this post by SergeStinckwich

On Mar 12, 2013, at 4:48 PM, Serge Stinckwich <[hidden email]> wrote:

> On Tue, Mar 12, 2013 at 4:02 PM, Stéphane Ducasse
> <[hidden email]> wrote:
>> Dear Pharoers
>>
>> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
>> I got quite frustrated by that situation, especially because we are working hard to build a better system.
>> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>>
>> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
>> plan to do. Simple, easy.
>> Then after people of the rmod team can discuss if they want more.
>
> It looks like quite an interesting idea in a research team. Do you a
> have a description somewhere how it works ?
> This is similar to a standup meeting ?

we tried but a stand up meeting failed with us.
So we just have a mail
        what you have done
        what you will do

Stfe
>
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://doesnotunderstand.org/
>


Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

SergeStinckwich
On Tue, Mar 12, 2013 at 5:13 PM, stephane ducasse
<[hidden email]> wrote:

>
> On Mar 12, 2013, at 4:48 PM, Serge Stinckwich <[hidden email]> wrote:
>
>> On Tue, Mar 12, 2013 at 4:02 PM, Stéphane Ducasse
>> <[hidden email]> wrote:
>>> Dear Pharoers
>>>
>>> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
>>> I got quite frustrated by that situation, especially because we are working hard to build a better system.
>>> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>>>
>>> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
>>> plan to do. Simple, easy.
>>> Then after people of the rmod team can discuss if they want more.
>>
>> It looks like quite an interesting idea in a research team. Do you a
>> have a description somewhere how it works ?
>> This is similar to a standup meeting ?
>
> we tried but a stand up meeting failed with us.
> So we just have a mail
>         what you have done
>         what you will do

I would like to adopt such habits in my team, but standup meeting for
research team is not really convenient.
There is a paper where SCRUM is adapted to research team needs:
http://www.cs.umd.edu/~mwh/papers/score.pdf

There is a business doing something like standup meeting by email here:
https://www.funscrum.com/
Apparently all the answers are summarized automatically.

Regards,
--
Serge Stinckwich
UCBN & UMI UMMISCO 209 (IRD/UPMC)
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/

Reply | Threaded
Open this post in threaded view
|

Re: about communication and collaboration

philippeback
Old stuff of mine (10 years old oh my!) but still works:

http://highoctane.be/articles/TeamManagementTeammeeting.html
http://highoctane.be/articles/fog0000000032.html (Team Tracking)

%s/CVS/Source Control/g
%s/MSN/IM/g

There is even a mention of the original SCRUM stuff: (1997!!!)
http://jeffsutherland.org/scrum/scrum_pattern.html


(For the fun & trivia, the fogxxxx name comes from FogCreek's CitiDesk
CMS - Pharo is using FogBugz, looks like there is something in the
fabric of the universe...)

Phil


2013/3/12 Serge Stinckwich <[hidden email]>:

> On Tue, Mar 12, 2013 at 5:13 PM, stephane ducasse
> <[hidden email]> wrote:
>>
>> On Mar 12, 2013, at 4:48 PM, Serge Stinckwich <[hidden email]> wrote:
>>
>>> On Tue, Mar 12, 2013 at 4:02 PM, Stéphane Ducasse
>>> <[hidden email]> wrote:
>>>> Dear Pharoers
>>>>
>>>> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
>>>> I got quite frustrated by that situation, especially because we are working hard to build a better system.
>>>> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>>>>
>>>> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
>>>> plan to do. Simple, easy.
>>>> Then after people of the rmod team can discuss if they want more.
>>>
>>> It looks like quite an interesting idea in a research team. Do you a
>>> have a description somewhere how it works ?
>>> This is similar to a standup meeting ?
>>
>> we tried but a stand up meeting failed with us.
>> So we just have a mail
>>         what you have done
>>         what you will do
>
> I would like to adopt such habits in my team, but standup meeting for
> research team is not really convenient.
> There is a paper where SCRUM is adapted to research team needs:
> http://www.cs.umd.edu/~mwh/papers/score.pdf
>
> There is a business doing something like standup meeting by email here:
> https://www.funscrum.com/
> Apparently all the answers are summarized automatically.
>
> Regards,
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://doesnotunderstand.org/
>

Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-users] about communication and collaboration

NorbertHartl
In reply to this post by Stéphane Ducasse
that's great! Another missing piece of the infrastructure!

Nobert

Am 12.03.2013 um 16:02 schrieb Stéphane Ducasse <[hidden email]>:

> Dear Pharoers
>
> last january I visited another lab and I realised that the Pharo Team was not good at systematically telling what we were doing.
> I got quite frustrated by that situation, especially because we are working hard to build a better system.
> So we brainstormed when I came back and we want to apply the same ideas that what we do for our research team.
>
> For our research team every monday we get a simple mail that tell us to say to the others what we did and what we
> plan to do. Simple, easy.
> Then after people of the rmod team can discuss if they want more.
>
> We want to do the same with pharo.
> Often this is not that we are not doing things. Often we are doing boring, tedious stupid but $^%&&*^ important tasks and we want that you know it.
> In addition we want to share on what we are weekly working. So that you can be more engaged to
> join and collaborate with us.
>
> So we will launch an experience and see. For now we will send a notification every two weeks.
>
> the Pharo Team