Sprints

What is a sprint?

In the CiviCRM community, sprints are times when people get together in the same time and place to work on improving CiviCRM.  We work on many different topics and you don't need to have technical skills or be a coder to attend a sprint.  Some of the things we do include:

• writing new features
• fixing bugs and writing tests
• writing documentation
• improving community processes
• creating marketing materials

Sprints are informal and we focus on collaborative working and peer learning. While you will learn a lot though attending a sprint, they aren't training events.   They are a way to contribute to CiviCRM and the focus is on being as productive as possible for the time that we are together.

Notes from sprints

You can have a look at these notes that we create at each sprint.

• 2009-05 May Tahoe book sprint (final report to OSI)
• 2009-11 Unit Testing Code Sprint - San Francisco November 2009
• 2010-04 April Tahoe book sprint
• 2010-04 CiviCRM Code Sprint
• 2010-09 CiviCRM Code and Test Sprint - New York September 2010
• 2011-08 CiviCase Sprint Plan - London August 2011
• 2011-08 Code, UI and Usability Sprint Plan - London
• 2011-08 Code and Usability Sprint Schedule
• 2011-09 September Bourne book sprint
• 2012-02 Ongoing notes from the April, 2012 sprint
• 2012-04 April Woolman documentation sprint
• 2012-04 Translation and documentation sprint 16th-17th April 2012
• 2012-08 Bourne sprints
• 2012-09 Butcombe and Apeldoorn book sprint
• 2012-09 Pre CiviCon London sprint
• 2012-12 Toronto CiviAccounts Sprint
• 2013-10 London sprint
• 2015 Denver Sprint
• Before conference sprint (CiviCon SF 2013)
• Woolman Sprint 2013

You may be interested in how to organise a sprint.