4 ms·
This is how you end up with poorly architected code that will be so difficult to change that development will eventually slow down, stop, or begin going backwar
by douglaswlance 6y ago
This is how you end up with poorly architected code that will be so difficult to change that development will eventually slow down, stop, or begin going backwards.
- lumost 6y ago+1 to this, eventually the sprint tasks are so minor as to not have any impact on the business - but they still take days.
- tchaffee 6y agoNot in my experience. If you are agile, you can fix the architecture as needed. You end up with poorly architected code by deciding to continue building on top of something when it is no longer suited to purpose. That can also happen as a result of big investments in planning. That investment makes it very hard to rationalize architecture changes when the requirements change mid project. Which they very often do. No amount of planning protects you from the unpredictable.