Comments on: Reacting to changehttp://lostechies.com/jimmybogard/2008/04/08/reacting-to-change/
Strong opinions, weakly heldTue, 03 Mar 2015 07:43:00 +0000hourly1http://wordpress.org/?v=3.4.2By: Nolan Eglyhttp://lostechies.com/jimmybogard/2008/04/08/reacting-to-change/#comment-310
Nolan EglyFri, 18 Apr 2008 20:28:39 +0000/blogs/jimmy_bogard/archive/2008/04/07/reacting-to-change.aspx#comment-310Great thoughts. Steve McConnell talks about the need to have an agreed upon change control process in any development effort, lest the reaction of developers become "change prevention" or 'change denial". It might be possible to develop a project that meets some initial requirements list without dealing with change, but you probably won't have a very happy customer at that point. Being able to effectively deal with change is critical for any project, and any methodology.Great thoughts. Steve McConnell talks about the need to have an agreed upon change control process in any development effort, lest the reaction of developers become “change prevention” or ‘change denial”. It might be possible to develop a project that meets some initial requirements list without dealing with change, but you probably won’t have a very happy customer at that point. Being able to effectively deal with change is critical for any project, and any methodology.
]]>By: Jeff Tuckerhttp://lostechies.com/jimmybogard/2008/04/08/reacting-to-change/#comment-309
Jeff TuckerTue, 08 Apr 2008 18:28:30 +0000/blogs/jimmy_bogard/archive/2008/04/07/reacting-to-change.aspx#comment-309Good points about change and reacting to it. I think that not only is lots of feedback important, but rapid feedback is important as well. That's the reason for things like Unit Tests, Continuous integration, and dev and qa working closely together. There is an arc of distortion between the time that something is created (like a story or feature) and the time that it is changed (like bugs, acceptance criteria changes, new stories) and the greater the amount of time, the greater the size of the arc and the harder it is to respond to that change. I discuss this a bit on my blog http://agilology.blogspot.com/2008/01/so-i-have-blog-now-its-about-agile-and.html
I think I may need to go into more detail about this at some point.Good points about change and reacting to it. I think that not only is lots of feedback important, but rapid feedback is important as well. That’s the reason for things like Unit Tests, Continuous integration, and dev and qa working closely together. There is an arc of distortion between the time that something is created (like a story or feature) and the time that it is changed (like bugs, acceptance criteria changes, new stories) and the greater the amount of time, the greater the size of the arc and the harder it is to respond to that change. I discuss this a bit on my blog http://agilology.blogspot.com/2008/01/so-i-have-blog-now-its-about-agile-and.html
I think I may need to go into more detail about this at some point.
]]>