Management
“Inside-Out”: IEEE presentation in Longmont (09/02/08)
On September 2nd, I’ll be speaking at a meeting of the Denver IEEE Reliability Society. It will be held at 5:30 pm in the Seagate Building in Longmont (CO), on Nelson Road between 75th Rd and Airport Rd. Here’s my abstract of the talk: INSIDE-OUT: Organizations too often treat software reliability as an ‘after the […]
The thermocline of truth — at NASA
Rand Simberg at Transterrestrial Musings (an outstanding blog, BTW) points to this e-mail from someone leaving NASA due to a litany of frustrations. I may parse out more of the e-mail later to note some of the classic troubled/failing project attributes, but this passage caught my eye: Then between us workers and the highest levels […]
They’d rather be wrong: rejecting project solutions
I have a new Baseline column up on the tendency of large organizations to reject the best solutions for a troubled IT project: The consultants, usually with the help of the employees in the trenches, would use their time, effort, and expertise to analyze the system under development or in production. They would arrive at […]
The dangers of a successful IT project
My latest Baseline column talks about the risks that follow a successful IT project: But sometimes with projects that really shouldn’t succeed—that are attempting too much, too fast, with too many risks—enough things go right, particularly along the critical paths, enough superhuman effort is made by those involved, so that the project does indeed go […]
Using a maintenance architect
My lastest Baseline column is up, in which I argue that setting up one or more maintenance architects within an enterprise can help reduce maintenance costs while at the same time providing a training path for chief software architects. Let me know what you think. ..bruce..