Structuring team development
Every development team has their own way of working together. Here at TMW, we are no different (other than perhaps having an unhealthy obsession with cake).
The Creative Tech team at TMW was put together just over 18 months ago, back in April 2012, when Zander and I joined the company. Before that point, there was little structure in the front-end development work being done; no documented guidelines, no frameworks.
Not having these development tools in place before, though not ideal, gave us a massive opportunity and was one of the reasons I relished taking on the role at TMW. We had the opportunity to shape the way our team would work right from the start, which is usually a situation only afforded to start-ups.
Our aim was, and still is, to put just enough in place to ensure the whole team is working on the same page. Both Zander and myself had worked on projects where something as basic as the core structure could become a major stumbling block to anyone else joining the team and we wanted to rectify these types of issues right from the start.
The team has now grown to 6 people – a mix of Creative Technologists and Interactive Developers – and the processes established when there were only 2 of us in the team have only needed to be tweaked during that growth, rather than completely overhauled.
So I just wanted to share the tools we have used to help our team, which could potentially help any development team of any size. I'll also take you through some of the resources we've started to build up that assist in our development efforts, and that we've been making openly available.
Define your way of working
One of the first things we did was to draw up a set of guidelines and standards for how we develop.
No matter what the size of the team, you should know what standards and code conventions you are all developing to, ensuring that they're consistent. This means that whatever the project, consistency is key; it should look like code that a member of your team has written, instead of requiring complex deciphering. As a team, decide how you want to standardise this and document it.
Writing documentation from scratch can be a barrier for some, so instead take an existing set and adjust it to your needs. Our TMW guidelines took inspiration from Isobar's 'Front-end Code Standards & Best Practices' and Harry Roberts 'CSS Guidelines', using the bits we agreed with and building on top of them with our own documentation.
Documenting these decisions can have all sorts of benefits. New starters immediately have something that informs them on team development standards. It also helps to control the output of freelancers, as it acts as a reference for the standard of code you expect them to create.
Above all, it acts as an evolving reference point for your team; you can refer anyone to it so that they can find details of the way in which you work. We've found this useful when hiring to show potential team members that we care about the work we produce, as well as the fact that it's an open document, which allows clients to see the the way in which we work.
Structure your codebase
Another issue we have come across in the past is front-end structure. When editing a project that another team member has created, you should know where things are. It should never feel like you're having to play a game of 'guess where the CSS and JS files are hiding' – a game I recommend you avoid playing with your family this Christmas.
We didn't want the bloat of using Bootstrap, while also wanting a level of control over the evolving structure of our projects without relying on a third party framework. Kickoff is therefore more minimal, made to create consistent structure rather than enforcing coding style.
We actively maintain Kickoff, looking at aspects of other frameworks and changing parts of it to keep up with the evolution of front-end development.
Like documentation, not everyone will want to, or have the time to, maintain their own framework. What I would advise is that you choose a consistent framework across your projects. There's little point in using Bootstrap on one project and then Foundation on the next. You'll just end up with lots of projects with inconsistent structures, making maintaining them harder.
Re-use what you've built
Something we've started to do more as the team has grown is to make our code more portable across projects and between team members, so we can reuse code snippets more readily in the future.
We'll be writing about some of these in more detail in future posts, but what I want to emphasise is the importance of making the effort to make your code portable between projects and team members. Even if you work mostly on your own, spending the time to make a useful piece of code portable and putting it somewhere you can easily access it can save hours down the line.
Within a team, the hardest part of this is actually knowing what has been built previously that you can then use yourself. Github helps us manage this, as it allows us to commit code we think could be of use on any project and all of the members of our team will get a notification and know where to find it.
Building this culture into your team will reap dividends, and is something we're working hard on within our team here at TMW.
Build for the future
The main goal is always to build with the future in mind. What would I care about if I got pulled onto a project half-way through? The aim is to help deal with the common frustrations we all feel when in this situation.
Keeping things consistent means that people are better oriented with the project style and structure at whatever point they start working with the codebase. I always know where the Grunt file lives, where the responsive mixins are located and where typography related CSS styles go in our SASS structure.
Some of these may seem like small things, but they can all add up to save a lot of time down the line. They may take time to put in place, but I can assure you it'll be worth the effort.