Sage Journals: Discover world-class research

Abstract

Stakeholder theory is a useful framework for analyzing the behavioral aspects of the project management process, particularly the complicated process of project management within the Department of Defense (DOD). Projects can be beset by the agenda of various stakeholders within the organizational structure. When this occurs, the implementation of a strong project stakeholder management strategy is necessary to increase the likelihood of success. This is a case study of a failed DOD project, even though it was fully justified and badly needed. Stakeholder theory serves as the theoretical underpinning of this case analysis, which identifies the potential causes of the project failure. Project management lessons learned from the failure and a project stakeholder management strategy framework are presented to facilitate better decision making on the part of project managers to increase the likelihood of successful project management outcomes.

Keywords

Project management project stakeholder management stakeholder theory decision-making

Get full access to this article

View all access options for this article.

References

Al-tabtabai

, Alex

A. P.

, & Abou-alfotouh

(2001). Conflict resolution using cognitive analysis approach. Project Management Journal, 32(2), 4–16.

Bender

K. W.

, Cedeno

J. E.

, Cirone

J. F.

, & Klaus

K. P.

(2000). Process innovation—Case studies of critical success factors. Engineering Management Journal, 12(4), 17–25.

Bourne

, & Walker

D. H. T.

(2006). Visualizing stakeholder influence—Two Australian examples. Project Management Journal, 37(1), 5–21.

Bourne

, & Walker

D. H. T.

(2005). Visualising and mapping stakeholder influence. Management Decision, 43(5/6), 649–660.

Christenson

, & Walker

D. H. T.

(2004). Understanding the role of “vision” in project success. Project Management Journal, 35(3), 39–52.

David

(2005). Strategic management. Upper Saddle River, NJ: Prentice Hall Publishing.

Defense Systems Management College (DSMC). (1989). Systems Engineering Guide. Washington, DC: Department of Defense.

DOD/Defense Acquisitions University (DAU). (2002). Risk Management Guide for DOD Acquisitions. Washington, DC: Department of Defense.

Griffard

(2002). Shortening the defense acquisition cycle: A strategic imperative. Issues Paper 13-02. Carlisle Barracks, PA.

10.

Helm

, & Remington

(2005). Effective project sponsorship: An evaluation of the role of the executive sponsor in complex infrastructure projects by senior project managers. Project Management Journal, 36(3), 51–61.

11.

Hosking

James E.

(2005). Lessons learned: Seven keys to a successful replacement hospital project. Journal of Healthcare Management, 50(1), 8–11.

12.

Ives

(2005). Identifying the contextual elements of project management within organizations and their impact on project success. Project Management Journal, 36(1), 37–50.

13.

Jugdev

, & Muller

(2005). A retrospective look at our evolving understanding of project success. Journal of Project Management, 36(4), 19–31.

14.

Kerzner

(2003). Project management: A systems approach to planning, scheduling, and controlling. Hoboken, NJ: John Wiley & Sons, Inc.

15.

Kerzner

(2004). Advanced project management: Best practices on implementation. Hoboken, NJ: John Wiley & Sons, Inc.

16.

Killian

W. P.

(1971). Project management—Future organizational concepts. Marquette Business Review, 2, 90–117.

17.

Kimmons

R. L.

(1990). Project management basics: A step by step approach. New York and Basel: Marcel Dekker, Inc.

18.

Matta

N. F.

, & Ashkenas

R. N.

(2003). Why good projects fail anyway. Harvard Business Review, 81(9), 109–114.

19.

Metzger

(2003). JWAES: A case study. Project Management Journal, 34(4), 40–46. (Note: The Required Operational Capability (ROC) document is now known as an Operational Requirements Document [ORD]).

20.

Norrie

, & Walker

D. H. T.

(2004). A balanced score-card approach to project management leadership. Project Management Journal, 35(4), 47–56.

21.

Office of Inspector General. (2001). Audit of major defense acquisition programs cycle time. Report No. D-2002-032, Project No. D2002AB-0066.000. Washington, DC: Department of Defense.

22.

Royer

(2003). Why bad projects are so hard to kill. Harvard Business Review, 81(2), 48–56.

23.

Shimizu

, & Hitt

M. A.

(2004). Strategic flexibility: Organizational preparedness to reverse ineffective strategic decisions. Academy of Management Journal, 18(4), 44–59.

24.

Willoughby

W. J.

(1986). Best practices. Department of the Navy, NAVSCO P-6061. Washington, DC: Department of the Navy.

A Case Study of Project and Stakeholder Management Failures: Lessons Learned

Abstract

Keywords

Get full access to this article

References