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.
My newest Baseline column is up: “Lies, Damned Lies, and Project Metrics (part 3)“. In it, I wrap up my discussion on IT project metrics, outlining a possible approach using instrumentation and heuristics. Go check it out. ..bruce..
My newest Baseline column is up: “Lies, Damned Lies, and Project Metrics (part 2)“. In it, I talk about why it’s so hard to apply metrics to IT project management and begin to suggest an approach. Go check it out. ..bruce..
[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial What are the risks in modern software development? Look at the pitfalls listed in this book to start. Kind of makes you want to take up gardening, doesn’t it? On the other hand, being able to identify those risks and then manage […]
[From Pitfalls of Modern Software Engineering by Bruce F. Webster (forthcoming)] Categories: managerial This is a classic pitfall in software engineering. Typically, insufficient time is allocated for the problem specification, research, design, architecture, and review that should occur before coding and during each development cycle. Likewise, software quality assurance (SQA) is often given little time, […]
I’ve been working for some time on a book called Surviving Complexity. Many of my posts over at brucefwebster.com have adapted from materials I’m writing for that book. Well, now I’ve been hired by Ziff Davis Enterprises to write a weekly column on IT Management for the online version of Baseline. That column is titled […]
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 […]