Webster is Principal and Founder at at Bruce F. Webster & Associates, as well as an Adjunct Professor for the BYU Computer Science Department. He works with organizations to help them with troubled or failed information technology (IT) projects. He has also worked in several dozen legal cases as a consultant and as a testifying expert, both in the United States and Japan. He can be reached at 303.502.4141 or at bwebster@bfwa.com.
[Cross-posted from brucefwebster.com] I’m currently writing a series of columns for Baseline on how to deal with frozen or reduced IT budgets due to the current economic troubles. Here are the first two columns: Performing IT Project Triage Pulling the Plug on IT Project Next up: how to deal with personnel issues. ..bruce..
The In re Bilski (545 F.3d 943 [Fed. Cir. 2008]; here’s a PDF of the decision) court decision placed significant new limits on so-called “process” or “business method” patents, which possible implications for many software patents. Well, I just received an e-mail from Joel Miller of the ABA Intellectual Property Law Committee (of which I’m […]
My latest Baseline column is up, and it talks about why you should read these five books now, if you haven’t already…and if you have read them, you should probably re-read them. ..bruce..
I’ve written previously about the “Dead Sea effect“, in which your best IT engineers and managers leave over time, leaving behind an IT staff that is slowly becoming less competent and effective. Obviously, to counteract the Dead Sea effect, you want to hold onto your best IT people. My two latest Baseline columns talk about […]
First, my apologies for the slow posting here and at brucefwebster.com over the past few months. It’s pretty bad when my last two posts have each covered my last two Baseline columns. But I’ve got some new material to start posting here as well, and will do so. In the meantime, I have two new […]
Classic patterns in disputed IT project: Hertz v. Accenture
Just ran across this article at the always-irreverent-but-usually-spot-on Register, an IT news site out of England. The standard patterns of a troubled IT project are so evident in this one report that I may well use it as a case study for my CS 428 (“Real-world software engineering”) class this fall. Here are some of […]
Neverending Story pattern: School District ERP system late, over-budget
A story a few days ago caught my eye, not because it was unusual, but because it follows so familiar a pattern. Here are a few excerpts from the article: MANATEE — Late nights, hefty contracts and humming computers are a norm in the district’s School Support Center, where employees are working to fix a […]
Minnesota DMV software project: Faulty Towers/Neverending Story patterns
In my 2000 white paper, “Patterns in IT Litigation: System Failure (1976-2000)” [PDF], which I researched and wrote while at PricewaterhouseCoopers, I describe six broad fact patterns to classify the types of software system implementation failure. One of those patterns I named “Faulty Towers”: The client buys the system from [or has the system developed […]
![The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]](http://bfwa.com/wp-content/uploads/2018/01/intel-cpu-150x150.jpg "The Meltdown/Spectre CPU bugs: a dramatic global case of the “Unintended Consequences” pattern [UPDATED 4/4/18]")
Back in 2000, PricewaterhouseCooper published my research white paper, “Patterns in IT Litigation: Systems Failure (1976-2000)” (PDF). This paper reflected research I and my staff had done over several months on roughly 120 two- or three-party lawsuits involving information technology. I found that almost all of these lawsuits fell into one or two of six […]