|
EDITOR'S NOTES
American philosopher, writer and publisher Elbert Hubbard said, “Progress comes from the intelligent use of experience.” It doesn’t necessarily matter if that experience is one’s own or that learned by another. After all, what mother or father hasn’t counseled a child (regardless of the age) to learn from others’ mistakes? That’s the point of the articles you read here each month.
With more than 25 years of experience to draw from, Larry True has learned a thing or two along the way. This month’s article is a lesson in cost overruns.
John Jurewicz, too, brings more than 20 years of experience to our editorial board. He’s watched the world of jobsite communication evolve over the years, yielding to its most recent incarnation—online collaboration—which provides the theme of his article, an overview of a recent Harvey study.
Finally, Primavera guru Gordon Aronson has used his 40 years of experience to hone his skills as an engineer. This month, he uses that knowledge gained to make some suggestions to CPM software developers.
This month’s final thought comes from French sculptor Auguste Rodin: “Nothing is a waste of time if you use the experience wisely.”
|
 |
COSTS OVERRUNS: NOW WHAT?
By Larry True
Cost overruns happen for a variety of reasons. Expert Larry True suggests that most overruns fit into one of three categories. In this month’s feature, he draws on his experience to offer tried and true methods for identifying and dealing with overruns.
|
 |
OVERVIEW OF HARVARD RESEARCH ON THE VALUE OF EXTRANETS
By John Jurewicz of ASPTIP.COM
The pool of online collaboration users is still relatively small, according to a recent Harvard study. But, case studies in the research suggest that those who favor this form of communication are seeing significant cost savings. John Jurewicz provides an overview of the recently released study.
|
 |
TIME-SCALED AND NETWORK LOGIC DIAGRAMS
By Gordon H. Aronson
Technological bells and whistles are only as good as their effectiveness. Scheduling expert Gordon Aronson makes a plea to scheduling software developers to create easy-to-read logic diagrams.
|
|
