Access Keys:
Skip to content (Access Key - 0)

Communication Issues

Skip to end of metadata
Go to start of metadata
Labels:
Skip to end of metadata
Go to start of metadata

Communication...a big problem in an inter-timezone project like ours. Again I think it is rather imporant to realize that we can not overcome the need for sleep (not for long anyway), hence some things are certainly complicated. Here are my musings on communication issues and what we should think about.

The most important thing is - how do we deal with show stopping issues?
Everyone has different times when they are free to work on WW. However interdependencies can not and should not be elliminated - just coordinated more.
So let's take some examples.

  1. I get up in the morning and decide to work on WW. Say I have 3 hours of time. After 20 mins I run into a problem - a UC lists 2 contradicting conditions. Which is true? I do not know enough about the subject and can not make a decision. So I can't work on it. Now everyone else is asleep at this time so my only possibility would be to mail the person who could answer the question or a list.
    A few things can be done to alleviate this situation:
    • Have other things to work on besides this, so the available 2.6 hours are not wasted.
    • Have me understand the subject well, so I can make the decision myself
    • Have the other people answer the mail asap..since our time difference is 7h, the shortest time limit we can set is 7h..but usually it can be answered quicker and should be, just in case I have some more time available right at that moment or something like that.
  2. I am working on something during the time that others are awake. I run into a show stopping issue. But noone is around on IRC. How should I contact people? IRC lag can go as high as 1.5h..people can time out or even not answer the question at all. Mail...I have had mails not answered at all..or answered in several days time..not very nice in such a situation. Blogs are even worse than mail in this regard..also private matters are not suitable for blogging for sure. So what is the solution?
  3. I am working on something and know that in 2 days I will get to a certain point in development where I need component X. I have no clue about component X and how it would be made. Someone else has to make it. How do I notify them that it should be done by that time? How do we make sure it does get done?

Post your own scenarios and of course ideas for solutions.

Labels:
  1. Dec 08, 2006

    I'll write more tomorrow, but everyone has a different communication style. Some people like email, others like web based stuff, still others would prefer voice chats.

    I think if we can improve our infrastructure just a little bit more, so that these different styles can be acoomodated. For instance, we have this blog thingie. Not very timely, but it is a rather pleasant format to collaborate in. Maybe we'd hook notifications into commenting, or use the RSS feeds feature and web type people can get their fix, and more email oriented people could use the RSS -> email tools. Anyhow, that was just a quick idea, we may even integrate IM for notifications for instance.

    Anyhow, I need to be up in 4 hours, so I'll pretend to get some sleep now. (smile)

  1. Dec 08, 2006

    I'll write more tomorrow, but everyone has a different communication style. Some people like email, others like web based stuff, still others would prefer voice chats.

    I think if we can improve our infrastructure just a little bit more, so that these different styles can be acoomodated. For instance, we have this blog thingie. Not very timely, but it is a rather pleasant format to collaborate in. Maybe we'd hook notifications into commenting, or use the RSS feeds feature and web type people can get their fix, and more email oriented people could use the RSS -> email tools. Anyhow, that was just a quick idea, we may even integrate IM for notifications for instance.

    Anyhow, I need to be up in 4 hours, so I'll pretend to get some sleep now. (smile)