03.07.2013 Views

View/Open - Naval Postgraduate School

View/Open - Naval Postgraduate School

View/Open - Naval Postgraduate School

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

When Should You Terminate Your Own Program? Bad Business:<br />

The JASORS Debacle<br />

Presenter: John Dillard joined the NPS faculty in the fall of 2000 with extensive<br />

experience in the field of systems acquisition management. His research focuses on defense<br />

acquisition policy changes and their implications. Dillard began his career in program and<br />

contract management after attaining a MS in Systems Management from the University of<br />

Southern California in 1985. He has been involved with myriad technologies and system<br />

concepts that have evolved into fielded products, such as the M-4 Carbine, 120mm Mortar, and<br />

M-24 Sniper Weapon. He was the Assistant Project Manager for Development of both the Army<br />

Tactical Missile System and, later, the JAVELIN Antitank Weapon System at Redstone Arsenal,<br />

Alabama. All of these systems incorporate state-of-the-art technologies, are in sustained<br />

production and fielding, and are now battle-proven. He was the Product Manager for the Joint<br />

Advanced Special Operations Radio System, and in 1998 was appointed to head Defense<br />

Department contract administration in the New York metropolitan area. Dillard has consulted for<br />

the governments of Mexico and the Czech Republic on achieving excellence in the public<br />

sector. As an adjunct professor for the University of California at Santa Cruz, he teaches<br />

courses in project management and leadership to Silicon Valley public- and private-industry<br />

professionals.<br />

John Dillard<br />

Senior Lecturer<br />

Graduate <strong>School</strong> of Business & Public Policy<br />

<strong>Naval</strong> <strong>Postgraduate</strong> <strong>School</strong><br />

Monterey, CA 93943-5197<br />

Phone: (831) 656-2650<br />

E-mail: jtdillard@nps.edu<br />

Preface<br />

The Project Manager (PM) is typically the advocate for his program. He is the champion<br />

for his team of government and industry players, the spokesman to higher headquarters for<br />

progress in achieving the various parameters of cost, schedule and performance, and the<br />

steward of taxpayer funds—on a constant quest for best value.<br />

He must keep the leadership—and sponsors—honestly informed in a timely manner,<br />

especially when things don’t go as planned. He must continually assess risk and the resources<br />

needed to complete the project effort so that he can marshal the appropriate forces against the<br />

challenges that invariably arise during the course of execution.<br />

The ultimate goal of a project being to advance warfighting capability, there is little<br />

accolade for lesser achievement. It is then perhaps easy for the manager’s zeal for success and<br />

personal self-worth to become associated with the project. This can allow optimism to reign—<br />

and cloud judgment—by unintentionally filtering and distorting information.<br />

A recent article describes the frustration of Congressional stakeholders with program<br />

cost overruns—whether from inaccurate early estimates, requirements creep or just poor<br />

management. There are even concerns over deliberate deception. On whether acquisition<br />

executives might ever consider terminating programs that spin out of control, their statements<br />

=<br />

=<br />

==================^Åèìáëáíáçå=oÉëÉ~êÅÜW=ÅêÉ~íáåÖ=ëóåÉêÖó=Ñçê=áåÑçêãÉÇ=ÅÜ~åÖÉ=======- 320 -<br />

=<br />

=

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!