What’s new?
Here’s a quick rundown of how things are going to happen:Fixed focus
A sprint will now always follow a certain focus. This focus is defined upfront and will align with the current TYPO3 CMS roadmap.You can request any ticket to be added to a sprint by getting in contact with <link>Mathias Schreiber or <link>Anja Leichsenring via email or preferably on Slack, our communication platform. To get your Slack invite, send an Email to <link>admin@typo3.org - please keep in mind that we do not want the invites, they are a simple technical limitation of the service we are using.
Everybody is welcome to join here.
Dedicated Scrum Masters and Experts
In our efforts to make our development and release scheduler more agile, we noticed that we need some people during a development phase and on a dedicated code sprint that simple enable the other attendees to code what’s on the desk - in an agile manner we call them Scrum Masters. Sometimes this means that these people just help getting people up to speed with Git and Gerrit, keep the sprint overview of the open tasks and remove any obstacles in the coders way in finding experts to make the decisions.The TYPO3 CMS Team will send dedicated Scrum Masters and Experts to a sprint.
By doing so we can maintain a high velocity during the sprint and get more stuff done in less time. Also we will have experts on location in the respective fields on which the sprint focusses. This means you won’t hear “We have to ask XYZ on that next week” during a code sprint because XYZ is already there. But even better - when you have a certain topic you would love to see taken care of, you can become a guest scrum master during a sprint. You should have proper knowledge of agile workflows and be able to guide a team of motivated people. In case you need support, the CMS Team Scrum Masters will be there to have your back.
Multi-Sprints
We are trying out something new in January: Running two sprints in parallel at two different locations at the same time.By doing so you will get a larger variety of locations to pick from as well as it makes it easier for us to get more people involved than before. Also this gives us the opportunity to work on several topics at the same time and no longer limiting ourselves.
Both locations will be connected via Slack and maybe a live-video feed and who knows… maybe a little competition here and there?
Stay tuned.
Why attend a sprint?
There are a lot of good reasons to attend a sprint or to let your employees attend one. First of all, it’s a great experience. You meet people that are passionate about the same things as you are, get things done and most importantly - it’s a lot of fun (and work, but shhhhhh). Being at a sprint can also help you shape the product towards your needs. Simply talk to one of the experts and share your ideas and thoughts. Sending your employees to a sprint will also give you a technical edge because why read about a feature in the documentation when you could create one yourself?And finally, sending your developers or project managers to a sprint or hosting one will result in a lot of positive buzz about your company. Travel and accommodation can be reimbursed by the TYPO3 association.
How to host a sprint?
Hosting a sprint is easy. Just get in contact with <link>Anja Leichsenring, <link>Mathias Schreiber or <link>Benni Mack. The prerequisites are lower than you might think. Normally, a sprint location should be able to host between 8 - 20 people. A solid internet connection is mandatory (who would have thought?). Having organisation tools like whiteboards, flipcharts and a FullHD TV are a big plus.Since sprints tend to not stop on working hours it is near-to required to have someone on location who may close the doors late at night when the sprint day has finished. We are constantly looking for people willing to host a codesprint outside of Germany - we’ve seen so much of this country…. we eagerly want to see something else. So if you are located outside of Germany, please consider hosting a sprint :)
Dates and preliminary locations for 2015
Date | Location | Focus |
Jan 29th - Feb 1st | Essen, GER & Berlin, GER | FAL & Core Cleanup |
Mar 21st - Mar 28th | Festenburg, GER (during T3UWX15) | Frontend / Content Elements |
April 30th - May 3rd | Rosenheim, GER, in2code GmbH | Extension Management |
Jun 15th - Jun 18th | Paris, FRA, [apply to host] | Backend UI |
Jul 13th - Jul 16th | Nuremberg, GER (ACME15) | Active Contributor Meeting (internal) |
Jul 16th - Jul 19th | Nuremberg, GER (during T3DD15) | tbd |
Sep 12th - Sep 16th | Espelkamp, GER, Mittwald | preparing CMS7 LTS |
Nov 4th - Nov 8st | Mönchengladbach, GER, web-vision GmbH | kicking off CMS8 |