The team of this project included myself as lead developer, another developer, a designer, and a project manager.

Once the design was completed, I planned out the best backend architecture to enable the client to manage the content easily, as well as helping the build to happen efficiently. Whilst I did this the other developer started on theming the main components of the website.

Once I completed the core of the backend, I began theming along with the other developer. We worked by creating reusable components maximising efficiency.

It was important to have consistent and frequent communication between the teams to ensure everyone knew what was happening, and this was particularly important within the development team. Communication between the backend and frontend teams was especially important to make sure our work aligned.

We also performed code reviews throughout the project. At the end of each week we would have a look at each others code and see why they had done something and if there were potential ways to improve. This worked extremely well and ensured the code could be easily understood by each developer, was efficient, and helped to prevent mistakes.

Overall, Anthony Nolan was a straight forward build. There were a few complexities in making sure taxonomies where set up correctly and worked well with the content. On top of this it was very important that the website had AA accessibility compliance - which isn't necessarily a complicated thing to do, but requires a lot of time and communication with the designer, as well as teaching the client of the importance of content entry to keep it at AA standard.

Once we had finished the build, thoroughly tested across all devices and browsers, it was ready to go to the client.