Add a comment

 

Re: Do architects define the software development process?

Usually, clearly stating the benefits of taking an iterative approach is enough. This varies between projects, but for example: allows us to tackle the risky integration with X first, allows us to prove that our design will work, early visibility of progress, early feedback from testing, etc. For me, getting the risky stuff out of the way first gives software projects a massive boost and stops those situations where you find a huge problem in the "last week of development".

Re: Do architects define the software development process?


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).