http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/ Software product success. Sun, 12 Feb 2012 19:10:25 +0000 hourly 1 http://wordpress.org/?v=3.0.4 http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/comment-page-1/#comment-92141 Scott Sehlhorst Sat, 28 Apr 2007 14:01:04 +0000 http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/#comment-92141 Oh - sorry, my choice of words wasn't the best. I'm thrilled about the refactoring going on for <em>this</em> project. I just feel bad for your other project. Oh – sorry, my choice of words wasn’t the best. I’m thrilled about the refactoring going on for this project. I just feel bad for your other project.

]]> http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/comment-page-1/#comment-91954 Rolf Sat, 28 Apr 2007 05:26:09 +0000 http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/#comment-91954 Don't be sorry, this is s project. I believe "causing controversal discussions early" is a good thing. Don’t be sorry, this is s project. I believe “causing controversal discussions early” is a good thing.

]]> http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/comment-page-1/#comment-91659 Scott Sehlhorst Fri, 27 Apr 2007 16:08:51 +0000 http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/#comment-91659 Excellent. I found that just drawing the diagram brought me a sense of clarity. Sorry about the refactoring that you're going through. I hope it is at least happening early enough that you aren't messing with the users too. Excellent. I found that just drawing the diagram brought me a sense of clarity. Sorry about the refactoring that you’re going through. I hope it is at least happening early enough that you aren’t messing with the users too.

]]> http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/comment-page-1/#comment-91490 Rolf Fri, 27 Apr 2007 10:14:35 +0000 http://tynerblain.com/blog/2007/04/26/apr-vision-update-1/#comment-91490 This very well suits my view that priority is one of the most important attribute of a requirement (vision, goal, ...). In one of my current projects I have to learn the hard way that not explicitly prioritized requirements can mean significant changes to a system's architecture, if suddenly a different architect is in charge. :-( This very well suits my view that priority is one of the most important attribute of a requirement (vision, goal, …). In one of my current projects I have to learn the hard way that not explicitly prioritized requirements can mean significant changes to a system’s architecture, if suddenly a different architect is in charge. :-(

]]>