Timeline for Agile implementation on a microservices oriented company
Current License: CC BY-SA 4.0
4 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 13, 2021 at 9:22 | comment | added | Thomas Owens♦ | @IgnacioSolerGarcia The approach I describe has nothing to do with the system architecture and applies equally to monoliths, microservices, and everything in between. For some organizations, a component-based approach may work well. I don't think that's the majority of organizations, though. Teams that own the whole system or an end-to-end slice (often organized by customer or user group) of the whole system, across components, have been found to be better at delivering faster and producing higher-quality work because they have reduced dependencies on other teams to deliver their changes. | |
Jul 13, 2021 at 6:41 | comment | added | Ignacio Soler Garcia | Well, as far as I know, the classical approach with microservices was to build them around a team that has the ownership of the service. And to give the microservice the full vertical slice of functionality so it can be fully independent, so with that approach, you would end up with an organization like ours. How would your approach fit with a microservices organization? Or is just that microservices organization is not a favoured trend anymore? | |
Jul 12, 2021 at 16:59 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
added 16 characters in body
|
Jul 12, 2021 at 15:05 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |