Communications
To be both efficient and satisfying communications can only be:
- asynchronous:
we are "resources", and one should not lock us to
handle the information in a serial global way.
This is both inefficient and frustrating.
(Tool: from phone to SMS)
- persistent: one must
be able to find it back and to track the history. Otherwise, one
is condemned to perform again the same tasks and do the same
errors.
(Tool: from SMS to mail)
- public: it means that
the status quo should be clearly identified, and referred to. In
this case, this means our web pages.
(Tool: from mail to news)
- continuous:
one should not request large amounts of time and
energy in a surprising way out of schedule and concern from
other people. Respecting other people, means giving them a
feeling of security, i.e. ensuring them that their expectations
are not jeopardized.
Tools for achieving this have been known and used for years. They
are html (text and links!) and ClearCase for the documentation, news
for the communications (small increments!), and a few brief (~1/2
hour) meetings for the check-points.
Information,
unshared documents,
Visual is Bad,
Archives at Nortel
SCM function ToC
Marc Girod
Last modified: Mon Sep 30 18:57:09 EETDST 2002