have been thinking about COLLABORATION. and i would like to work on it in more detail. For now here are my random notes:
Balance between collaboration and ability.
value collaboration as a skill equally with skill. especially collaborative communication : as distinct from simply communication – being very verbose but just slagging everyone else off for being stupid is not useful.
Rate things according to how useful they are:
define a CURRENCY for useful. In terms of agile the prime directive is producing working software. Also same for lean. THis is the currency. Is a behaviour / skill providing value in terms of achieving this goal?
Itas about HUMAN behaviour, not MACHINE or SOFTWARE behaviour!
be confident enough to know your not the best at something and still be valuable.
Subservience can be good and USEFUL? not sure about this.
WHATS THE POINT ? see value and currency
Be nice to people!
Accept others as having a valid point of view EVEN if they are doing something which you BELIEVE to be invalid not useful! this is an extreme principal – i.e. you might like to say “accept others as having a valid point of view, UNLESS they are doing something useful” this challenges you to be INCLUSIVE in your approach.
The competition between EGO and COLLABORATION – eveyone wants to be the HERO! the lone coder upon whose shoulders the fate of the world rests. even in the Agile pairing world this is funcamendtal human emotion – dont supress it, embrace it and try to utilise it – not sure how – but maybe by recognising collaboration as equally valuable can achieve a balance.
AUTHORITY through collaboration, not TECHNOCRACY.
IN theory if you have the best way to do something you should ALWAYS be able to get someone else to see the “truth” if after 30mins cant convince them then maybe it DOESNT MATTER!
Can take the method of XP and identify behaviours which are good and attempt to ALLWAYS do them – it at least generates an IDEAL and even if the reality never reaches that IDEAL, it will provide a driving force. much like the rest of the AGILE process.