The real secret to successful Shared DevOps

Scroll for more

The real secret to successful Shared DevOps

In conversation with: Joris Bruijn, DevOps Manager at CaseNine

CaseNine uses a Shared DevOps structure. What does this setup entail and what benefits does it offer you as a customer? Joris Bruijn, Lead Developer within CaseNine's DevOps team, explains it briefly and powerfully.


What are the key features of Shared DevOps?

"Where previously as a customer you were assigned one permanent developer for a development project, in a Shared DevOps setup you get a pool of 5 developers, for example, which can be alternated between. In fact, this gives you access to 5 FTE developers. Within this pool, there is the flexibility to switch developers. Moreover, a project team can dynamically estimate and adjust hours: this also provides additional flexibility during the development process. "

What advantages does this offer?

"Scalability is an important advantage: you can grow relatively easily if the project calls for it. The other way around is also possible: in quiet times you can scale back. Of course, you need a familiarisation period per developer: in this respect Shared DevOps does not differ from a traditional set-up. What is distinctive is that at CaseNine we take care of the necessary training period. So as a customer, you don't have to worry about onboarding. With Shared DevOps, as a customer you also benefit from continuity during the development process and you have more knowledge at your disposal: the knowledge pool is larger. To ensure continuity, we make sure that a regular developer is always up to date with the overall project status: what is going on at the customer and which stories are currently being worked on. We also often have a colleague working in the background: again, for the sake of continuity."

What do developers notice about this setup?

"For developers, Shared DevOps offers much more variety. After all, you can work on different projects. You work in a dynamic team that is well attuned to each other and helps each other well. Moreover, there is a large degree of transparency: such an open structure is obviously important for Shared DevOps to function optimally. Each team member has his or her own responsibility. At CaseNine, the development team consists of a combination of junior, medior and senior developers. This creates an environment where you can develop yourself and learn from others. In addition, each developer attends Salesforce training, so everyone has in-depth and up-to-date knowledge."

Interested in what we can do for you?

Contact our experts directly. We'd love to hear from you!

Want to learn more about CaseNine Shared DevOps? Download our presentation today.

Joris Bruijn


Joris Bruijn works as DevOps Manager at CaseNine. He deals with the various projects on a day-to-day basis and continuously researches how to improve the development processes within CaseNine. Joris works in the team of IT'er s responsible for internal development and app developments, among other things. In addition, he supports key customers.

Receive notification when a new blog arrives

We would love to keep you updated on the latest news.