Software Development Best Practices

We want to be as dependable as we can be and we achieve that through good Software Development Best Practices.

Software Development Best Practices

Software Development Best Practices are key to us being seen as reliable and trusted which in turn helps us to develop a long term relationship with you, which is at the heart of our business.

We believe that a strong software development process is central to being able to provide a mature and repeatable engineering function.

Shared Documentation

All our projects begin with a technical requirements document and a corresponding technical specification document. They are often modified throughout a project’s lifecycle as new requirements come to light or are better understood. Crucially they provide all stakeholders with an agreement as to what can be expected at a given point in time.

Shared Source Repository with Version Control

All our projects use a shared repository that all stakeholders can access at any time. Primarily we use Git but we’re agnostic if your project has a different source control system such as Perforce for example.

Continuous Integration

We believe that having access to regular (often nightly) and stable builds is key to visible progress and confidence – both in us and our development process. We use Jenkins for our projects but as with source control are happy using your favourite tools too.

Constant Communication

This is central to our relationships with clients and something we as key to developing long term partnerships. Even if it’s just say everything is ok, we’ll keep in touch at a regular interval that’s comfortable for you.

Shared Agile Progress

We’re happy to use an Agile progress or dashboard tool of your choice to feedback our progress through your project backlog. Internally we use Trello for our projects but are familiar with many others such as Jira, Asana etc.