CLOSE FULL VIEW
Agile Architecture: Linking Requirements and Architecture to Solve the Right Problem
Recorded at:
Community comments
Great stuff
by
Guillaume L
Posted
Great stuff
by
Guillaume L
I was litterally blown away by this presentation that links together so many concepts and practices I used to see separately from each other. It really "put together the pieces of the puzzle" as Mario said.
2 remarks though :
- Section C was a bit rough, probably requiring a good understanding of CQRS (which few people have). A question comes to mind : is implementing CQRS and all that seemingly complex stuff really a way of "achieving simplicity" ? One of the goals of the approach seems to be to reduce the number of abstractions, but isn't putting visible interfaces and facades everywhere the exact opposite of that ?
- Part A was about regular "stakeholder" user stories, part B about technical/architectural stories. I didn't get if the architectural model described in part C and the Given-When-Then scenarios mapped to fake stores, queries & commands address only technical stories or any type of story. Maybe the presentation lacked step by step examples of how the overall architecture can emerge through the creation and implementation of these scenarios.
I'll definitely buy the book when it comes out.
2 remarks though :
- Section C was a bit rough, probably requiring a good understanding of CQRS (which few people have). A question comes to mind : is implementing CQRS and all that seemingly complex stuff really a way of "achieving simplicity" ? One of the goals of the approach seems to be to reduce the number of abstractions, but isn't putting visible interfaces and facades everywhere the exact opposite of that ?
- Part A was about regular "stakeholder" user stories, part B about technical/architectural stories. I didn't get if the architectural model described in part C and the Given-When-Then scenarios mapped to fake stores, queries & commands address only technical stories or any type of story. Maybe the presentation lacked step by step examples of how the overall architecture can emerge through the creation and implementation of these scenarios.
I'll definitely buy the book when it comes out.




Hello stranger!
You need to Register an InfoQ account or Login to post comments. But there's so much more behind being registered.Get the most out of the InfoQ experience.
Tell us what you think