[
Lists Home |
Date Index |
Thread Index
]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ Robin LaFontaine <robin.lafontaine@deltaxml.com> was heard to say:
| So the second one often does not get serious take-up until a long time
| later. But somehow we should be learning how to do this better.
It's definitely the social problems that are the hardest to manage.
You get all sorts of tensions.
* Small working groups are better than big working groups, but
* Everyone wants to participate in "important" groups
* Small and simple is better than big and complex, but
* Everything has to go in V1 in case there's no V2.
* Experience is good, but
* As soon as V1 is finished, work begins on V1+delta
* Not all requirements are equally important to all participants, but
* A single, minimal set of requirements would help make specs simpler.
* Strong technical leadership with vision is best, but
* Not all groups contain strong technical leaders, and
* Some groups contain several strong leaders with competing visions
So, if you're lucky, you get a relatively small working group with
strong technical leadership doing something with a relatively narrow
scope that no one particularly cares about before it's finished.
If you're not lucky, you get a large working group containing lots of
people with competing agendas, no single clear technical vision,
working in an area that lots of people assert is desperately
important.
If you know how to solve these problems, I see the Nobel Price for
Peace in your future.
Be seeing you,
norm
- --
Norman.Walsh@Sun.COM | It is a general error to imagine the loudest
XML Standards Architect | complainers for the public to be the most
Sun Microsystems, Inc. | anxious for its welfare.--Edmund Burke, 1769
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE9mxFqOyltUcwYWjsRAsAUAJwNjNnRAB/bHrhfMNqdE3oHcfcA9QCfYZZ/
+SLKOBzsFCfqx6hWzt0irtU=
=xl55
-----END PGP SIGNATURE-----
|
