A messy Team Interactions Modeling diagram, which doesn't follow the rules, and tries to represent the full enterprise

The most important part of Team Topologies is also the one most people overlook

Last year, during FastFlowConf, Matthew Skelton answered questions about what had changed/evolved since the Team Topologies book was published. In his own words, they (both authors) should have emphasized the team interactions and the evolution of the topologies over time as central themes for achieving a fast flow of value. We sometimes hear criticism that the...

Adopting an Intentional Strategy for Managing Team Cognitive Load

I recently created an online cohort-based course, Effectively Manage Team Cognitive Load. Since the release of Team Topologies book, I have adopted its language and principles in my consultancy practice, supporting organizations in their digital transformation journey. I've noticed in the field that more people are aware of the effects of unmanaged Team Cognitive Load...

My observations on the effects of CAPEX and OPEX on organisational behaviour

During my career, I’ve been involved in different digital transformations, ranging from financial to telco institutions. Those digital transformations aim to evolve the operating model (or parts of it) and bring digital capabilities to the forefront. As part of it, new ways of working are implemented, which leads to new practices to manage capabilities. You might recognise those digital transformations by other names, such as Agile transformation, DevOps transformation, or cloud transformation.

Thoughts on organizing architecture

When being part of an enterprise, you will meet different architects on any given day. The first one introduces itself as a solution architect, the other calls itself the enterprise architect, and they both mention a domain architect. It might feel like different names for the same thing, and perhaps even a bigger question, do we even need all of these different architects? Should the team not be able to make all of these architectural decisions by themselves?

Using Team Topologies to discover and improve reliability qualities

Team Topologies is the work of Matthew Skelton and Manuel Pais, and I use it as part of my job. From a sociotechnical perspective, a team-first approach is paramount for any organisation and helps to decrease the accidental complexity. As such, I’m often asked ‘How can we operate in DevOps?’ or ‘How can I have a reliable service to deliver value to my customer?’.

Build and secure containers to support your CI/CD pipeline

There are 2 systems in any company that are critical: the payroll system, and the CI/CD system. Why? You may ask…
If the payroll system doesn’t work, people will leave the company and the company (may) face legal problems; the CI/CD system is the gateway to production. If it is down and there is a bug in production, it will affect your business; loss of revenue, loss of customers, loss of money, just to name a few.

Using Flyway and GitLab to deploy a MySQL database to AWS RDS securely

One of my passions is to be a trainer. Sharing knowledge, meeting new people, be continuously challenged, it fuels my brain, and I’m always learning something new. I’m creating a new training for software development teams, and one of the components is a MySQL database. Also, I’m using a public cloud provider (in this case AWS), and Xebia provides accounts to cover training, workshops and our own experiments.

Learning DDD as a team

A few sprints ago my team and I decided to invest heavily in Domain Driven Desing. We already started to develop the new microservices in a DDD fashion, with our domain as the central component. However, we wanted to formalize it and move the old microservices to this new paradigm.

TechDays NL 2017

he first conference that I attend since we arrived in The Netherlands was the TechDays NL 2017. The conference is sponsored by Microsoft, and it’s one of the most significant tech events in the Benelux area. However, even being sponsored by Microsoft, other streams of the industry were present, showing that Microsoft is no longer "the evil".