McKinsey Consulting came out with a CRM article the same week I read Mark Van Clieaf’s comments about how to succeed at CRM — he says to run it through Marketing before, during and after implementation. McKinsey’s piece (Anupam Agarwal, David P. Harding, and Jeffrey R. Schumacher, “Organizing for CRM“, McKinsey Quarterly) has some very amusing things to say: In …
Project Portfolios Require High-Level Capability
In Waltzing With Bears, Lister and DeMarco describe the benefits of running IT projects within a portfolio. Not every one of them would have to succeed: you could take on several very high-risk (but high-payoff) projects and balance it with several low risk / low payoff projects. Having low-risk/high pay-off projects would be great, but most of the time those …
You Need All Levels of People For Success
People who can see the whole complexity of the project “need to be paired with people that can deal with the details at other levels,” says Jack Vinson. Absolutely. Looking back on what I have written, I haven’t made that entirely clear. Everyone is important and necessary for the group to succeed. We need each other, each of us working …
Know Your Projects’ IT Level of Complexity and Explode Up Your Success Rates
How do I consult to a non-Requisite Organization, one whose very organizational structure means that they will not succeed at this change? I can’t in good conscience tell them that whatever I suggest will have much of an effect on their performance as a group.
Simplifying Project Costing & Staffing with Requisite Organization’s Time Span of Discretion
I don’t think that I am going out on a limb when I say that short time horizons of project managers, sponsors and planners is the leading cause to the disastrous failure rate of IT projects… As Michelle says, “you want a consultant whose current capability at least equals that called for by the entire project, not just the time span of the planning phase.””
Risk Taking, Risk Management and Software Project Management
Since IT projects are particularly prone to ignoring risk and escalation of commitment, reviewing some of the research on how we make decisions will benefit any IT manager or PM.
The Abilene Paradox of Escalation of Commitment: How We Can All Agree To Go Over the Cliff
When a project starts heading south, you would think that the rats would start abandoning the ship and the sponsor would quickly pull the plug to minimize losses. But that’s not what happens. Sponsors’ commitment to projects going bad actually seems to grow. The literature is littered with examples of sponsors continuing to spend money on a project that is …
De-escalation of Commitment to Projects
There is a large body of work dealing with the escalation of commitment in IT projects, how managers continue to throw good money after bad, increasing their commitment to a project that has little chance of succeeding. For example, Gustavo Dimello has an interesting summary (“To Pull or Not To Pull the Plug: When Managers Commit Themselves to Failure”) of …
Succeeding at Software Projects
Software projects are almost always late and underdone. Most executives take it for granted nowadays that developers will turn in something other than what was requested for more than was announced. They even admit that this is one of the biggest reasons that they outsource, because the contracts with outsourcers force the organization to develop software in a rational way. …
Rules for Organizing for Project Success
Even though they are continuing to spend millions every year, the project has almost no chance of success for entirely organizational reasons.