A recent paper published by CETIS. Abstract below, the full paper is here:
Its a very good article except that it makes one small factual error. Book Sprints were not inspired by Agile programming methods. The methodology was largely inspired by Unconferences and in particular those I participated in that were facilitated by Allen Gunn (Gunner).
Writing in Book Sprints, Phil Barker, Lorna M. Campbell and Martin Hawksey, Amber Thomas
This lightning talk will outline a novel approach taken by Jisc and Cetis to synthesise and disseminate the technical outputs and findings of three years of HEFCE funded UKOER Programmes. Rather than employing a consultant to produce a final synthesis report, the authors decided to undertake the task themselves by participating in a three-day Book Aprint facilitated by Adam Hyde of BookSprints.net. Over the course of the three days the authors wrote and edited a complete draft of a 21,000 word book titled “Technology for Open Educational Resources: Into the Wild – Reflections of three years of the UKOER programmes”. While the authors all had considerable experience of the technical issues and challenges surfaced by the UKOER programmes, and had blogged extensively about these topics, it was a challenge to write a large coherent volume of text in such a short period. By employing the Book Sprint methodology and the BookType open source book authoring platform the editorial team were able to rise to this challenge. Although BookType allows authors to restrict access to their works in progress, the team decide to produce the OER technical synthesis book as an open draft. This meant that colleagues who were not participating in the Book Sprint were able to monitor progress, and read and comment on the draft as it grew.
Book Sprints are essentially short intense facilitated writing retreats, which bring together a group of four to twelve people along with a facilitator to produce a book in three to five days. The model involves little or no pre-production, and the aim is to have a published book (in ebook and print-on-demand formats) by the end of the Sprint. Book Sprints are not primarily an exercise in collating content from existing sources, the majority of the text is original material written during the Sprint, however in the case of “Into the Wild”, some material was incorporated from relevant blog posts. Although the Book Sprint methodology was originally designed for producing open source software manuals, particularly FLOSS Manuals, the technique has now been adopted by other non-technical domains, including academic disciplines. For example, a group of Finnish high school teachers recently wrote a maths textbook during three-day Book Sprint (Harmon, 2012).
We believe that the facilitated Book Sprint approach and the open source BookType software will be of relevance to colleagues who are interested in developing books for or about open educational resources, particularly where they have the necessary background knowledge and access to content that can be adapted and reused, but lack the time or support to marshal these resources into a coherent, professional product.
In this paper we will outline and reflect on our experience of employing the Book Sprint methodology and explore its applicability to the creation of open educational resources.