Implementing strategy through project management: The importance of managing the project front-end

Making Essential Choices with Scant Information: Front-End Decision Making in Major Projects

Volumn , Issue , 2009, Pages 39-67

  Morris, Peter W G ^a  

^a UNIVERSITY COLLEGE LONDON   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 85009235560     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1057/9780230236837     Document Type: Chapter

References (109)

1. Akalu M. (2001). Re-examining project appraisal and control: developing a focus on wealth creation. International Journal of Project Management 19 (7): 375-383.
2. Anderson D and Merna A. (2003). Project management strategy - project management represented as a process based set of management domains and the consequences for project management strategy. International Journal of Project Management 26 (3): 586-612.
3. Archer N and Ghasemzadeh F. (1999). An integrated framework for project portfolio selection. International Journal of Project Management 21 (4): 207-216.
4. Artto K and Dietrich P. (2004). Strategic business management through multiple projects. In: Morris PWG and Pinto J (eds). The Wiley Guide to Managing Projects. Wiley: Hoboken, NJ.
5. Artto K, Kujala J, Dietrich P, and Martinsuo M. (2008a). What is project strategy? International Journal of Project Management 26 (1): 4-12.
6. Artto K, Martinsuo M, Dietrich P, and Kujala J. (2008b). Project strategy: strategy types and their contents in innovation projects. International Journal of Managing Projects in Business 1 (1): 49-70.
7. Artto K, Martinsuo M, Gemünden H, and Murtoroa J. (2008c). Foundations of program management: a bibliometric view. International Journal of Project Management (in press).
8. Association for Project Management. (2004). Directing Change. A Guide to Governance of Project Management. Association for Project Management: High Wycombe.
9. Association for Project Management. (2006). Body of Knowledge for Managing Projects and Programmes (5th edition). Association for Project Management: High Wycombe.
10. Barney J and Clark D. (2007). Resource-Based Theory: Creating and Sustaining Competitive Advantage. Oxford University Press: Oxford.
11. Blyth A and Worthington J. (2001). Managing the Brief for Better Design. Spon: London.
12. Bossidy L, Charan R, Burck C, and Smith C. (2002). Execution: The Discipline of Getting Things Done. Crown Business: New York.
13. Boyatzis R. (1982). The Competent Manager: A Model for Effective Performance. John Wiley: New York.
14. Boyatzis R. (1993). Beyond competence: the choice to be a leader. Human Resource Management Review 3 (1): 1-14.
15. Bredillet C. (2007, 2008). Exploring research in project management: nine schools of project management research. Project Management Journal 38, 39.
16. Bridges W. (1996). Managing Transitions: Making the Most of Challenges (People Skills for Professionals). Nicholas Brealey Publishing Ltd.: London.
17. British Standards Institution. (BSI) (2000). Value Management, Standard. BS EN 12973:2000. British Standards Institute: London.
18. Brown S and Eisenhardt K. (1997). The art of continuous change: linking complexity theory and time-paced evolution in relentlessly shifting organisations. Administrative Science Quarterly 42:1-24.
19. Bryson J and Delbecq A. (1979). A contingent approach to strategy and tactics in project planning. American Planning Association Journal 45:176-179.
20. Burgelman R and Doz Y. (2001). The power of strategic interaction. Sloan Management Review 42 (3): 28-38.
21. Cameron E and Green M. (2005). Making Sense of Change Management: A Complete Guide to the Models, Tools and Techniques of Change Management. Kogan Page: London.
22. Christensen C. (1999). Innovation and the General Manager. Irwin McGraw Hill: Boston.
23. Christensen C and Raynor M. (2003). The Innovator's Solution: Creating and Sustaining Successful Growth. Harvard Business School Press: Cambridge, MA.
24. Cohen D. (2005). The Heart of Change Field Guide. Harvard Business School Press: Cambridge, MA.
25. Collis D and Montgomery C. (1995). Competing on resources: strategy in the 1990s. Harvard Business Review July-August: 118-128.
26. Cooke-Davies T. (2004). Project success. In: Morris PWG and Pinto J (eds). The Wiley Guide to Managing Projects. Wiley: Hoboken, NJ.
27. Cooper R, Edgett S, and Kleinschmidt E. (1998). Portfolio Management for New Products. Addison-Wesley: Reading, MA.
28. Cox A et al. (2003). Supply Chain Management: A Guide to Best Practice. Financial Times/Prentice Hall: London.
29. Crawford L. (2005). Senior management perceptions of project management competence. International Journal of Project Management 23 (1): 7-16.
30. Dallas M. (2007). Value and Risk Management: A Guide to Best Practice. Blackwell: Oxford.
31. Davis A, Hickey A, and Zweig A. (2004). Requirements management in the project management context. In: Morris PWG and Pinto J (eds). TheWiley Guide to Managing Projects. Wiley: Hoboken, NJ.
32. Dvir D, Raz T, and Shenhar A. (2003). An empirical analysis of the relationship between project planning and project success. International Journal of Project Management 21 (2): 89-95.
33. Eden C and Ackermann F. (1998). Making Strategy: The Journey of Strategic Management. Sage: London.
34. Eisenhardt K. (1989). Making fast strategic decisions in high-velocity environments. Academy of Management Journal 32 (2): 543-576.
35. Eisenhardt K and Martin J. (2003). Dynamic capabilities: what are they? In: The SMS Blackwell Handbook of Organisational Capabilities. Blackwell: Oxford.
36. ENAA. (2002). P2M: A Guidebook of Project & Program Management for Enterprise Innovation: Summary Translation. Project Management Professionals Certification Center (PMCC): Tokyo.
37. Englund R and Graham R. (1999). From experience: linking projects to strategy. The Journal of Product Innovation Management 16 (1): 52-64.
38. Flyvbjerg B, Bruzelius N, and Rothengatter W. (2003). Megaprojects and Risk: An Anatomy of Ambition. Cambridge University Press: Cambridge.
39. Foulkes J and Morris PWG. (2004). Pharmaceutical drug development project management. In: Morris PWG and Pinto J (eds). TheWiley Guide to Managing Projects. Wiley: Hoboken, NJ.
40. GAO. (2006). Assessment of Selected Major Acquisition Systems. GAO-06-626 General Accountability Office: Washington, DC.
41. Gilbert X, Büchel B, and Davidson R. (2007). Smarter Execution: Seven Steps to Getting Results. Financial Times, Pearson: London.
42. Hamel G and Prahalad C. (1994). Competing for the Future. Harvard Business School Press: Cambridge, MA.
43. ICE. (1998). RAMP: Risk Analysis and Management for Projects. Institution of Civil Engineers and Institute of Actuaries: London.
44. INCOSE. (2004). International Council on Systems Engineering Handbook. International Council on Systems Engineering: Seattle, WA.
45. IPA. (2008). http://www.ipaglobal.com Accessed April 2008.
46. Jørgensen M and Moløkken-Østvold K. (2006). How large are software cost overruns? Critical comments on the standish group's CHAOS reports. Information and Software Technology 48 (4): 297-301.
47. Kaplan R and Norton D. (2004). Strategy Maps: Converting Intangible Assets into Tangible Outcomes. Harvard Business School Press: Cambridge, MA.
48. Kaplan R and Norton D. (2008). The Execution Premium: Linking Strategy to Operations for Competitive Advantage. Harvard Business School Press: Cambridge, MA.
49. Kotter J. (1996). Leading Change. Harvard Business School Press: Cambridge, MA.
50. Kotter J. (2000). A Force for Change. Free Press: New York.
51. Kruchten P and Kroll P. (2003). The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP. Addison-Wesley: Reading, MA.
52. Kuhn T. (1962). The Structure of Scientific Revolutions. University of Chicago Press: Chicago.
53. Laufer A and Hoffman E. (2000). The "real" success factors on projects. International Journal of Project Management 20 (3): 185-190.
54. Lechler T. (1998). When it comes to project management, it's the people that matter: an empirical analysis of project management in Germany. IRNOP III. The Nature and Role of Projects in the Next 20 Years: Research Issues and Problems. University of Calgary: Calgary.
55. Leffingwell D. (2007). Scaling Software Agility. Addison Wesley: Upper Saddle River, NJ.
56. Loch C. (2000). Tailoring product development to strategy: case of a European technology manufacturer. European Management Journal 18 (3): 246-258.
57. Luecke R. (2003). Managing Change and Transition. Harvard Business School Press: Cambridge, MA.
58. McKinlay M. (2007). Managing requirements. In: Turner J and Simister S (eds). The Gower Handbook of Project Management (4th edition). McGraw-Hill: Maidenhead.
59. Meier S. (2008). Best project management and systems engineering practices in pre-acquisition practices in the federal intelligence and defense agencies. Project Management Journal 39 (1): 59-71.
60. Miller R and Lessard D. (2001). The Strategic Management of Large Engineering Projects: Shaping Institutions, Risks and Governance. The MIT Press: Cambridge, MA.
61. Milosevic D. (1989). Systems approach to strategic project management. International Journal of Project Management 19:437-443.
62. Milosevic D. (2002). Selecting a culturally responsive project management strategy. Technovation 22:493-508.
63. Milosevic D and Srivannaboon S. (2006). A theoretical framework for aligning project management with business strategy. Project Management Journal 37 (3): 98-110.
64. Mintzberg H. (1987a). Crafting strategy. Harvard Business Review July-August 65 (3): 66-73.
65. Mintzberg H. (1987b). The strategy concept I: five P's for strategy. California Management Review 30 (1): 11-24.
66. Montgomery C. (2008). Putting leadership back into strategy. Harvard Business Review January 86 (1): 54-60.
67. Morris PWG. (1994). The Management of Projects Thomas. Telford: London.
68. Morris PWG. (2003). The (Ir) relevance of project management. Proceedings of International Association for Project Management World Congress June, Moscow. IPMA: Zurich.
69. Morris PWG et al. (2006). Exploring the role of formal bodies of knowledge in defining a profession - the case of project management. International Journal of Project Management 24:710-721.
70. Morris PWG and Hough GH. (1987). The Anatomy of Major Projects. JohnWiley & Sons: Chichester.
71. Morris PWG and Jamieson H. (2004). Translating Corporate Strategy into Project Strategy. Project Management Institute: Newtown Square, PA.
72. Morris PWG and Pinto J (eds). (2004). The Wiley Guide to Managing Projects. Wiley: Hoboken, NJ.
73. Munns A and Bjeirmi B. (1996). The role of project management in achieving project success. International Journal of Project Management 14 (2): 81-87.
74. OGC. (2002a). Managing Successful Projects with PRINCE 2. The Stationery Office: Norwich.
75. OGC. (2002b). Management of Risk: Guidance for Practitioners. The Stationery Office: London.
76. OGC. (2007). Managing Successful Programmes. The Stationery Office: Norwich.
77. Pendlebury J, Grouard B, and Meston F. (1998). The Ten Keys to Successful Change Management. John Wiley & Sons: New York.
78. Porter M. (1980). Competitive Strategy: Techniques for Analyzing Industries and Competitors. Free Press: New York.
79. Porter M. (1985). Competitive Advantage: Creating and Sustaining Superior Performance. Free Press: New York.
80. Prahalad C. (1994). Corporate governance or corporate value added?: rethinking the primacy of shareholder value. Journal of Applied Corporate Finance 6 (4): 40-50.
81. Prasad B. (1996). Concurrent Engineering Fundamentals. Vols. (I and II). Prentice Hall: New York.
82. Project Management Institute. (2004). A Guide to the Project Management Body of Knowledge (3rd edition). Project Management Institute: Newtown Square, PA.
83. Project Management Institute. (2006a). The Standard for Program Management. Project Management Institute: Newtown Square, PA.
84. Project Management Institute. (2006b). The Standard for Portfolio Management. Project Management Institute: Newtown Square, PA.
85. Rajegopal S, McGuin P, and Waller J. (2007). Project Portfolio Management: Leading the Corporate Vision. Palgrave Macmillan: Basingstoke.
86. Reiss G et al. (2006). The Gower Handbook of Programme Management. Gower: Aldershot.
87. Richards K. (2007). Agile Project Management: Running PRINCE2 Projects with DSDM Atern. The Stationery Office: Norwich.
88. Sense A. (2008). Conceptions of learning and managing the flow of knowledge in the project-based environment. International Journal of Managing Projects in Business 1 (1): 33-48.
89. Shenhar A, Dvir D, and Levy O. (1997). Mapping the dimensions of project success. Project Management Journal 28:5-13.
90. Simister S. (2007). Managing value. In: Turner J and Simister S (eds). The Gower Handbook of Project Management (4th edition). McGraw-Hill: Maidenhead
91. Simon P, Hillson D, and Newland K. (1997). Project Risk Analysis and Management (PRAM). Association for Project Management: High Wycombe.
92. Society of American Value Engineers. (1997). Value Methodology Standard. SAVE International: Northbrook, IL.
93. Srivannaboon S. (2006). Linking project management with business strategy. Project Management Journal 37 (5): 88-96.
94. Srivannaboon S and Milosevic D. (2004). The process of translating business strategy in project actions. In: Slevin D, Cleland D, and Pinto J (eds). Innovations: Project Management Research 2004. Project Management Institute: Newtown Square, PA, pp. 175-192.
95. Standish. (1994). http://www.cs.nmt.edu/~cs328/reading/Standish.pdf Accessed April 2008.
96. Standish. (2006). http:www.infoq.com/articles/Interview-Johnson-Standish-CHAOS. Accessed April 2008.
97. Stevens R, Brook P, Jackson K, and Arnold S. (1998). Systems Engineering: Coping with Complexity. Prentice Hall: Hemel Hempstead.
98. Thiry M. (2004a). Program management: a strategic decision management process. In: Morris P and Pinto J (eds). TheWiley Guide to Managing Projects. Wiley: Hoboken, NJ.
99. Thiry M. (2004b). Value management. In: Morris P and Pinto J (eds). The Wiley Guide to Managing Projects. Wiley: Hoboken, NJ.
100. Thomas J, Delisle C, and Jugdev K. (2002). Selling Project Management to Senior Executives: Framing the Moves that Matter. Project Management Institute: Newtown Square, PA.
101. Thomke S. (2003). Experimentation Matters. Harvard Business School Press: Cambridge, MA.
102. Thompson A and Strickland J. (1995). Crafting and Implementing Strategy. Irwin: Chicago.
103. Turner J. (2000). Projects for shareholder value. In: Turner J and Simister S (eds). The Handbook of Project-Based Management (3rd edition). McGraw-Hill: Maidenhead.
104. Turner J. (2006). Editorials. International Journal of Project Management 24.
105. Wateridge J. (1995). How can IS/IT projects be measured for success? International Journal of Project Management 16 (1): 59-63.
106. Williams T. (2005). Assessing and building on project management theory in the light of badly over-run projects. IEEE Transactions on Engineering Management 52 (4): 497-508.
107. Winter M, Smith C, Morris P, and Cicmil S. (2006). Directions for future research in project management: the main findings of a UK government-funded research network. International Journal of Project Management 24 (8): 638-649.
108. Yeo K and Qiu F. (2003). The value of management flexibility - a real option approach to investment evaluation. International Journal of Project Management 21 (4): 243-250.
109. Youker R. (1993). Defining the hierarchy of objectives. In: Proceedings of PMI 24th Annual Symposium, San Diego. Project Management Institute: Newtown Square, PA