Many experts have applauded the concept of speed to market. The fastest team wins in the competitive arena. While this may be correct in many cases, we should be careful in applying it as a hard and fast rule for new information technologies.

Any risk analysis should be undertaken by assessing the likelihood and relevance of risks and threats, but it is difficult to know exactly the extent to which the information and technical infrastructure of any building in any country is exposed without knowing who was responsible for undertaking and funding the attack on the World Trade Center (WTC).

A reader recently asked me to comment on the application of data warehousing and business intelligence (BI) in business-to-business (B2B) e-commerce. Therefore, I've decided to make this the topic of this week's Advisor.

Too many projects? Not sure which projects are most important? Welcome to project portfolio management.

The Internet and advances in information and communication technology (ICT) offer many new opportunities, especially for small and medium-sized enterprises (SMEs) to leverage their business. The hard reality is, however, that many SMEs across the world are not recognizing and realizing these opportunities, and are not aware of the threats they face in the new economy, which are listed here:

One of my favorite scenes from the old Star Wars movie was Obi-Wan Kenobi's sixth-sense recognition that one of the rebel planets has been completely obliterated by Darth Vader's sinister "death star." With profound sorrow and sadness,

A recent study from Cutter Consortium's e-Project Management Advisory Service looked at how much voluntary overtime developers were working. It found that companies that had developers working more than 10 hours per week in voluntary overtime suffered in a number of areas when compared to companies that did not have developers working more than 10 hours per week.

I've been rather amused by the number of Y2K-related e-mail messages I've received since 11 September -- though I dearly wish that the events that prompted those messages had never occurred.

In one form or another, computing people have always worked in teams. As a result, the implementation of self-managing teams into computing groups should be easy, but, as Larry Constantine has noted, putting a bunch of computer people together and calling them a team does not make them a team.