Jun 7, 2010
Developing software may seem very different and far removed from building a house, but I believe there is more in common than not. Consider requirements for example. If you don't invest the time and effort to capture and communicate a project's requirements effectively, the result will be wasted in the form of very costly rework. If my father built a house where 50% of the cost to the owner was in fixing things that he didn't get right the first time, he never would have built a second one, plain and simple. But yet, it appears to be "normal" or at least acceptable for our line of construction. What are your thoughts? Check out the latest Blueprint blog post by Chip Carey: http://trunc.it/8gmvu