Today one year ago FYND (Finnish Yles New Drupal) launched it’s first site. Read about the work that went into the preparations here.
It has been a year of shared development when we really have seen the advantages of working on the same distro, and working with open source.
One of the first things we decided on was to work as two teams in a similar way to how NBC Universal works with their Drupal sites (or cells if you want to compare to how Supercell works).
”Clash of Clans and Hay Day were each developed by teams of just five developers. Even now they are global smashes each has a team no bigger than 15.” Ilkka Paananen in Wired Magazine
”Is Five the Optimal Team Size? …the cost per function point of a team of size 7 was $566 and that of a team of size 14 was $2970 – Jeff Sutherland…If you have 3 team members, then you will have 4 communication channels, if you have 4 then you have 9. I think the formula is m-1^2. In my opinion, a small team of 4 or 5 is ideal. – PMHut”
One idea that also was put forward was that we should work as one big team (quite common in big organisations I guess). We did however pursue the idea of having two teams, since we assumed this would make us more focused and productive. It would also allow us to better understand the business goals and needs if we got them independently from two sources (Svenska Yle and Yle Luovat sisällöt).
One year on we are happy with the end results, as the distro has continued steadily on its development path.
The main advantages with two teams and two sites have been:
- Twice the amount of tasks have gotten done – everyone benefits
- Maintaing the distro core is a shared task
- You focus on the task at hand – not a zillion tasks all over the place
- When there has been a module problem, there has been a clone site to compare with
- We can mitigate the risk when a new function or module is activated, as we can share the burden by activating it on one of the sites before activating it on the other
- It has been possible to compare notes, and get an “external” view on different tasks
- External human & tech resources can be shared between the teams
- Cross reviewing (using pull requests)
- Documentation and best practices are better maintained as you clearly see the need and gain. In our case two semi separated teams provide better quality assurance than before
- One observation is that quality assurance has gone up. One theory we have discussed is that it is because the teams see the other team as an outside party. The team members become aware that someone else will suffer if they write bad code or do not test their code. Just like in open source development where many eyes check the code, we are doing the same on a low level.
- Time is needed for co-ordinating
- Time is needed to separate the settings for the two sites, but this would be needed just by the fact that we are running sites with two different languages
- Risk for conflicting business goals – but this has been kept at bay by clearly stating that the purpose of the system is to provide articles publishing according to subjects.
- If you break something you will get blamed
Some of the functionality we have shared over the last year:
- API connections
- New version of the Image Management System
- New meta data solutions for Finto and Freebase
The structure we made on the technical side has worked out nicely, and we have not run into any problems that we have been unable to solve.
We have also found that the business goals are quite similar, and it has not been a problem to agree on changes in the shared core functions.
There has also been spillover in other areas. The content teams can check out what the other teams are doing and get inspired to do the same in their own site.
When there is a request for a new feature the product owner of svenska.yle.fi checks with the product owner at yle.fi/aihe (or vice versa) if they also are interested. If they are we will make it for both SYND and FYND (YDD wide). Depending on the type of issue and how important it is for the sites we will negotiate about which team builds it. Maintenance issues have been shared 50/50.
If it is not a shared goal it will be made for the site that requested it – or it might not get made at all. This is a good checking point, if the feature is not of interest in another site that has almost the same functionality it might not be such a crucial feature after all.
We have a shared issue backlog, but we separate the issues as for both SYND and FYND, or only one of them.
In one month we will celebrate two years with SYND. More about that later.