home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!mole-end!mat
- From: mat@mole-end.matawan.nj.us
- Subject: Re: Software psychology and the role of temperment in the programming team
- Message-ID: <1992Sep11.095636.15748@mole-end.matawan.nj.us>
- Organization: :
- References: <79076@ut-emx.uucp> <-191179993@hpopd.pwd.hp.com>
- Date: Fri, 11 Sep 1992 09:56:36 GMT
- Lines: 33
-
- In article <-191179993@hpopd.pwd.hp.com>, ajp@hpopd.pwd.hp.com (Andy Pearce) writes:
-
- > ... A key ingredient in any team (IMO) is respect for one another,
- > and willingness to communicate and collaborate to achieve a common
- > well-defined goal.
-
- Let me repeat Andy's statement:
-
- ... A key ingredient in any team (IMO) is respect for
- one another, and willingness to communicate and collaborate
- to achieve a common well-defined goal.
-
- This is one of the few things that costs nothing and benefits every
- team member(*), and the team as a whole, just as soon as it is provided.
-
- (Why the asterisk? Because it doesn't benefit BS artists who hide
- behind their `dignity' to conceal their negative worth. But those
- tend to be almost rare enough ...)
-
- Vic Vyssotsky (have I misspelled his name?) somewhere notes that
- functional organizations are efficient, while product organizations
- are effective and flexible. For development, you need the latter.
- And the functional organization, by dividing work into little bits
- owned by different players and preventing any individual from seeing
- the whole process, works against communication, collaboration, and
- mutual respect. (``Throw it over the wall. It doesn't matter; the
- specs we got were wrong and They will chuck our work and redesign it
- anyhow so whatever we did get right will get _totally_ flogged up.'')
- --
- (This man's opinions are his own.)
- From mole-end Mark Terribile
-
- mat@mole-end.matawan.nj.us, Somewhere in Matawan, NJ
-