There is no need to spin your wheels. With a complete set of user journeys, prototypes, and technical specifications, from the Design Lab, the development team begins agile sprint planning. The entire technical team including architects, product owners, and developers will break down the requirements into units of work, planned into a two week work cycle called a “sprint”.

This process is very important, and we encourage clients to be involved, as the team uses these sessions to gain insights into complexities of the use cases they need to solve, they lean on fellow team members to brainstorm the best outcomes, and then commit to a set amount of work for the next two weeks.

Focus is key. To ensure we gain the best possible velocity on the development items, we do our best to avoid interruptions during sprints. To achieve this whilst still having visibility on progress, we enforce a project “stand up” every morning with the team.

These quick sessions are used to raise issues and share progress with the team. Should any problem arise, the project manager assigned to the project will do their best to unblock the issue for the developer.

Test, test, and test again. Testing is a key part of our development process. This phase in most cases runs in parallel with development. We put a lot of emphasis on ensuring the developers write automated tests for each unit of work delivered where possible.

This upfront effort becomes beneficial later in the project when components are brought together and to minimize the risk of regression testing when the project is live. Manual tests are also continuously conducted by the Testing Lab on all units of work.