Add a comment

 

Re: The conflict between agile and architecture (part 1)

OK, I'll bite :). For me I'd go through an evaluation and prototyping process. I typically go through Matt Raible's 20 point check list for picking a web technology stack. If covers all sort of questions ranging from technical (does it support txns) to more cultural (does the tech stack fit in with the existing IT infrastructure, can you hire developers for this tech stack etc). I'd pick a couple of stacks to then prototype for 1 week each, tackling what I perceive to be the pain points for the application (tackle the hard stuff first). Given the fact that there's a short time frame, I'd also be pretty adamant about having a co-located team of users, business people, developers etc

Re: The conflict between agile and architecture (part 1)


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).