Learning from others: Textbook sprinting in New Zealand
Note: this is a cross post from my personal blog at ClintLalonde.net.
I’m picking up steam on researching and planning a possible textbook sprint here in BC as part of the open textbook project. While I am still in the research stages of how this thing might work, I’m feeling more confident that with the right people involved we can pull off a textbook sprint.
Just before Christmas I had a chance to speak with Erika Pearson at Otago University in New Zealand. In November, Erika ran a textbook hack to create a first year Media Studies textbook and during the course of our chat I got a better understanding of some of the logistics involved in pulling it together. I am appreciative of her time and willingness to share, and look forward to the cookbook they are planning on releasing later this spring on how to organize a textbook sprint. Here are my notes from our convo.
- Timeline for the entire project was about 3 months (project plan and a more detailed timeline are posted).
- There were about 10 participants involved in the Otago sprint. Surprsing to me, most of them were distributed, so communication was virtual done through Google Hangouts.
- Most of the authors were actually grad students which turned the activity into a powerful authentic learning experience (she’s talking my language here).
- Authors had a dual role – writing & peer reviewing what other wrote.
- Erika stressed the important role of designating an OER librarian to help source and attribute resources needed on the fly. A strong CC bg with knowledge of CC & educational repositories.
- Prior to the sprint, the authors met virtually & came up with a rough outline of the book, including topics and chapters. This was based on course outlines shared by faculty. In retrospect, Erika said she wished that there would have been a bit more pre-work done ahead of time and that everyone came to the sprint with draft chapters that could then be honed and worked on over the actual sprint. Note to self: do as much work ahead of time. By the time we all get together face to face, a good bulk of work might already be done.
- Write in sprints. Erika’s project broke their day into 90 minute writing chunks, followed by a period of peer review. Iterative development. Note to self: if we use PressBooks (which I want to do if this goes ahead) what kind of workflowing tools do we have/can we add to facilitate a review process?
- There were a number of virtual lurkers in the hangout. Note to self: make external participation possible (video, chat, event hashtag)
- Have a note taker to record what needs to be done as it comes up. They kept a spreadsheet of tasks that got added to as the sprint progressed.
- A fact checker would be a good role to have. Someone to research as problems/disputes/questions of content arise so that authors don’t get bogged down in surfing for answers to questions.
Erika’s project was supported by Creative Commons.
- Sprint is a bit of a misnomer as I think most of the work will be done ahead of time in the weeks/months leading up to the actual sprint. Therefore, trying to find a time where faculty have at least a few weeks leading up to the actual event to work on the project will be important. Perhaps early June might be a good time?
- We’ll need a few pre-event virtual sessions of participants, including some technical training on the platform, setting up the structure, and draft writing. Perhaps 3 seperate pre-event synchronous sessions?
- The actual sprint itself. If we can get most of the authoring work done ahead of time, 2, maybe 3 days would be what we would need together. Anything longer than that might be a tough f2f commitment for some to make. And, if the actual days are as intense as I think they might be, any longer risks burnout.
- Subject area. I have one in mind and I have contacted the head of the provincial articulation committee for that area to get his input & feedback. It is an area that currently has no existing open textbook available, but (I suspect) quite a few open resources available. And the subject area is perfect to create something very Canada-specific, which may not get created otherwise by some of the more U.S.-centric projects.
- A synchronous PressBooks code sprint. This is something Brad Payne and I have been discussing. Alongside the book sprint it might be useful to have running parallel a PressBooks code sprint. There are a number of enhancements that could be made to PressBooks to make it a better tool for collaborative textbook authoring, and having the input of users at the time they are actually using the tool might be invaluable. And it could be a real catalyst to improving participation rates among developers for the project. If we can find some WordPress developers interested in working with us on improving PressBooks, this could be a very useful exercise as it would be great to see more developers participate from higher ed.