Agile and Architecture: a meeting of the undead - Einar Høst - NDC Oslo 2024
HTML-код
- Опубликовано: 21 сен 2024
- This talk was recorded at NDC Oslo in Oslo, Norway. #ndcoslo #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences...
ndcoslo.com/
Subscribe to our RUclips channel and learn every day:
/ @NDC
Follow our Social Media!
/ ndcconferences
/ ndc_conferences
/ ndc_conferences
#architecture #agile #developer #ndcoslo #ndcconferences
Twenty years ago, Architecture was murdered in its sleep by Agile, as part of the assassination plot against the arch-enemy Waterfall. Fast forward to today, and Agile isn't looking too healthy either: reduced to hollow-eyed cargo culting and pointless rituals, wading through the debris of methodology pop culture, or bloated to a monstrous parody of itself in order to scale. But death aside, they are both still among us, and moaning for brains. Why?
One reason might be that the problems that Architecture and Agile set out to fix have not been solved. Or they need continuous solving, and in the absence of new life to tackle them, we animate our dead. What are these problems, and how do we see them today?
Have we learned anything from the death of these two grand attempts at fixing software development, and their refusal to lie down even in the face of death? Is there still something that can be found in the black hearts of the undead that can be of use in addressing the problems we face? Should Agile and Architecture be revived or put out of their misery for good? Will we be able to? What new kind of life do these two half-lives point towards? What acts of bravery will be required of us going forward?
The audio issues are really distracting, seems like an interesting talk
Any chance of a reupload with clean audio?
@@Dinnella sounds like how it was captured with a ducking compressor working. The only way around it may be to recreate using AI?
@42:00 accidental or emergent?
@18:40 Captain Kirk has materialized!
@13:12 Too much emphasis on getting an architecture defined quickly is wrong, as in the first phase(s) of a project, the details are unknown. You are therefore front-loading a design before you know the details, and when the details emerge, changing the architecture is (could be) costly.