Way of Working

The Way of Working be­gan as a de­fined process around the ag­ile de­vel­op­ment frame­work, which has slowly grown into its own set of prin­ci­ples, tools and guide­lines. Where the ag­ile method­ol­ogy sets out a vi­sion, the Way of Working cre­ates a more de­tailed frame­work for de­vel­op­ment teams to fol­low. Broadly speak­ing, the Way of Working processes and prac­tices have been ap­plied to: Develop bespoke web and mo­bile applications, Migrate legacy software, Maintain and en­hance exist­ing products, Develop with teams of 3-9 people, Release projects fre­quently, Sustain and support projects and their customers

We keep you on track

Every software project has four key phases: Brief, Scope, Development and Support. Projects will nav­i­gate these in different ways, and it is not designed to be treated as a linear process. The strength in this process is its ability to adapt to different use cases, while still maintaining a reliable and consistent process to guide the way.

Embracing transparency

While the Way of Working has been designed for software development agencies working on external customer projects, the same principles and tools can be applied to internal development projects.