Skip to content
  1. We help small teams achieve big things.
  2. Our Technical Fellow just became a Microsoft MVP!
  3. We run the Azure Weekly newsletter.
  4. We just won 2 awards.
  5. We just published Programming C# 8.0 book.
  6. We run the Power BI Weekly newsletter.
  7. Our NDC London 2020 talk is now available online!
  8. We are school STEM ambassadors.

Endjin's DevOps Delivery process is based around weekly iterations, delivering code, specifications, infrastructure templates and documents directly into customer-owned source control and cloud environments.

At the end of each weekly iteration, we'll provide a project update and demo video detailing what we did, why and how we did it, whether it was successful, and our recommendations for the next iteration.

From complete systems, to isolated features, or proof-of-concepts, we de-risk your most complex requirements through reliable, predictable delivery.

DevOps Delivery Process

The DevOps Delivery Squad

You'll work directly with one of our principal endjineers, providing day to day oversight, and an executive point of contact for the project, but every project benefits from the skills and experience of our entire team.

The squad will consist of a blend of different roles at different stages of the project (architects, engineers, test engineering, DevOps, and infrastructure), drawn from the entire endjin team, depending on the type of problem that needs to be solved.​

Specification based development

​ Core to endjin's approach to successful delivery is the development of executable specifications.

We'll start writing these specifications at the beginning of the project, in conjunction with the business owners of the system, to develop our understanding of what's being built. Then, as the solution is implemented, we write code to sit behind those specifications and test that the assertions they make are true.

The implemented specifications are embedded into the software delivery process as part of the build and release pipeline. Once added, they are executed every time a change is made to the source code to ensure that no breaking changes are introduced.

The full set of specifications acts as living documentation for the system, as well as becoming a vital quality gate to ensure that the system behaves as intended.

This process continues during implementation as we refine our understanding and make decisions about how the system should function.