When you subscribe to Furtherfield’s newsletter service you will receive occasional email newsletters from us plus invitations to our exhibitions and events. To opt out of the newsletter service at any time please click the unsubscribe link in the emails.
All Content
UFO Icon
Irridescent cyber duck illustration with a bionic eye Irridescent cyber bear illustration with a bionic eye Irridescent cyber bee illustration
Visit People's Park Plinth

Sprint As Process

Helen Varley Jamieson

Helen Varley Jamieson’s account of working collaboratively in Madrid at the Eclectic Tech Carnival. On a ‘sprint’, with five women coming together for a week to rebuild the group’s website, physically & remotely.

In the last week of June I went to Madrid for the Eclectic Tech Carnival (/ETC) website workweek – the collective effort of five women coming together for a week to rebuild the group’s website. This is sprint methodology, a concept that I first met in Agile software development, but one that is being increasingly applied as a successful creative collaboration methodology. During the workweek I blogged about the process and this article is an assemblage of the blog posts.

Thinking about the concept of the sprint, I realised that over the years, I’ve participated in a number of theatrical “sprints” although we didn’t call them that. In fact it could be argued that the normal development process for theatre productions in New Zealand is the sprint – a three or four week turnaround of devising/rehearsing/presenting. Except that it doesn’t usually continue the Agile process after the first sprint – evaluation, refinement then the next sprint and iteration – and as a result, the work is often undercooked. But theatre projects that better fit the sprint analogy are some of the workshop-performance processes that I’ve participated in at theatre festivals, where a small group comes together for a few days to create a performance, then some time later meets again in another situation, perhaps a slightly different configuration of people, for another sprint. Each sprint generates a stand-alone performance or work-in-process showing, as well as contributes to a larger evolving body of work that forms the whole collaborative project. Two such projects that I’ve been part of are Water[war]s and Women With Big Eyes (with the Magdalena Project).

with the Magdalena Project

Recently I participated remotely in a Floss Manuals sprint, developing a manual for CiviCRM (which is something that I use with the Magdalena Aoteroa site). In this sprint, a group of about 15 people met somewhere in the USA to create a manual for CiviCRM. A few more of us were online, doing things like copy-editing the content. Most of the time there were people active in the IRC channel, chatting about the project and other things going on around them, so I got a sense of their environment, time zone and the camaraderie generated by the intense process.

Sprinting seems like a very logical and effective way to work in many situations: in software development, where each sprint focuses on specific feature development, and allows for a lot of flexibility and adaptation as the project progresses; in theatre, where limited resources make it a practical way to work, and the time pressure forces us to be resourceful and imaginative and also with networks, such as the Eclectic Tech Carnival, whose organisers don’t get to meet physically very often. It also makes sense in the context of our hectic lives, to block out a week or a few days when we agree to put everything else on hold and commit to intense, focused work instead of trying to juggle and multitask, with deadlines pushing out and out.

Sprint as Process

By halfway through the second day of the workweek, the wiki we used to plan and manage the project was filling up with tech specs, user requirements, design ideas, etc. We were getting encouraging emails from others in the network, and chatting to each other across the table and in the IRC. After lunch we did the new Drupal install and things seemed to be moving forward quickly in an organised and collaborative way.


Wednesday afternoon and the heat was oppressive; I put a little rack under my laptop because she was so hot, and my hands were too sweaty to use the trackpad. It wasn’t just Madrid’s weather that was making me sweat – we’d all been working hard on the new site since our late start in the morning (following on from a late night …). Agnes was busy developing the theme for the site, Aileen was working on profiles and user roles while Donna and Amaia were trying to configure mailing list integration and I was using the command line to drush download modules – much easier and quicker than the process of downloading, unpacking, ftp-ing and installing! And very exciting for me to use the command line, which I generally only get to do when hanging out with the /ETC crowd.

Working on Site

We were in that murky middle phase of the process: we’d done a lot of groundwork in terms of defining users, content types, general structure and the functionality required, but everything was still very bitsy and amorphous. But the installation of the test site had happened very easily yesterday, using drush, so that meant we now had something tangible to work with.

Working with Drupal can be pretty frustrating; it seems that every step of the way, another module is required to do what we want – then that module requires other modules, and then every little thing has to be finely configured to work just right with every other piece of the puzzle. From my previous experience with the Magdalena Aotearoa site, I knew we are doing a lot better this time in terms of defining what we need first, but some things we just can’t define until we know what’s possible, which we don’t really know for sure until we actually try it. We *think* we’re going to be able to do everything we want, but getting there isn’t simple. Also, the naming of different components and modules is sometimes ambiguous or confusing – the documentation ranges from really clear and detailed to non-existent. And some things just didn’t seem intuitive to me.

But, with five brains and our different complementary experiences and skills, I was still confident that we would have a new site by the end of Friday; maybe not a completely finished one, but a web site is never finished, is it?


On Friday morning the heat broke with a thunder storm and cooling welcome rain, but it didn’t last long. For some reason I woke up at 7.30am, ridiculously early as we hadn’t gone to bed until 2am. But I was wide awake so I enjoyed a couple of hours of quiet before everyone else awoke, drinking coffee and answering emails. The day before, Agnez and I had got up early to do yoga on the terrace, but the intense rain prevented that on Friday.

Final day

The test site was up and some of the others not present in Madrid were looking at it and trying things out. We’d solved a lot of problems but there were still a number of things not working. I had learned heaps about Drupal in the previous four days, particularly about organic groups, roles, permissions, and views. Altogether it is potentially incredibly flexible and powerful, however it takes time to work out how things need to be done and sometimes it is a confusing and circular process. Changing a setting in one place can stop something in a completely different place from working. However the combination of skills and experience between the five of us meant that usually one of us had at least an idea about how to do things and a couple of times we drew on external expertise via IRC or email.

On the last day, Agnez worked on finishing the theme while Aileen and I tried to work out why our groups are no longer displaying in the og_my view, and how to make the roles of group members visible. Donna had found that mailhandler and listhandler didn’t seem to be a practical way to integrate our mailman lists with Drupal after all – for the time being we’ll stick to the old system – and Amaia had been working on a way to create a programme for each event. The idea is that each /ETC event can be created as an organic group with the organisers having control over content and members within that group, but not being able to edit the rest of the site content. By Friday, we had this working pretty much how we wanted it.

We had planned a barbecue to celebrate the end of the workweek, but the rain prevented that. Instead, we ate inside then took turns to suffer humiliation and defeat with Wii Fitness (Amaia had clearly been practising!). In fact it wasn’t really the end of the sprint – rain again on Saturday morning meant that we decided to keep working longer and only went into the city in the afternoon, for a wander around and then the Gay Pride parade. On Sunday as we began to scatter back to our different parts of the globe, the site was still not live, as we were waiting for more feedback from testers and the finishing of the design themes. However, the site is essentially functional and should be live very soon.

The sprint process enabled us to achieve a considerable amount in a short space of time, sharing our knowledge and developing our skills. We also had great conversations over meals, explored Madrid and Colmenar Viejo, learned how to make Spanish tortilla, attempted a bit of Spanish, went swimming and did yoga. I even fitted in a performance on the first night, with Agnez, and dinner with friends another night. It’s amazing what you can do when you put the rest of your life on hold for a week; the only downside is the catching up afterwards.