By Topic

The project scoping gamble

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

2 Author(s)
Lawrence, B. ; Coyote Valley Software Consulting, USA ; Johnson, B.

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

Published in:

Software, IEEE  (Volume:14 ,  Issue: 3 )