Timeline for How can Agile methodologies, CI/CD be applied to massive, monolithic software projects with 100s/1000s of developers?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2017 at 18:02 | comment | added | Tensibai | Any real world examples of those methods successfully implemented ? I only remember failures getting back to a V cycle or long iteration, kind of hybrid organization at end and not really Agile | |
| Mar 3, 2017 at 17:54 | comment | added | Evgeny Zislis | There are definitely examples of how large teams apply Agile methods. SAFe is an example, so is LeSS. | |
| Mar 3, 2017 at 14:13 | comment | added | Tensibai | Then the second alternative, splitting by "library" (hard to tell without a real insight on what code base we are talking about) could be a way, for large libraries, splitting the responsibility on parts with the fewer possible overlaps (and once done, splitting the library itself whenever possible) could be a way to tackle the problem. | |
| Mar 3, 2017 at 14:09 | comment | added | Dan Cornilescu | For embedded systems with legacy monolithic code microservices are rarely a practical solution. And, in general, microservices add a whole new dimension into the systems' complexity, they're really not as easy as they're often advertised as. But I digress - the question is specifically about monolithic sw ;) | |
| Mar 3, 2017 at 12:50 | history | answered | Tensibai | CC BY-SA 3.0 |