Editor's Note: The following two articles are from Cutter's Business Technology Trends and Impacts Council Opinion, " Spending Priorities for 2002," (Vol. 2, No. 11) published at the close of 2001.
"There are three kinds of people: those who can count and those who can't." — Anonymous
Whether you are trying to initiate a software metrics program or trying to sustain one due to organizational changes, budget constraints, or other factors, the benefits must be continuously sold
"If you want higher quality, build less stuff." That, in essence, is what Cutter Business Technology Council Fellow Tom DeMarco once said about a daring strategy for quality improvement: reduce quantity.
This issue of Amplify presents a curated collection of visionary yet grounded contributions that illuminate the most pressing challenges and innovative solutions shaping the future of quantum software engineering.
May 19, 2025 | Authored By: Mario Piattini, Ricardo Perez Castillo
"The more efficient you are, the harder it is to change." In this article, Cutter Business Technology Council Fellow Tom DeMarco's adage will be our guidepost as we examine issues concerning IT and business, drawn from Cutter Consortium's surveys.
"Slack represents operational capability sacrificed in the interests of long-term (organizational) health." So writes Cutter Business Technology Council Fellow Tom DeMarco in his acclaimed book, Slack: Getting Past Burnout, Busy Work, and the Myth of Total Efficienc
PART I: THE "MAKE OR BREAK" OF A PROJECT
How important are development teams to the success of a software project? Does team structure really matter? To a varying degree, most of us believe that it does.
This time of year, whether you want to or not, you have to give some thought to the basic issues of our IT management profession. Things like: Who's paying? How much can the company afford? What technologies does it want? And what is most important?
In this month's CBR, we take on a classic issue: software estimation. It's a classic because it looks, on the surface, like something we ought to have figured out by now. There's a "way it's supposed to work" that looks plausible.
PROJECT MEASUREMENT
Tom DeMarco was clear when he said, "You can't control what you can't measure." 1 The concept of a software metric is widely developed, and it reflects the worldwide industry acknowledgement of this imperative need.
In the early 1990s, there was something of a rush to migrate mainframe applications to client-server platforms. By the mid-1990s, this rush slowed as organizations found themselves needing to deal with the reality of the Internet.
It's hard to open a newspaper these days and not read about the purported economic slowdown. Indeed, anything compared to the ferocious growth of the 1990s would suffer. Pressures brought about from these conditions make negotiation very difficult for IT organizations under the gun.
In more than 30 years of IT and business consulting, I have never encountered a more mean-spirited managerial environment than the one facing the survivors of the post–dot-com and post-Enron work world. 1 In management and project management seminars
The term "agile," which has gained increasing popularity in today's IT and larger business world, is applied as an adjective to a variety of activities, ranging from computer programming to organizational behavior.
The use of software metrics to manage and control project development and delivery is an accepted industry-wide best practice. Even though standardized metric definitions and practices are not yet fully developed, measurement programs are evident in more than 80% of IT organizations today.