Author Archive: bfwebster
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.
HR 3200 from a systems design perspective (Part II)
In the first part of this three-part series, I briefly outlined the parallels between developing software and crafting legislation, while pointing out the great risks and issues in the latter. I also indicated what I felt were some of the general structural flaws in HR 3200, the House bill on health care reform — not […]
HR 3200 from a systems design perspective (Part I)
[Welcome Slashdotters — feel free to leave comments here or there. But no debates on health care reform or what HR 3200 does or does not do, please — just on the concept itself.] [Part II is now up.] On the occasions where I have reviewed the actual text of major legislation, I have been […]
Book review: “Why New Systems Fail”
My review of Why New Systems Fail by Phil Simon is now up on Slashdot. Here’s the opening paragraph: Over the last forty years, a small set of classic works on risks and pitfalls in software engineering and IT project management have been published and remained in print. The authors are well known, or should […]
Techno-blindness
A few decades back, when handheld electronic calculators were still pretty neat, someone did a study on the authority people gave to them. As I recall, those conducting the study built some normal-looking calculators that were designed with specific errors in the calculation circuits such that in certain cases the calculators would give wrong answers. […]
Fireflies, conveyor belts, and landfills
My newest Baseline column is up, and in it, I talk about technology lifecycles that can cause you grief: Each technology is on its own product lifecycle, which may or may not match with your organization’s business and development lifecycles. In particular, there are certain cycle mismatch patterns that commonly occur in organizations looking to […]