AaltonenK., & SivonenR. (2007). Response strategies to stakeholder pressure in global projects. International Journal of Project Management, 27(2), 131–141.
2.
AbbottA. (1992). The system of professions.Chicago, IL: University of Chicago Press.
3.
AckerD. D. (1980). The maturing of the DoD acquisition process. Defense Systems Management Review, 3, 3.
4.
ArgyrisC. (1976). Single-loop and double-loop models in research on decision making. Administrative Science Quarterly, 21, 363–375.
5.
ArgyrisC., & SchönD. (1978). Organizational learning: A theory of action perspective.Reading, MA: Addison-Wesley.
6.
ArttoK., KujalaJ., DietrichP., & MartinsuoM. (2007). What is project strategy?International Journal of Project Management, 26(1), 4–12.
7.
Association for Project Management. (2004). Directing change. A guide to governance of project management.High Wycombe: APM.
8.
Association for Project Management. (2013). Body of Knowledge (6th ed.). Princes Risborough: APM.
9.
BergenW. B. (1954). New management approach at Martin. Aviation Age, 20(6), 39–47.
10.
BhaskarR. (1975). A realist theory of science.Leeds: Leeds Books.
11.
BresnenM. (2007). Deconstructing partnering in project-based organisation: Seven pillars, seven paradoxes and seven deadly sins. International Journal of Project Management, 25(4), 365–374.
12.
BresnenM., & MarshallN. (2000). Building partnerships: Case studies of client-contractor collaboration in the UK construction industry. Construction Management and Economics, 18(7), 819–832.
13.
BrooksC. G., GrimwoodJ. M., & SwensonL. S. (1979). Chariots for Apollo: A history of manned lunar spacecraft.Washington, DC: NASA.
14.
BS ISO 10006 (2003). Quality management systems: Guidelines for quality management in projects.London, England: BSI.
15.
BurnsT., & FlamH. (1987). The shaping of social organization: Social rule system theory with applications.London, England: Sage Publications.
16.
BurnsT., & StalkerG. M. (1961). The management of innovation.London, England: Tavistock Publications.
17.
CarrE. H. (1961). What is history?Cambridge, MA: Cambridge University Press.
18.
ChapmanC., & WardS. (2011). How to manage project opportunity and risk: Why uncertainty management can be a much better approach than risk management.Chichester, England: John Wiley & Sons.
19.
ClarkK. B., & FujimotoT. (1991). Product development performance.Cambridge, MA: Harvard Business School Press.
20.
CookD. L. (1977). Certification of project managers—Fantasy or reality?Project Management Quarterly, 8(3), 32–34.
21.
CoxA., & IrelandP. (2006). Relationship management theories and tools in project procurement. In PrykeS., & SmythH. (Eds.), The management of complex projects: A relationship approach (pp. 251–281). Oxford: Blackwell Publishing.
22.
DaviesA., & HobdayM. (2005). The business of projects.Cambridge, MA: Cambridge University Press.
23.
DavisA. M., HickeyA. M., & ZweigA. S. (2004). Requirements management in a project management context. In MorrisP. W. G., & PintoJ. K. (Eds.), The Wiley guide tomanaging projects.Hoboken, NJ: Wiley.
24.
DavisS. M., & LawrenceP. R. (1977). Matrix.Reading, MA: Addison-Wesley.
25.
DeFillippiR. J., & ArthurM. B. (1998). Paradox in project-based enterprise: The case of film making. California Management Review, 40(2), 125–139.
26.
EastmanC., TeicholzP., SacksR., & ListonK. (2011). BIM handbook: A guide to building information modeling for owners, managers, designers, engineers, and contractors (2nd ed.). Hoboken, NJ: Wiley.
27.
ENAA. (2002). P2M: A guidebook of project & program management for enterprise innovation: Summary translation.Project Management Professionals Certification Center. Tokyo, Japan: PMCC.
28.
European Construction Institute. (1999). The ECI guide to managing health in construction.London, England: Thomas Telford.
29.
Faculty of Actuaries, Institute of Actuaries, the Institution of Civil Engineers. (1998). Risk analysis and management for projects.London, England: Thomas Telford.
30.
FlyvbjergB., BruzeliusN., & RothengatterW. (2002). Megaprojects and risk: An anatomy of ambition.Cambridge: Cambridge University Press.
31.
FlyvbjergB., & BudzierA. (2013). Making sense of the impact and importance of outliers in project management through the use of power laws. Paper presented at the IRNOP 11th Conference, Oslo.
GannD. M., & SalterA. J. (2000). Innovation in project-based, service-enhanced firms: The construction of complex products and systems. Research Policy, 29(7-8), 955–972.
34.
GeelsF. (2004). From sectoral systems of innovation to socio-technical systems: Insights about dynamics and change from sociology and institutional theory. Research Policy, 33, 897–920.
35.
GerwinD., & SusmanG. (1996). Special issue on concurrent engineering. IEEE Transactions on Engineering Management, 32(2), 118–123.
36.
GiddensA. (1984). The constitution of society: Outline of the theory of structuration.Berkeley and Los Angeles: University of California Press.
37.
GoldrattE. M. (1990). Theory of constraints.Great Barrington, MA: North River Press.
38.
GoldrattE. M. (1997). Critical chain.Great Barrington, MA: North River Press.
39.
GrabherG. (2002). Cool projects, boring institutions: Temporary collaboration in social context. Regional Studies, 36(3), 205–214.
40.
GrabherG. (2004). Temporary architectures of learning: Knowledge governance in project ecologies. Organization Studies, 25(9), 1491–1514.
41.
HarréR. (1972). The philosophies of science.Oxford: Oxford University Press.
42.
HelmJ., & RemingtonK. (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.
43.
HodgsonD., & CicmilS. (2006). Making projects critical.Hampshire and New York: Palgrave Macmillan.
44.
HodgsonD., & MuzioD. (2010). Prospects for professionalism, In MorrisP. W G., PintoJ. K., & SöderlundJ. (Eds.), The Oxford handbook of project management.Oxford: Oxford University Press.
45.
HorwitchM. (1982). Clipped wings: The American SST conflict.Cambridge, MA: MIT Press.
46.
JohnsonS. B. (1997). Three approaches to big technology: Operations research, systems engineering, and project management. Technology and Culture, 38(4), 891–919.
47.
JohnsonS. B. (2001). Samuel Phillips and the taming of Apollo. Technology and Culture, 42(4), 685–709.
48.
JørgensenM., & Moløkken-ØstvoldK. J. (2006). How large are software cost overruns? Critical comments on the Standish Group's CHAOS reports. Information and Software Technology, 48(4), 297–301.
49.
JugdevK., & MüllerR. (2005). A retrospective look at our evolving understanding of project success. Project Management Journal, 36(4), 19–31.
50.
KnightK. (1976). Matrix organization: A review. Journal of Management Studies, 13, 111–130.
51.
KoskelaL., & HowellG. (2002). The underlying theory of project management is obsolete. Conference Proceedings of the 2002 PMI Research Conference, Seattle, WA.Newtown Square, PA: Project Management Institute.
52.
LanierF. (1956). Organizing for large engineering projects, Machine Design, 27, 54.
53.
LarsonE. W., & GobeliD. H. (1989). Significance of project management structure on development success. IEEE Transactions on Engineering Management, 36(2), 119–125.
54.
LawrenceP. R., & LorschJ. W. (1967a). Organisation and environment: Managing integration and differentiation.Cambridge, MA: Harvard University Press.
55.
LawrenceP. R., & LorschJ. W. (1967b). The new management job: The integrator. Harvard Business Review, Nov-Dec, 142–151.
56.
LeffingwellD. (2007). Scaling software agility.Upper Saddle River, NJ: Addison-Wesley.
57.
LenfleS. (2012). Proceeding in the dark. Innovation, project managment and the making of the atomic bomb (CRG working paper (008–01)).
58.
LittauP., JujagiriN. J., & AdlbrechtG. (2010). 25 years of stakeholder theory in project management literature (1984–2009). Project Management Journal, 41(4), 17–29.
59.
LochC. (2000). Tailoring product development to strategy: Case of a European technology manufacturer. European Management Journal, 18(3), 246–258.
60.
Mahmoud-JouiniS. B., MidlerC., & GarelG. (2004). Time-to-market vs. time-to-delivery: Managing speed in engineering, procurement and construction projects. International Journal of Project Management, 22(5), 359–367.
61.
MeierS. R. (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.
62.
MidlerC., & NavarreC. (2004). Project management in the automotive industry. In MorrisP. W. G., & PintoJ. K. (Eds.), The Wiley guide to managing projects (Chap. 10). Hoboken, NJ: Wiley.
63.
MightR. J., & FischerN. Z. (1985). The role of structural factors in determining project management success. IEEE Transactions on Engineering Management, 32(2), 71–77.
64.
MillerE. J., & RiceA. K. (1967). Systems of organization: The control of task and sentient boundaries.London, England: Tavistock.
65.
MillerR., & HobbsB. (2005). Governance regimes for large complex projects. Project Management Journal, 36(3), 42–50.
66.
MillerR., & LessardD. R. (2001). The strategic management of large engineering projects.Cambridge, MA: MIT Press.
67.
MintzbergH. (1979). The structuring of organizations.Englewood Cliffs, NJ: Prentice-Hall.
68.
MorrisP. W. G. (1994). The management of projects.London: Thomas Telford.
69.
MorrisP. W. G. (2013). Reconstructing project management.Chichester, England: Wiley-Blackwell.
70.
MorrisP. W. G., & HoughG. H. (1987). The anatomy of major projects.Chichester, England: John Wiley and Sons.
71.
MorrisP. W. G., & JamiesonH. A. (2004). Translating corporate strategy into project strategy.Newtown Square, PA: Project Management Institute.
72.
MorrisP. W. G., PatelM. B., & WearneS. H. (2000). Research into revising the APM project management body of knowledge. International Journal of Project Management, 18(3), 155–164.
73.
MorrisonE. J. (1967). Defense systems management: The 375 series. California Management Review, 9, 4.
74.
MüllerR., & TurnerJ. R. (2005). The impact of principal-agent relationship and contract type on communication between project owner and manager. International Journal of Project Management, 23(5), 398–403.
75.
NewcombeR. (2003). From client to project stakeholders: A stakeholder mapping approach. Construction Management and Economics, 21(8), 841–848.
76.
NonakaI., & TakeuchiH. (1995). The knowledge-creating company.New York, NY: Oxford University Press.
77.
Office of Government Commerce. (2002a). Managing successful projects with PRINCE 2.Norwich: TSO.
78.
Office of Government Commerce. (2002b). Managing successful projects with PRINCE 2.Norwich: TSO.
79.
Office of Government Commerce. (2003). Managing successful programmes.Norwich: TSO.
80.
Office of Government Commerce. (2006). Portfolio, programme and project management maturity model (P3M3®). London, England: Office of Government Commerce.
81.
OharaS., & AsadaT. (2002). Japanese project management.Singapore: World Scientific Management Publishing.
82.
OrrR. J., & ScottW. R. (2008). Institutional exceptions on global projects: A process model. Journal of International Business Studies, 39, 562–588.
83.
PackendorffJ. (1996). Inquiring into the temporary organization: New directions for project mnagement research. Scandinavian Journal of Management, 11(4), 319–334.
84.
PellegrinelliS., PartingtonD., & GeraldiJ. (2010). Program management: An emerging opportunity for research and scholarship. In MorrisP. W. G., PintoJ. K., & SöderlundJ. (Eds.), The Oxford handbook of project management.Oxford: Oxford University Press.
85.
PinneyB. W. (2001). Projects, management, and protean times: Engineering enterprise in the United States, 1870–1960 (Doctoral dissertation). Massachusetts Institute of Technology, Cambridge.
86.
PopperK. (1959). The logic of scientific discovery.New York, NY: Basic Books.
87.
Project Management Institute. (1996). A Guide to the Project Management Body of Knowledge (PMBOK® Guide).Newtown Square, PA: Author.
88.
Project Management Institute. (2003). Organizational Project Management Maturity Model (OPM3).Newtown Square, PA: Author.
89.
Project Management Institute. (2006). The Standard for Program Management.Newtown Square, PA: Author.
90.
Project Management Institute. (2013). A guide to the project management body of knowledge (PMBOK® guide)—Fifth edition.Newtown Square, PA: Author.
91.
PrykeS. D. (2001). Analysing construction project coalitions: Exploring the application of social network analysis. Construction Management and Economics, 22, 787–797.
92.
RazT., BarnesR., & DvirD. (2003). A critical look at critical chain project management. Project Management Journal, 34(4), 24–32.
93.
ReveT., & LevittR. (1984). Organization and governance in construction. Project Management, 2(1), 17–25.
94.
RhodesR. (1988). The making of the atomic bomb.Harmondsworth: Penguin.
95.
SalomoS., WeiseJ., & GemündenH. G. (2007). NPD planning activities and innovation performance: The mediating role of process management and the moderating effect of product innovativeness. Journal of Product Innovation Management, 24, 285–302.
96.
SapolskyH. (1972). The Polaris system development: Bureaucratic and programmatic success in government.Cambridge, MA: Harvard University Press.
97.
SapolskyH. (2003). Inventing systems integration. In PrencipeA., DaviesA., & HobdayM. (Eds.), The business of systems integration (pp. 15–34). Oxford: Oxford University Press.
98.
SauerC. (1993). Why information systems fail.Henley-on-Thames: Alfred Toller.
99.
SayerR. A. (2000). Realism and social science.London, England: Sage.
100.
SchönD. (1987). Educating the reflective practitioner.San Francisco, CA: Jossey-Bass.
101.
SenseA. J., & AntoniM. (2003). Exploring the politics of project learning. International Journal of Project Management, 21(7), 487–494.
102.
ShenharA. J., & DvirD. (2007). Re-inventing project management.Cambridge, MA: Harvard Business School Press.
103.
SöderlundJ., & LenfleS. (2013). Making history: Revisiting the past, creating the futureInternational Journal of Project Management, 33, 653–662.
104.
StevensR., BrookP., JacksonK., & ArnoldS. (1998). Systems engineering: Coping with complexity.Hemel Hempstead: Prentice-Hall.
ThomasJ. (2006). Problematizing project management. In HodgsonD., & CicmilS., (Eds.), Making projects critical.Hampshire and New York: Palgrave Macmillan.
107.
ThompsonJ. D. (1967/2003). Organizations in action.New York, NY: McGraw-Hill/New Brunswick.
108.
TurnerJ. R., & KeeganA. (2001). Mechanisms of governance in the project-based organization: Roles of the broker and steward. European Management Journal, 19(3), 254–267.
109.
WardS., & ChapmanC. (2003). Transforming project risk management into project uncertainty management. International Journal of Project Management, 21(2), 97–106.
110.
WateridgeJ. (1998). How can IS/IT projects be measured for success?International Journal of Project Management, 16(1), 59–63.
111.
WendlerR. (2012). The maturity of maturity model research: A systematic mapping study. Information and Software Technology, 54, 1317–1339.
112.
WengerE. (1998). Communities of practice: Learning, meaning, and identity.Cambridge, England: Cambridge University Press.
113.
WheelwrightS. C., & ClarkK. B. (1992). Revolutionizing product development.Cambridge, MA: Harvard Business School Press.
114.
WomackJ. R., JonesD. T., & RoosD. (1990). The machine that changed the world.New York, NY: Macmillan International.
115.
YardleyD. (2002). Successful IT project delivery: Learning the lessons of project failure.Reading, MA: Addison-Wesley.