Agile Architecture: Linking Requirements and Architecture to Solve the Right Problem

Recorded at:

Summary
Mario Cardinal explains how to use agile practices to incrementally introduce non-functional requirements into the architecture in order to reduce the complexity of the solution.

Bio

Mario Cardinal is an independent consultant specializing in software architecture. He has hosted the VS Talk Show since 2004 and he leads the architecture user group for the Montreal .Net Community and is the architecture track tech chair for DevTeach. He is a Microsoft MVP and Certified ScrumMaster (CSM), Microsoft Certified Technology Specialist and Microsoft Certified Solution Developer.

DevTeach stands for Developers Teaching Therefore, It is a conference done by developers for developers. These events have all the elements of an international conference with speakers coming from all over the globe but keeping the values we all treasure from local community events. We pride ourselves in offering the biggest diversity of subjects covered in our various sessions. All our sessions provide presentation material to the attendee and whenever possible, hans-on training. DevTeach is not so much a conference as it is a “developer festival.

Get the most out of the InfoQ experience.

Tell us what you think

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.