Location visible to members
The words “agile” and “architecture” are often seen as mutually exclusive but the real world is starting to tell a different story. Some software teams do see architecture as an unnecessary evil whereas others are coming to the conclusion that they do need to think about architecture once again. After all, even the most agile of software projects will have some architectural concerns and these things really should be thought about up front. Agile software projects therefore do need “architecture”, but this seems to conflict with how agile has been evangelised for the past 10 years. This session will look at the conflict between agile and architecture in the context of the software development process and how the software architecture role fits into agile teams.
Depending on your viewpoint, Simon is either a software architect who codes or a software developer who understands architecture. When he's not developing software with .NET or Java, Simon can usually be found consulting, coaching or training. Simon has also written books about Java, presented at industry events and has put together a training course called Software architecture for developers (http://www.softwarearchitecturefordevelopers.com/), which is based upon his software architecture writing at Coding the Architecture (http://www.codingthearchitecture.com/).
Twitter: @simonbrown (http://twitter.com/simonbrown)
E-mail: simon.brown at codingthearchitecture.com
A panel discussion after Simon take with:
* Simon Brown
* Robert Smallshire
* Eamonn J. Casey
* Magnus Green