The project scoping gamble

A discussion is given on how to get people and technology to work together. The authors argue that software project managers can learn important lessons from the gambler. Software development is a gamble. Its a risky game-not unlike high stakes poker. And, like a gambler who must try to figure the best bet, when we're put on the spot trying to "scope" a software project we feel in need of some advice. Judging the timing and resources for a project is difficult when there's not much to go on. And yet, if you fail to estimate correctly, developers, management, and customers will all be unhappy. Defining a proper scope for your project won't guarantee its success, but a poor and especially an overly restricted scope may doom your project to failure. A gambler playing poker uses a variety of strategies to improve the odds of winning.