دفاتر مدیریت پروژه : یک مورد از الگوی اصلی مبتنی بر دانش

While Project Management Offices (PMOs) have become a mainstay in organizations, systematic research has not yet been undertaken to study their intricacies. In this paper, we conduct an exploratory and descriptive case study of PMOs, based on our interviews with senior managers and directors of PMOs in 32 IT organizations. The objectives are to: (1) outline the nature and characteristics of PMOs; (2) classify and derive archetypes of PMOs; and (3) enumerate critical success factors of PMOs. To the best of our knowledge, this is the first paper to systematically investigate PMOs from a knowledge archetype perspective. A novel and significant contribution of this paper is the case description of four PMO archetypes, which clearly delineate PMOs based on their knowledge management functions and capabilities.

Much of the work conducted in organizations occurs as projects (Keil, Mixon, Saarinen, & Tuunainen, 1995). Project-based work is especially popular in the information technology domain. Statistics indicate that between 50% and 80% of IT projects are unsuccessful—they either fail to deliver on time, overstep budgeted estimates of resources and time, do not meet customer requirements, or fall short of customer expectations (Keil & Robey, 2001; Keil et al., 2000). This alarming scenario is hardly surprising—too many organizations tend to repeat the same mistakes too often, particularly in terms of knowledge transfer and reuse of the information derived from past projects (Collier, De Marco, & Fearey, 1996; Desouza, Dingsøyr, & Awazu, 2005). Some of the primary reasons for project failures are a result of poor knowledge management: lack of effective project estimation and budgeting, poor communication and information sharing practices, inadequate reuse of past experiences and lessons learned, and insufficient understanding of the technology, particularly its limitations. Other typical reasons are lack of consistency in management, lack of formal tracking, and lack of functional user involvement. The end result is overruns in cost and time through restarts or projects routinely abandoned before completion. Establishing a Project Management Office (PMO) is one strategy that can be used to resolve these persistent problems—it is a source of centralized integration and a repository of knowledge which can be used to inform more effective and efficient IT project management. A well-implemented PMO can resolve the most challenging project management issues by capturing and transferring knowledge, maximizing the power of cross-functional teams, regulating the demand of integrated technologies, and providing ownership and accountability for key efforts. Moreover, it can fully assess the impact and risk of change and provide projects with guidance on best practices and standards. PMOs have been common in the telecom, aerospace, and defense industries for decades now. Much of this can be attributed to the fact that in the life-blood of work in such organizations occurs in the form of multi-million (or billion) dollar projects. IT organizations began to develop PMOs in the pre-2000 era to oversee projects involved with Y2K transitions. PMOs were originally conceived as a means of capturing and disseminating good project management practices and project knowledge throughout the organization. Due to the success rate of Y2K transitions, many organizations continued with PMOs and extended their scope of activity to include analysis, communication, and decision support. The newer objectives were to improve Project Management (PM) skills and communication, follow a standardized and consistent methodology, and monitor projects for progress within time and budget. In recent years, many organizations have implemented PMOs to help lower the typical risks facing projects. Whether implementing a one-time project with a defined start and end, or running an ongoing program with several projects, experienced project and program management are essential for successful, on-time, within-budget delivery. A PMO is seen to combine the deliverable and focused discipline of project management with the conceptual and analytical strengths of business consultancy. CIO Magazine and the Project Management Institute (PMI) surveyed 450 managers and found that 67% of their organizations had a PMO in place. The same survey concluded that the longer a PMO was operative, the higher was its impact on improving project success. The findings conclusively indicate that PMOs can instill project management discipline and align project management processes with an organization's overall strategic objectives. The objective of this paper is to describe PMOs and outline the major knowledge-based archetypes. To the best of our knowledge, this is the first paper to systematically investigate PMOs from a knowledge archetype perspective. We conducted semi-structured interviews with PMO managers or directors in 32 IT organizations.

The primary purpose of a PMO is to centralize information in order to create a knowledge base. An organization would profit from the time and effort it takes to define the right PMO archetype to match its corporate culture and goals. A well-defined, effective PMO can be an important step to greater success for the organization. Administrative PMOs typically document and disseminate project reports, lessons learned and best practices, but here tacit knowledge from projects is difficult to capture. Knowledge-intensive PMOs create collaborative communities for project managers to share knowledge and learning that may be difficult to capture and document through conventional mechanisms. The synergy of project management and knowledge management concepts creates a sturdy knowledge-based framework that enables sharing of project knowledge and lessons learned, and promotes the cross-pollination of ideas. Knowledge-based PMOs, therefore, promote wider organizational involvement and support and facilitate ownership of project management knowledge.