Pair Programming Is Peer Review Pair programming ensures that the code is constantly being peer reviewed. This results in quality that is as good as — or better than — that of "non-agile" projects. |
Pair Programming Is Peer Review Pair programming ensures that the code is constantly being peer reviewed. This results in quality that is as good as — or better than — that of "non-agile" projects. |
Now picture this: your CEO, COO, CFO, and CIO meet to discuss levels of IT spending and next year's IT budget. So what do they talk about when they talk about IT spending? Certainly, they talk about planned levels of IT spending and whether the projected trend is up or down and by how much. But also important, they talk about the distribution of the company's IT dollars and the allocation of IT resources. Each executive brings to the table his or her view of the role of IT within the company, and these views shape the discussion.
Understand the Business and the People |
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."