|
Capers Jones, "Software Project Management
Practices: Failure Versus Success," Crosstalk, October, 2004,
http://www.stsc.hill.af.mil/crosstalk/2004/10/0410Jones.html.
An exceptional
resource on the probability of success, failure and cost overruns on major
projects, based on a review of 250 major projects.
Mark Haynie, "Mainframe Migration: Performance
of Enterprise Server™ for Windows®," September, 2004,
http://www.microfocus.com/Resources/Whitepapers/?stp=lst&stext=ibm,
document
wp-mm-windows2005_tcm21-5274.pdf. This document deserves a careful read for the
methodology and analysis, but the conclusion is pretty clear:
"This table indicates that an eight processor configuration of the Unisys
ES7000 (up to a 32-CPU box) is measured at 1347 mainframe MIPS and can
handle the workload up to that level. So, the implication is that an
existing mainframe online transaction processing workload under CICS up to
1347 MIPS it could run on Micro Focus Enterprise Server with MTO environment
in this hardware configuration." (page 11)
Note that the author confirmed that the ES7000 configuration was 8 2.8 GHz
CPUs via private communication.
Mark Haynie, "Mainframe Migration: Performance of Micro Focus Server for
Linux," September, 2004,
http://www.microfocus.com/Resources/Whitepapers/?stp=lst&stext=ibm,
document
wp-mm-Linux07_tcm21-5273.pdf. This document also deserves a careful read, but
gives an even better result with Linux:
"This table indicates that an eight [sic] processor configuration of the
Dell PowerEdge 2650 (2-CPU Pentium 4, 2.8GHz, 2GB RAM) is measured at 875
mainframe MIPS and can handle the workload up to that level. So, the
implication is that an existing mainframe online transaction processing
workload under CICS up to 875 MIPS it could run on a Micro Focus Server
environment in this hardware configuration." (page 10, note typographical
error)
Warren S. Reid, "CPR (Cooperative
Project Recovery) - Reviving the Drowning Large-Scale IT Project," August,
2007,
http://www.hgexperts.com/hg/legalarticle-cooperative-project-recovery.asp.
13 step model that focuses on the actions that must be taken to turn around,
overcome, and compensate for deficiencies in project management, methodology,
technology, and people in live, ongoing projects.
Warren S. Reid,
"Why Do Systems &
Software Projects Fail?," August, 2007,
http://www.hgexperts.com/hg/legalarticle-software-projects.asp. In
this new millennium, it is still true that approximately 29% of all
large-scale systems projects are successful, 53% are challenged
(with average overruns of 84% in time, 56% in dollars and only providing 67% of
the required functionality), and 18% are scrapped and written off altogether.
A brief discussion of the communication failures that create this result are
presented both humorously and very effectively in a "he said/she said" format.
|
