We work on-site alongside our clients, and also have a software delivery center in Milton Keynes, UK. Our clients reap the benefits of shared lessons learned across projects and we gain efficiencies through our standardisation of tools, technologies and approach.
We follow the Harlan Mills 'Surgical Team' model where a senior engineer is the point-person, working on the critical parts of the software and delegating activities to the rest of the team. The delivery teams are supported by administrators at JUXT who provide the environment for a team to thrive in, as well as taking care of contractual and reporting matters.
JUXT is an opinionated engineering firm, with technical direction coming from the founders, one of which is our Technical Director. This means that for each project we don’t start completely afresh having to debate each and every technical decision. At JUXT we can hit the ground running and deliver value to our clients more quickly.
Everyone in JUXT helps each other by advising on technology choices and providing insights where they are needed. We will match the needs of our clients to the right individuals involved, but we also have strength in depth, so that we are able to rotate a person in with a specific skillset when needed.
We use a lightweight Agile process, valuing fast, iterative feedback. Our starting point is for engineers to communicate directly with the client and we evolve support mechanisms - such as business analysts and project managers - as needed. We deploy often, provide regular showcases, and we encourage daily stand-ups. We use best-of-breed tools such as Clubhouse to provide transparency and to manage project work-streams.
We welcome external audit of our software projects, from security to architectural reviews. Our technology platforms have been externally pen-tested and we manage long term services that conform to various regulatory compliance regimes.
Our developers work across the stack, including provisioning cloud infrastructure, back-end, database administration, front-end, and mobile applications. This means that we do not need to divide a development team into sub-teams that will require a higher operational overhead to synchronise efforts.