« April 2006 | Main | June 2006 »

May 30, 2006

Brainstorming, Brainwriting and Swimming Pools

I was out of the office for most of last week, meeting with the Greenpeace fundraising community to discuss their requirements and wishes for a new CRM system. The purpose of the time was to do some initial reconnaissance on the project, get a feel for the scope and complexity of the issues, and assemble a working group who could take the project forward.

The meeting was held in a hotel near Barcelona, which makes more sense when you realise that people had to travel from all over the world (Argentina, China, India etc.) to attend. The hotel turned out to come complete with the one thing every brainstorm needs - an empty swimming pool...

In 'The Art of Innovation' Tim Kelley writes that while most people think they can do brainstorming "I believe you can deliver more value, create more energy and foster more innovation through better brainstorming". I just started the book today, but I was introduced to Tim's ideas about brainstorming several years ago when touring the offices of IDEO - the design consultancy he manages. Since then I've read up on a number of techniques and evangelised about my ideas to anyone I've worked with.

Brainstorming commonly runs up against a number of problems, and most can be dealt with through some simple groundrules and facilitiation. Others are more serious, particularly the one known as 'production blocking'. This is the stage where one person has an idea and wants to talk, but can't because someone else is. For small groups it's manageable, for large groups it's a killer. Since I was faced with around 20 people for this session and had about 60 minutes available for the brainstorm it was obvious that a traditional approach would leave 3 minutes per person - and be very dull for most of the participants.

The solution is a technique called brainwriting. In essence you ask people to write down their ideas instead of shouting them out, and then share and discuss them. It's best combined with a traditional brainstorm (brainstorm for ten minutes, brainwrite for five then back again), but in this case the number of people and time made that difficult. In addition I asked people to structure their ideas into my favourite requirements format - As a ... I would like to ... so that ...

The result was that everyone got to go outside and spend fifteen minutes writing up their ideas. Then we came back together to share, group, and select the ideas. The 20 people generated around 120 ideas in those fifteen minutes, and while many were similar few were identical.

The best place to do the discussion and grouping turned out to be sitting round the empty swimming pool. People could read out their ideas in turn - and anyone with a similar idea could read it out as well. Then the collection of related ideas was grouped together in the pool. Since it was a little windy we had to weight the ideas down with shoes - probably the only time in my career I'll be glad to have my teammates throwing shoes at me....

now, what were we thinking again?

In the end the sharing and sorting produced around 40 batches of ideas, and participants were able to vote for the ones they felt would be most valuable to their office. A good result - and a great process - albeit not one I'll probably ever manage to repeat.

lots of ideas, lots of shoes

May 20, 2006

MySQL -> PostgreSQL

I just changed the Greenpeace instance of the latest Rhubarb code over from MySQL to PostgreSQL. I had a bit of trouble getting the existing instance to work with either suggested (by rails) PostgreSQL Ruby bindings, both gave errors about not being able to find PGConn. Eventually I just recreated the instance from scratch and it works now.

I tried exporting the data from MySQL and importing into PostgreSQL but even using the tools provided in the contrib/mysql directory of PostgreSQL (7.4.8) I kept getting syntax errors. Since the data was just test data I didn't bother trying to fix these. I recreated the user accounts so logins should still work but now theres no data in the system.

Oh, and it's deliberately configured NOT to send email at the moment.

May 19, 2006

We've got to get us one of those...

There's a flash demo of Sahi up and running now at Sourceforge.

I really like the tendency of developers to produce these movies now, because it makes it a lot easier to understand not just what tool a b or c is supposed to do, but how you're supposed to use it. When so many tools arrive as not much more than a selection of scripts and a readme file a rich demo is the next best thing to having the developer next to you.

On which note we'll try and make one for Rhubarb...

Updated login details

I was wrong earlier when I said that you could login to the rhubarb demo as Martin, Testing

The combination you want is 'mlloyd' and 'testing'

Try it here...

http://rhubarb-fngtps.staging.greenpeace.org/

remember this deployment of the system isn't configured to send email, for obvious reasons.

May 17, 2006

How to receive delivery failure notification

