Software modeling is getting more fashionable, but it has a long way to go before it becomes as respectable as writing code. Which is funny in a way, because code is just one particular kind of model! Too many people get hung up on the graphical nature of modeling techniques such as the Unified Modeling Language (UML), forgetting that they have underlying textual representations as well.

Innovation is a risky proposition. While at times it can lead to spectacular success (e.g., Google, PCs), at other times the results can be disastrous (e.g., Microsoft Bob). Some of us obsessively look for the Next Big Thing, while others firmly stick to the adage "follow, do not lead." How can we master the delicate balance between attempting the new and perfecting the current? Between reinventing and reengineering? Join Guest Editor Borys Stokalski for a debate on the key issues surrounding IT-based innovations. Discover the single greatest reason that 70%-80% of new product development projects fail -- and find out how your team can "plan to get lucky."

The ability to organize for high performance is a source of competitive advantage. Teams are seen as a critical component of a high-performance organization. In my view, however, few IT managers accurately assess the organizational risk in failing to attend to team dynamics that lead to reliable delivery. Thus, they incur tremendous "organizational debt" in the way they structure and manage the work. That's where this issue of CBR comes in.