(2002-05-14) n

Joel Spolsky [republishes](http://www.joelonsoftware.com/articles/Jim HighsmithonProductVisi.html) Jim Highsmith article on applying Crossing The Chasm lessons to software projects. For any project, but particularly those with high uncertainty for which significant requirements changes are anticipated, creating a product vision statement helps teams remain focused on the critical aspects of the product, even when details are changing rapidly... Even within an IT organization, I think every project should be considered to produce a "product."... One practice that I've found effective in getting teams to think about a product vision is the Design The Box exercise. (Shared Vision)