Comments on: Agile in your architecture process…where to put it? http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/ Rants on GIS, .NET, and life in general Mon, 21 Sep 2009 12:56:28 +0000 http://wordpress.com/ hourly 1 By: Chris Spagnuolo's EdgeHopper http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-147 Chris Spagnuolo's EdgeHopper Tue, 09 Sep 2008 19:56:37 +0000 http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-147 [...] tasks are not really useable by our clients and we really can’t demo them either.  Brian Noyle recently wrote a post on his blog asking a similar [...] [...] tasks are not really useable by our clients and we really can’t demo them either.  Brian Noyle recently wrote a post on his blog asking a similar [...]

]]> By: Frank http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-94 Frank Fri, 14 Mar 2008 20:13:48 +0000 http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-94 nice site. nice site.

]]> By: homebrutrout http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-13 homebrutrout Thu, 17 Jan 2008 20:53:18 +0000 http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-13 Thanks Chris, The coarse-to-fine grain iterative architecture process worked well for me on a previous project. Technology selection and black box diagrams up front, evolving down to communication paradigms, interaction models, and class diagrams as we moved forward. Comprehensive forward engineering is definitely NOT the only option...nor is it the best one in my estimation. Cheers, Brian Thanks Chris,
The coarse-to-fine grain iterative architecture process worked well for me on a previous project. Technology selection and black box diagrams up front, evolving down to communication paradigms, interaction models, and class diagrams as we moved forward. Comprehensive forward engineering is definitely NOT the only option…nor is it the best one in my estimation.

Cheers,
Brian

]]> By: Chris Spagnuolo http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-12 Chris Spagnuolo Thu, 17 Jan 2008 20:25:36 +0000 http://briannoyle.wordpress.com/2008/01/17/agile-in-your-architecture-processwhere-to-put-it/#comment-12 Brian, this is an excellent post. Most people discount agile practices because of this design/architecture argument. I think it's a non-starter. Agile does address both, it just does it in an iterative fashion. However, you have to be careful to balance your time spent on up-front architecture with actually building "deliverable" functionality to your clients. If you looked at it like a bar chart, in the early iterations you'd see big architectural bars and small functionality bars. Conversely, as you get deeper into your project, the later iterations will have small or no architecture bars and big functionality bars. I'll be writing a blog post about this next week and will let you know when it's up. Chris Brian, this is an excellent post. Most people discount agile practices because of this design/architecture argument. I think it’s a non-starter. Agile does address both, it just does it in an iterative fashion. However, you have to be careful to balance your time spent on up-front architecture with actually building “deliverable” functionality to your clients. If you looked at it like a bar chart, in the early iterations you’d see big architectural bars and small functionality bars. Conversely, as you get deeper into your project, the later iterations will have small or no architecture bars and big functionality bars. I’ll be writing a blog post about this next week and will let you know when it’s up.

Chris

]]>