Back in January, I blogged about Brad Appleton’s Unchangeable Rules of Software Change. In February, Brad, together with Robert Cowham and Steve Berczuk, expanded on that topic in a longer, but still easy to read, article by the same title for CM Crossroads. I missed his post about the article.
This month we examine the fundamental truths about project and requirements changes: What can we control? What is beyond our control? What are some of the common perils and pitfalls of change-control and iterative development? We discuss how to avoid many of these common pitfalls without creating new ones along the way, and provide a wealth of resources for first-timers to iterative development.