Teamwork

Teamwork is the all-out favorite buzz-word of Agile. And rightly so. The team is the unit of work; without a good team, nothing happens and then only a Waterfall approach can get you to a low-quality result (for a lot of sweat, money, trouble and oh, it's probably late).

A nice example of how this works was last week. I had read the cepstrum post from Matt Hall on the Agile Geosciences blog. It's clear that this would be nice for OpendTect, we have the tools, we have the people to do it.

So, I Skyped (what a great tool Skype is for Agile development) Satyaki, pointing him to Matt's post. Before I knew it, he had made a button on the normal Amplitude Spectrum window, and asked me to check it out. I immediately visited Bruno, because we don't have spectra for well logs yet. And I think these cepstra are particularly interesting for well logs. In a moment, Bruno and Satyaki were discussing, I added some small design tips, and off everything went. I'm pretty sure Bruno will deliver something this week. Mind you, all beside their main project work.

The big things here are:

• Personal Skills
  
• Willingness to Help (team members, but also users)
  
• Interest for the work and topic
  
• Ability and willingness to Communicate
  

Our team is a SHIC team. (just invented that, here and now). Making plans for ehh, team meetings (every day - is that enough?), sprints (how fast can you code?), masters (who are the slaves?) and whatever more the apparatchiks of the various methodologies prescribe - suit yourself, whatever. The team itself, its building and nurturing - now that is the important part.