Computerworld has a great article on dealing with projects in jeopardy. While this is more managment than architecture, anyone who has been involved with a bad project will appreciate this practical advice.

Most interesting is that while there are 10 steps covering everything from risk assessment to management and reporting, there isn’t one for assigning blame. Focusing on assigning blame is like trying to recover the sunk cost in a bad investment. While some projects seem to have the ability to make time stop, in reality time is only forward, and the best thing we can do is try to learn from our mistakes and make things better in the future.

This entry was posted on Friday, September 15th, 2006 at 6:46 am and is filed under People, Practices, Relationships. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.