Timeline for Agile implementation on a microservices oriented company
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 26, 2021 at 9:59 | comment | added | Ignacio Soler Garcia | They are but we are building everything together so the reason these services need to add functionalities is that they are not feature complete, they are more close to MVPs than anything else, so when we need to add features almost everything needs to add features as well. They are loosely coupled, is not that everything depends on everything but there are a few dependency links here and there. | |
| Jul 16, 2021 at 21:12 | comment | added | Kris Van Bael | I would expect that your microservices would be loosely couples and to some extend organized per domain. So a typical new feature would need a few services updated at most. | |
| Jul 16, 2021 at 10:03 | comment | added | Ignacio Soler Garcia | Can you elaborate a bit more? What is what you consider needs to be improved? | |
| Jul 16, 2021 at 5:29 | comment | added | Kris Van Bael | Hmmm, if that is common, then your micro-service architecture might need a closer inspection than your organisation. | |
| Jul 15, 2021 at 6:51 | comment | added | Ignacio Soler Garcia | One example, to add a new feature to a product 9 teams need to collaborate adding functionalities to their microservices. These 9 teams need to coordinate between them to plan their work as there are multiple dependencies between them. | |
| Jul 14, 2021 at 5:21 | comment | added | Kris Van Bael | Can you elaborate on “complex team dependencies”? As to understand your problems better. | |
| Jul 12, 2021 at 15:05 | answer | added | Thomas Owens♦ | timeline score: 4 | |
| Jul 12, 2021 at 12:15 | history | asked | Ignacio Soler Garcia | CC BY-SA 4.0 |