By bfwebster on Aug 29, 2008 in Articles, Baseline, Development, Main, Maintenance | 0 Comments
My newest Baseline column is up, talking about the dilemma faced in deciding whether to acquire software or build it yourself:
The other day, an IT colleague of mine mentioned a conflict at a corporation where he’s working. The corporation has a mission-critical application deployed across a large number of workstations. The set of [...]
By bfwebster on Aug 24, 2008 in Articles, Baseline, Main, Surviving Complexity | 0 Comments
My latest Baseline column is now up:
Last week, I talked about some of the reasons why large organizations often reject the best solutions for a troubled IT project: fear, pride, budget, and the ever-present internal politics. This week, as promised, I will talk about what it takes to champion the right solution. I can’t guarantee [...]
By bfwebster on Aug 15, 2008 in Articles, Baseline, Main, Management, Project Failure, Surviving Complexity | 1 Comment
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 a [...]
By bfwebster on Aug 7, 2008 in Articles, Baseline, Development, Main, Management, Surviving Complexity | 0 Comments
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 into [...]
By bfwebster on Jul 25, 2008 in Architecture, Articles, Baseline, Main, Maintenance, Management | 0 Comments
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..