We use a tool called Jenkins to do Continuous Integration (often referred to as CI). Without getting too nerdy, all that means is that we have a server sitting in the background continually checking our work. Each time someone changes something, the Jenkins CI server “builds” a completely new version of the site and runs some tests over it.
Read MoreCategory / How we do
How a project gets tested and deployed with GitFlow
We’ve started moving all of our projects over to GitFlow, which is a way of managing all the complex changes and workflow involved in making, testing and publishing digital projects. How we manage our test and deploy workflow has changed massively over the years. Many moons ago we started off with no tests, manual publishing …
Read MoreClicktale Review – how the technology really works and why it didn't for us

A review of how Clicktale technology works and some real world issues that you might face when implementing or using Clicktale
Read MoreJira priorities: the story of Team Six and The Iceberg

We use Jira to keep track of all of our tasks – without it we’d be overwhelmed with the sheer volume of “stuff” you need to keep track of on a typical project. For each of our projects, the client can email in issues to our team via a project email address. These emails don’t …
Read MoreBenchmarking the perfect project: what makes one project better than another
A few months ago, we started working with a project management coach. The aim was to try to improve the way we do things. We already have lots of quite tight processes for our technical work, but didn’t have any around managing all the different things that our project managers do. Each week, we’ve been …
Read More
