Despite the broadening use of systematic approaches to project management, the majority of related literature is focused on a handful of industries–construction, engineering, government, information technology, and utilities– that have, until recently, been the traditional areas for project management. Currently, the nontraditional project management areas include banking, pharmaceuticals, consulting, advertising, legal, health care, safety, and non-traditional manufacturing and industrial sectors (Kerzner, 2001). In recognition of growth, scholars and practitioners have begun to include viewpoints generalized across the field as well as perspectives from specific industries. We report on the findings from a systematic review of project management literature.
AdamsJ. R., & BarndtS. E. (1983). Behavioral implications of project life cycle. In ClelandD. I. & KingW. R. (Eds.), Project management handbook (pp. 222–244). New York: Van Nostrand Reinhold.
2.
ArchibaldR. (1976). Managing high-technology programs and projects.New York: Wiley.
3.
ArgyrisC., & SchönD. (1974). Theory in practice: Increasing professional effectiveness. San Francisco, Jossey-Bass.
4.
ArnoultM. D. (1972). Fundamentals of scientific method in psychology.Dubuque, IA: Wm. C. Brown Company.
5.
AshR., & Smith-DanielsD. (2004). Managing the impact of customer support disruptions on new project development projects. Project Management Journal, 35(1), 3–10.
6.
AttaranM., & AttaranS. (2001). Collaborative computing technology: The hot new managing tool. Journal of Management Development, 21, 598–609.
7.
BakerG., MurphyD., & FisherD. (1983). Factors affecting project management. In ClelandD. I. & KingW. R. (Eds.), Project management handbook (pp. 669–685). New York: Van Nostrand Reinhold.
8.
BarberE. (2004). Benchmarking the management of projects: A review of current thinking. International Journal of Project Management, 22, 301–307.
9.
BarberE., & WarnJ. (2005). Leadership in project management: From firefighter to firelighter. Management Decision, 43, 1032–1039.
10.
BassB. M. (1990). From transactional to transformational leadership: Learning to share the vision. Organizational Dynamics, 18(3), 19–31.
11.
BettsM., & LansleyP. (1995). International Journal of Project Management: A review of the first ten years. International Journal of Project Management, 13, 207–217.
12.
BourneL., & WalkerH. T. (2005). Visualising and mapping stakeholder influence. Management Decision, 43, 649–660.
13.
BowersJ. A. (2000). Interpreting float in resource constrained projects. International Journal of Project Management, 18, 385–392.
14.
BredilletC. (2003). Genesis and role of standards: Theoretical foundations and socio-economical model for the construction and use of standards. International Journal of Project Management, 21, 463–470.
15.
BrydeD. (2003). Project management concepts, methods, and application. International Journal of Operations & Production Management, 23, 775–793.
16.
BuckleP., & ThomasJ. (2003). Deconstructuring project management: A gender analysis of project management guidelines. International Journal of Project Management, 21, 433–441.
17.
BurnsJ. M. (1978). Leadership.New York: Harper & Row.
18.
ButlerA. (1973). Project management: A study in organizational conflict. Academy of Management Journal, 16(1), 84–101.
19.
CackowskiD., NajdawiM., & ChungQ. B. (2000). Object analysis in organizational design: A solution for matrix organizations. Project Management Journal, 31(3), 44–51.
20.
CameronK. S., & WhettonD. A. (1981). Perceptions of organizational effectiveness over organizational life cycles. Administrative Science Quarterly, 26, 525–544.
CaseyD. (1978). Project training for managers. Journal of European Industrial Training, 2(5), 3–6.
23.
CashC., & FoxR. (1992). Elements of successful project management. Journal of Systems Management, 43(9), 10–14.
24.
ChandlerA. (1962). Strategy and structure. In FossN. (Ed.), Resources, firms, and strategies: A reader in the resource-based perspective (pp. 40–51). New York: Oxford Press.
25.
ChatzoglouP., & MacaulayL. (1997). The importance of human factors in planning the requirements capture stage of a project. International Journal of Project Management, 15(1), 39–53.
26.
ChristensonD., & WalkerD. (2004). Understanding the role of “vision” in project success. Project Management Journal, 35(3), 39–52.
27.
CicmilS. (2000). Quality in project environments: A non-conventional agenda. International Journal & Reliability Management, 17, 540–570.
28.
CicmilS., & HodgsonD. (2006). Making projects critical: An introduction. In HodgsonD. & CicmilS. (Eds.), Making projects critical (pp. 1–25). New York: Palgrave Macmillan.
29.
DammD., & SchindlerM. (2002). Security issues of a knowledge medium for distributed project work. International Journal of Project Management, 20, 37–47.
30.
DawsonR. J., & DawsonC.W. (1998). Practical proposals for managing uncertainty and risk in project planning. International Journal of Project Management, 16, 299–310.
31.
EvaristoR., & FenemaP. (1999). A typology of project management emergence and evolution of new forms. International Journal of Project Management, 17(5), 275–281.
32.
FabiB., & PettersenN. (1992). Human resource management practices in project management. International Journal of Project Management, 10, 81–88.
33.
FlitmanA. (2003). Towards meaningful benchmarking of software development team productivity team productivity. Benchmarking: An International Journal, 10, 382–399.
34.
FoxT., & SpenceJ. (1998). Tools of the trade: A survey of project management tools. Project Management Journal, 29(3), 20–27.
35.
GaddisP. (1959). The project manager. Harvard Business Review, 37(3), 89–97.
36.
GelinasR. (1999). The just-in-time implementation project. International Journal of Project Management, 17, 171–179.
37.
GhoshP., & VargheseJ. (2004). Globally distributed product development using a new project management framework. International Journal of Project Management, 22, 699–708.
38.
GlobersonS., & ZwikaelO. (2002). The impact of project manager on project management planning processes. Project Management Journal, 33(3), 58–64.
39.
GottschalkP., & KarlsenJ. (2005). A comparison of leadership roles in internal IT projects versus outsourcing projects. Industrial Management & Data Systems, 105, 1137–1149.
40.
GowanJ., & MathieuR. (2005). The importance of management practices in IS project performance. Journal of Enterprise Information Management, 18, 235–255.
41.
GrayR. (2001). Organisational climate and project success. International Journal of Project Management, 19, 103–109.
42.
GullettR. (1972). Personnel management in project organization. Public Personnel Review, 1(3), 17–22.
43.
GussC. (1998). Virtual project management: Tools and the trade. Project Management Journal, 29(1), 22–30.
44.
HartmanF., & AshrafiR. (2002). Project management in the information systems and information technologies industry. Project Management Journal, 33(3), 5–15.
45.
HartmanF., & AshrafiR. (2004). Project management in the information systems and information technologies industry. International Journal of Project Management, 22, 499–510.
46.
HauschildtJ., KeimG., & MedcofJ. (2000). Realistic criteria for project manager selection and development. Project Management Journal, 31(3), 23–32.
47.
HendersonL. (2004). Encoding and decoding communication competencies in project management: An exploratory study. International Journal of Project Management, 22, 469–476.
48.
HenrieM., & Sousa-PozaA. (2005). Project management: A cultural literary review. Project Management Journal, 36(2), 5–13.
49.
HodgettsR. (1968). Leadership techniques in the project organization. Academy of Management Journal, 11, 211–219.
50.
IvesM. (2005). Identifying the contextual demand of project management within organizations and their impact on project success. Project Management Journal, 36(1), 37–50.
51.
JiangJ., KleinG., & ChenH. (2001). The relative influence of IS project implementation policies and project leadership on eventual outcomes. Project Management Journal, 32(3), 49–55.
52.
JiangJ., KleinG., & MeansG. (2000). Project risk impact on software development team performance. Project Management Journal, 31(4), 19–27.
53.
JohnsT. (1999). On creating organizational support for the project management method. International Journal of Project Management, 17, 47–53.
54.
JugdevK. (2004). Through the looking glass: Examining theory development in project management with the resource-based view lens. Project Management Journal, 35(3), 15–26.
55.
JugdevK., & MüllerR. (2005). A retrospective look at our evolving understanding of project success. Project Management Journal, 36(4), 19–31.
56.
KendraK., & TaplinL. (2004). Project success: A cultural framework. Project Management Journal, 35(1), 30–45.
57.
KerznerH. (1989). Project management: A system approach to planning scheduling and controlling.New York: Van Nostrand Reinhold.
58.
KerznerH. (2001). Project management: A systems approach to planning, scheduling, and controlling.New York: Wiley.
59.
KleinK. J., TosiH., & CannellaA. A.Jr. (1999). Multilevel theory building: Benefits, barriers, and new developments. Academy of Management Review, 24, 243–248.
60.
KloppenborgT., & OpferW. (2002). The current state of project management research: Trends, interpretations, and predictions. Project Management Journal, 33(2), 5–18.
61.
KotnourT. (2000). Organizational learning practices in the project management environment. Organizational Learning, 17, 393–406.
62.
LaiL. (1997). A synergistic approach to project management in information systems development. International Journal of Project Management, 15(3), 173–179.
63.
LevyN., & ShlomoG. (1997). Improving a multiproject management by using a queuing theory approach. Project Management Journal, 28(4), 40–46.
64.
LewinK. (1951). Field theory in social science: Selected theoretical papers.New York: Harper.
65.
McCrayG., PurvisR., & McCrayC. (2002). Project management under certainty: The impact of heuristics and biases. Project Management Journal, 33(1), 49–57.
66.
MilisK., & MerckenR. (2004). The use of the balanced scorecard for the evaluation of information and communication technology projects. International Journal of Project Management, 22(2), 87–97.
67.
MilosevicD., & PatanakulP. (2004). Standardized project management may increase development projects success. International Journal of Project Management, 23, 181–192.
68.
MintzbergH., & LampelJ. (1999). Reflecting on the strategy process. Sloan Management Review, 40(3), 21–30.
69.
MorrisP.W.G., PatelM. B., & WearneS. H. (2000). Research into revising the APM project management body of knowledge. International Journal of Project Management, 18, 155–164.
70.
MüllerR. (2002). Determinants for external communications of IT project managers. International Journal of Project Management, 21, 345–354.
71.
PackendorffJ. (1995). Inquiring into the temporary organization: New directions for project management research. Scandinavian Journal of Management, 11, 319–333.
72.
PattersonF., & NeaileyK. (2002). A risk register database system to aid the management of project risk. International Journal of Project Management, 20, 365–374.
73.
PennypackerJ., & GrantK. (2003). Project management maturity: An industry benchmark. Project Management Journal, 34(1), 4–11.
74.
PintoJ. (1998). Understanding the role of politics in successful project management. International Journal of Project Management, 19, 83–91.
75.
PintoJ., & PrescottJ. (1990). Planning and tactical factors in the project implementation process. Journal of Management Studies, 27, 305–327.
76.
PintoM., PintoJ., & PrescottJ. (1993). Antecedents and consequences of project team cross-functional cooperation. Management Science, 39, 1281–1297.
77.
PrabhakarG. (2005). An empirical study reflecting the importance of transformational leadership on project success across twenty-eight nations. Project Management Journal, 36(4), 53–60.
78.
Project Management Institute (PMI) Global Standard. (2004). A guide to the project management body of knowledge (PMBOK Guide®) (3rd ed.). Newtown Square, PA: Author.
79.
Project Management Institute (PMI). (2007). Who we are. Retrieved November 20, 2007, from http://www.pmi.org
80.
RazT., & GlobersonS. (1998). Effective sizing and content definition of work packages. Project Management Journal, 29(4), 17–23.
81.
RemenyiD., & Sherwood-SmithM. (1998). Business benefits from information systems through an active benefit realization programme. International Journal of Project Management, 16, 81–98.
82.
ReyckB., Grushka-CockayneY., LockettM., CalderiniS., MouraM., & SloperA. (2005). The impact of project portfolio management on information technology. International Journal of Project Management, 23, 524–537.
83.
RiveraF., & DuranA. (2004). Critical clouds and critical sets in resource-constrained projects. International Journal of Project Management, 22, 489–497.
84.
SalehY., & AlshawiM. (2005). An alternative model for measuring the success of IS projects: The GPIS model. Journal of Enterprise Information Management, 18, 47–63.
85.
SanchezA., & PerezM. (2004). Early warning signals for R&D projects: An empirical study. Project Management Journal, 35(1), 11–23.
86.
SchafferR., & ThomsonH. (1992). Successful change programs begin with results. Harvard Business Review, 70(1), 80–89.
87.
SchindlerM., & EpplerM. (2003). Harvesting project knowledge: A review of project learning methods and success factors. International Journal of Project Management, 21, 219–228.
88.
SeelyM., & DuongQ. (2001). The dynamic baseline model of project management. Project Management Journal, 32(2), 25–36.
89.
SenseA. (2003). A model of the politics of project leader learning. International Journal of Project Management, 21, 107–114.
90.
SenseA. (2005). Facilitating conversational learning in a project team practice. Journal of Workplace Learning, 17(3), 178–193.
91.
ShaniA., SenaJ., & StebbinsM. (2000). Knowledge work teams and groupware technology: Learning from Seagate's experience. Journal of Knowledge Management, 4(2), 111–124.
92.
ShenharA. (2001). One size does not fit all projects: Exploring classical contingency domains. Management Science, 47, 394–415.
93.
ShenharA., & DvirD. (1996). Toward a typological theory of project management. Research Policy, 25, 607–632.
94.
SlevinD. (1983). Motivation and the project manager. In ClelandD. I. & KingW. R. (Eds.), Project management handbook (pp. 567–580). New York: Van Nostrand Reinhold.
95.
SmithK. G., MitchellT. R., & SummerC. E. (1985). Top level management priorities in different stages of the organizational life cycle. Academy of Management Journal, 28, 799–820.
96.
SniderK., & NissenM. (2003). Beyond the body of knowledge: A knowledge-flow approach to project management theory and practice. Project Management Journal, 34(2), 4–12.
97.
SöderlundJ. (2002). On the development of project management research: Schools of thought and critique. International Project Management Journal, 8(1), 20–31.
98.
SöderlundJ. (2003). Building theories of project management: Past research, questions for the future. International Journal of Project Management, 22, 183–191.
99.
SöderlundJ. (2004). On the broadening scope of the research on projects: A review and a model for analysis. International Journal of Project Management, 22, 655–667.
TeschD., KloppenborgT., & StemmerJ. (2003). Project management learning: What the literature has to say. Project Management Journal, 34(4), 33–39.
103.
ThamhainH. (2004). Team leadership effectiveness in technology-based project environments. Project Management Journal, 35(4), 35–46.
104.
ThamhainH. & WilemonD. (1975). Conflict management in project life cycles. Sloan Management Review, 16(3), 31–50.
105.
ThiryM. (2001). Sensemaking in value management practice. International Journal of Project Management, 19, 71–77.
106.
ThiryM. (2002). Combining value and project management into an effective programme management model. International Journal of Project Management, 20, 221–227.
107.
ThiryM. (2004). “For DAD”: A programme management life-cycle process. International Journal of Project Management, 22, 245–252.
108.
ThomasP., & PintoJ. (1999). Project leadership: A question of timing. Project Management Journal, 30(1), 19–26.
109.
TrietschD. (2005). Why a critical path by another name would smell less sweet?Project Management Journal, 36(1), 17–36.
110.
TurnbullS. (2002). Preface. In SwansonR. A. & LynhamS. A. (Eds.), Theory building in applied disciplines. Advances in Developing Human Resources, 4, 219–220.
111.
TurnerJ. R., & MüllerR. (2003). On the nature of the project as a temporary organization. International Journal of Project Management, 21, 1–8.
112.
TurnerJ. R., & MüllerR. (2005). The project manager's leadership styles as a success factor on projects: A literature review. Project Management Journal, 36(1), 49–61.
113.
UrliB., & UrliD. (2000). Project management in North America, stability of the concepts. Project Management Journal, 31(3), 33–43.
114.
WalkerD., & ChristensonD. (2005). Knowledge wisdom and networks: A project management centre of excellence example. The Learning Organization, 12, 275–291.
115.
WangE., ChouH. W., & JiangJ. (2005). The impacts of charismatic leadership style on team cohesiveness and overall performance during ERP implementation. International Journal of Project Management, 23, 173–180.
116.
WardS., & ChapmanC. (2003). Transforming project risk management into project uncertainty management. International Journal of Project Management, 21, 97–105.
117.
WellerA. C. (2002). Editorial peer review: Its strengths and weaknesses.Medford, NJ: American Society for Information Science and Technology.
118.
WhiteD., & FortuneJ. (2002). Current practice in project management—An empirical study. International Journal of Project Management, 20, 1–11.
119.
WhittyS. (2005). A memetic paradigm of project management. International Journal of Project Management, 23, 575–583.
120.
WilemonD., & CieroJ. (1970). The project manager: Anomalies and ambiguities. Academy of Management Journal, 13, 269–282.
121.
YaoK. T., & QiuF. (2002). The value of management flexibility—A real option approach to investment evaluation. International Journal of Project Management, 21, 243–250.
122.
YuA., FlettP., & BowersJ. (2005). Developing a value-centred proposal for assessing project success. International Journal of Project Management, 23, 428–136.
123.
ZimmerT., & YasinM. (1998). The leadership profile of American project managers. Project Management Journal, 29(1), 31–38.
124.
ZwikaelO., ShimizuK., & GlobersonS. (2005). Cultural differences in project management capabilities: A field study. International Journal of Project Management, 23, 454–462.
