article thumbnail

Thoughts on organizing architecture

Xebia

The scope of a team often concerns a limited number of components, microservice or other functionalities. The decisions made on organizational level typically offer boundaries and guidelines towards the organization. As we move up to domain-oriented units, business lines and enterprises, we see an increase in the complexity.

article thumbnail

Thoughts on organizing architecture

Xebia

The scope of a team often concerns a limited number of components, microservice or other functionalities. The decisions made on organizational level typically offer boundaries and guidelines towards the organization. As we move up to domain-oriented units, business lines and enterprises, we see an increase in the complexity.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

AoAD2 Practice: Whole Team

James Shore

Your team is building the UI, and several other teams are building the back-end microservices. Broadly speaking, these skills can be grouped into customer skills, development skills, and coaching skills. Coaching Skills. People with coaching skills help teams learn how to be effective Agile teams. Whole Team.

article thumbnail

From Project to Program: Scaling Camunda Adoption in Your Company

Bernd Rucker

It concentrates on helpful guidelines instead of putting constraints in place. Which brings us to microservices. Managing Decentralized Workflow Engines Instead of central platforms I advocate for an approach that every team runs its own engine , especially in a microservices context. And that is totally OK!