In previous issues of ITMS, I tackled the subject of managing Internet-speed deadlines (see ITMS, May and June 2000). Specifically, what do you do when IT projects are given a deadline first, before you know the full scope of the requirements? Also, how do IT applications development and maintenance projects fundamentally behave -- what are the "laws of nature"? How can that knowledge help us estimate projects better?
Article
Sizing Up Your Promises and Expectations
By Michael Mah
Posted August 31, 2000 | Technology | Cutter Benchmark Review
About The Author
Michael Mah is Managing Partner of QSM Associates, Inc., a firm specializing in software measurement, project estimation, and "in-flight" control for both inhouse and outsourced/offshore development. QSM has developed and maintains one of the largest databases of more than 7,500 completed projects collected worldwide, with productivity statistics and trends on cost, schedule, and quality from more than 500 organizations and 18 countries.
With… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.