[Excerpted from an article in the September 1992 Cutter IT Journal (formerly American Programmer).]

Few software risk management approaches attempt to handle both software-intensive systems-related process and product risks, and almost none assesses the primary reasons for utilizing software-intensive systems in the first place, as this is perceived to be "outside the scope" of software project managers.

Last week I had a one-on-one meeting with the CIO of one of my clients, a major financial services firm. During our conversation, Ron asked for advice about transforming his organization. By this time, I'd been working with Ron's team for about six months, and the team had made remarkable progress.

I remember when "platform" meant hardware, and later "hardware and an operating system." Today, the term is used in a variety of ways, but it always seems to suggest the platform on which key applications will sit or the environment the applications will depend on as they are executed.

Terminating a long-term, strategic relationship is often difficult and costly, as we began to discuss in the first Advisor of this series (" Ending Relationships Productively," 23 June 2004). This week we will discuss how termination based on changes in strategy or business needs can occur in a way that minimizes negative impact.

Terminating a long-term, strategic relationship is often difficult and costly, as we began to discuss in the first Advisor of this series (" Ending Relationships Productively," 23 June 2004). This week we will discuss how termination based on changes in strategy or business needs can occur in a way that minimizes negative impact.

I remember when "platform" meant hardware, and later "hardware and an operating system." Today, the term is used in a variety of ways, but it always seems to suggest the platform on which key applications will sit or the environment the applications will depend on as they are executed.

I remember when "platform" meant hardware, and later "hardware and an operating system." Today, the term is used in a variety of ways, but it always seems to suggest the platform on which key applications will sit or the environment the applications will depend on as they are executed.

I've remarked before that one of the great things about the popularity of the Internet and the Web (really beginning around 1997) is that it forced many IT people to take a larger view of their jobs.