3 ms·
Great stuff. I asked one Agile coach about how and when one should do software architecture decisions for a larger project, he said you can take an extra sprin
by adrianmsmith 10y ago
Great stuff.
I asked one Agile coach about how and when one should do software architecture decisions for a larger project, he said you can take an extra sprint/spike at the start to do software architecture if necessary.
At another place, the testing members of the team always tested the previous sprint's work (otherwise they'd be doing nothing for the first 80% of the sprint, if they tested that sprint's software).
So if you had a requirements sprint, a software architecture sprint, a development sprint, then that gets tested on the next sprint, what process does that remind you of? :)
- Sharlin 10y agoThat is still iteration. Agile doesn't say you can't do things in phases, it just says those phases need to be short enough that you can iterate on them.
- valuearb 10y agoYea but how done is your sprint if your work isn't tested? It's the old, "done" vs. "done done" debates we had end of every sprint. I wrote the code, it mostly works, it has bugs. Am I done? Should I move on? Technical debt creeping higher and higher.
- adrianmsmith 10y agoAgile does say the results of sprints should be something the customer can understand and use: a software architecture document, or untested code from the development sprint, isn't that.