We’re well into the second week and we’ve still not fully implemented all stories for the first iteration. I really underestimated the amount of tweaking and real-world testing needed to figure out how to create and send email in such a way as to received meaningful notification for delivery failures. So far, we've learned the following:

  • The Errors-To header is just not going to work most of the time. You have to set the email address you want to receive notification on in the From header. We're now setting the email adress of whoever wrote the message in the Reply-To header so that the receiver can still reply directly.
  • If you send an email to multiple recipients, you will probably not receive a notification if the email cannot be delivered. It doesn't matter if the delivery failed for only one, for some, or for every single recipient. If you want to receive failure notification, it seems that you better send each email to a single recipient only.

Another thing to consider is that it might take up to at least 7 days before a MTA decides to give and you'll get the email returned. Right now, I'm still receiving return email from out first test run last week...

May 15, 2006

Also powered by Greenpeace

This site in the UK (and apparently a few others) runs on the GCMS or Greenpeace Content Management System, which was developed on the OpenACS platform and delivers most of our global webpresence

Like www.greenpeace.org

Nice to see these Open Source things getting used. I have high hopes that Rhubarb will get picked up and used elsewhere as well. Since it's small, compact, easy to install, does a simple job well and so on.

May 12, 2006

Rapidly Developing

The new version of Rhubarb is coming together nicely. You can see the latest version on greenpeace servers by following this link. It doesn't yet send mail, although the development version does....

You can login as 'Martin', password 'Testing' , we'll add a guest account at some stage. Probably once we've built something that lets us add users easily.

So far I'm enjoying the fact that since I've got access to the Fingertips SVN repository I can see how the developments been going. They've also been keeping us up to date with regular updates on their staging server. All in all things seem to be going remarkably smoothly so far.

Next week though we'll be dealing with localisation. Making things work in multiple lanaguges / character sets / encodings is the bane of the international developer. We have ideas about this, but if anyone knows of a nice, lightweight approach to internationalisation do let us know.

May 11, 2006

Google Trends has landed

Well, everyone's talking about Google Trends, so I may as well note that it's got a lot of folks here very excited. Take a look at this result for 'whaling', the big spikes are more or less centered on the IWC meetings, which are extremely dull meetings, where extremely important stuff gets decided amid diplomatic arm twisting, bribery and threats. We're there of course, lobbying, informing, discussing and drawing attention.

The smaller hump toward the end of every year is when the Japanese whaling fleet sets off and in 2005 when we also set off to confront it in the oceans. I'm not sure what this means for the various campaigns, but the sight of eyes lighting up around various departments as we showed this to people suggests that this is all going to prove very useful indeed.

May 8, 2006

We're Advocacy Developers

At least that seems to be the gist of the Advocacy Developers Hub, which among other things documents 'convergences' of other people like us.

Mostly I'm interested in their wiki, which contains the results of some useful looking discussions on e-advocacy and the implementation of CRM systems for non-profits. All things we're thinking quite hard about here at the moment.

Found via AspirationTech

New project, new tools

Today development kicks off on 'Rhubarb on Rails' the project to turn our letter writing prototype into production standard code that can be used around the world. It's a short project - estimated at two weeks of development, and it's being carried out on our behalf by Fingertips, who will hopefully be posting about their experiences of the project on this blog.

Since the project is so short we've decided that we'll be working with Fingertips tools of choice. So that's BaseCamp for project management, and Trac for issue tracking and SVN access. (Copies of the work in progress will be moved to our public SVN server on a weekly basis.)

Within Greenpeace we use RT for issue tracking, largely because we've been using it for so long, and have so much stuff in it that moving away would be hugely expensive. By and large we're not that happy with RT, but finding an alternative that does what we want, the way we want it is proving much harder than expected. So trying out the BaseCamp / Trac combination is a good thing to be doing, if nothing else it might stop Ximon from writing a new bug tracker out of sheer frustration...

(I have been threatening to do that for some time, but 'learning to program' needs to come first...)

May 3, 2006

Greenpeace at Google

About eleven minutes and thirty seconds into his talk on Django to Google Django creator Jason Kaplan Moss talks about Melt. So it's nice to get noticed.

As a more general update we're planning to get back to work on Melt this month, with a target of getting the first public site up next month. During our recent downtime we've been gratified to see Google adding more data to their Google maps, so that the system makes much more sense now when you're looking at results in Europe.

May 2, 2006

Things to go to

I suspect that we'll be hearing more about this in the next few weeks

http://xtech06.usefulinc.com/

Looks like it's going to address a lot of the issues we work with, either directly or indirectly. Now we just need to decide who should be going and to what... Also need to discover whether this is another one of those conferences where 'academic' pricing is extended to NGOs