We do our best work when our team can become an extension of your organisation. We want to know your customer needs and business goals inside out. The way we work enables us to be flexible and adaptable to changing business needs, and our online tools and communication channels will keep you informed of progress every step of the way.

 

An important part of how we deliver is our project delivery process. Based on our experience of delivering digital projects since 2000,  our process has been developed from the ITG Agile Project Framework, combined with other agile practices that are particularly suitable for an agency environment. We invest heavily in agile training for our staff and clients, to ensure everyone is confident about their roles and responsibilities.

​

Our framework.

We ensure that everyone in the team is clear on their roles and responsibilities from the start. We work in multidisciplinary teams consisting of UX designers, designers and developers as well as client-based subject matter experts. As a ITG client you'll be involved throughout the project and will have direct communication with all members of the team throughout the project lifecycle.

 

Our projects have four main stages:

 

Pre-project.

We start by meeting the most senior members of the organisation, to discuss organisational vision, mission and goals for the project. These outcomes are set out in a shared document that we call the project blueprint. This is kept up-to-date throughout the project to provide a single point of reference throughout.

​

Feasibility.

Once there is a shared understanding of what the project needs to achieve, we run a full-day workshop with your core project team and ITG Technical Director and Project Lead, to explore project feasibility. The objective of this meeting is to ensure the project is set up for success and that we are all confident that everything is in place to be able to deliver the project successfully. It's here we ask questions like "Is the brand ready?", "Are both teams ready to start?", "Is the project both financially and technically feasible?".

​

The outcome of this meeting will inform when we collectively agree to start the project. Sometimes there are some further preparatory activities that need be completed before the project can get underway.

​

Foundations.

The aim of the foundations' stage is to do "just enough" design, user experience and technical discovery work before development can start. This phase is typically between two and six weeks in duration. The outcomes for the foundations' stage are fixed but the activities are fluid. We adapt the activities based on what we discover along the way. This enables us to change direction and ensures we only do 'just enough' and no more. Outputs of the foundation phase typically include a testable working prototype, a pattern library and a prioritised, and en estimated list of requirements. This phase includes a variety of research and exploration tasks to ensure we build the right thing and move fast when we start development.

​

Evolutionary development.

At this point, we will start building your site in fortnightly iterations, known as timeboxes. You will identify features for each timebox to be designed and built.

As these features are completed, they will be demonstrated to you to show how they meet your acceptance criteria. Once features are signed off, these can be rolled out to your team and/or customers as and when required. This approach helps generate business value early and often from the build, rather than waiting months for a final "big bang" launch. After the main feature development has finished, we will continue to work with you to fix issues, respond to new feature requests and ensure your site is secure and fully optimised.