Harvard Business School: the Atekpc Project Management Office

In order for an organization to remain successful, it must be able to fulfill its day-to-day operations without mistakes. If these demands cannot be met, a new project must be created in order to stay in business and ahead of the competition. If an organization has a problem, they can benefit from fixing it by following a formal process for identifying, selecting, initiating, and planning projects (Valacich, 2009).

3) Is it acceptable for the PMO to report to the chief information officer or to someone else?

According to A Guide to the Project Management Body of Knowledge (PMBOK® Guide), - Third Edition,

The paper is divided into three sections, the first of which will establish a timeline of events. This project background will serve as a case study for the analysis in the following section that will be structured such that each of the previously mentioned facets will be independently analyzed and contrasted with project management principles. Finally the paper will conclude with a summary of the analysis and recommendations based on

The lack of having a Project Management Office (PMO) within Multi Projects Inc. that can assist with policy

Project Management Institute. (2000). _A Guide to the Project Management Body of Knowledge (4th ed.)._

In today’s competitive economic climate, most project managers and organizational leadership has concluded the importance of the positive impact that project management leadership has contributed to the organization and on their projects and programs. This positive impact has caused most organizations to implement Project Support Offices (PSO). Within the Project Support Offices (PSO) there will be an understanding of the importance of the as-is and the to-be process is to managing projects and programs. The Project Support Office (PSO) uses this very effective technique in transforming vision into results. This technique is used to develop and populate an As-Is and To-Be diagrams. The As-Is diagram depicts the present state of the organizations, project or program process, culture, and capabilities. The To-Be diagram depicts the desired future state of how the organizations process, culture, and capabilities will look in the future. This case study reviews the goals confronted by the Pizza Delivered Quickly (PDQ) business while further developing the multiple related sub-systems to achieve the Pizza Delivery Quick (PDQ) requirements and be able to manage the project (Wysocki, 2012).

To understand which services were most important to the AT&T Project Management Community, the PMCOE distributed both company-wide and business unit surveys to identify problem areas (e.g. leadership support, adequate training, etc.) and determine what needs its audience had which could potentially be met by the center. Initial discussions and survey findings helped to tailor the PMCOE offerings to provide the best payback of investment for both the PM Community and PMCOE efforts.

Limitations: o Shortage of PMO expert resources; o Staff consisted of: PMO director + 3 contract project managers. Project charter introduced “idea form” = used to prioritize projects. PMO responsibilities: o Establish, publish, and disseminate project practices, standards and tools; o Add Later – Portfolio Management & Archiving of projects for knowledge sharing.

The role of the project management office (PMO) has increased nowadays, as many organizations are implementing it. According to PMI (PMI 2011), organizations with a PMO report more projects coming in on time, on budget and meeting intended goals to those without a PMO.

This business case outlines how the CPOE Project will address current business concerns, the benefits of the project, and recommendations and justification of the project. The business case also discusses detailed project goals, performance measures, assumptions, and constraints.

Tran-Tan, N. (2011). CPOE Implementation Barriers in Healthcare Organizations. Business Advantage Services, INC. Retrieved from http://bas-consulting.net/consulting2/?p=15

Project Management Office (PMO) and Agile method are highly reputable terms in many organizations, especially in their IT projects. The PMO is a group of people or committee within an organization that is responsible to define and maintain standards and practices for traditional project management. The ultimate objective for the PMO is to gain the benefits that are derived from applying Project Management (PM) methods, practices and policies. Thus, the PMO over time will become the origin for documentation, guidance and metrics regarding to any practices that are involved in managing projects within the organization, as well as it will be the communication channel that

As according to the AtekPC Project Management Office case, the purpose1 of a PMO is to fulfill the need for greater discipline in managing IT projects. Moreover, it establishes or enhances project management skills, process, and governance structures within an organization (Applegate Pg. 462). The director of Application Development, Richard Steinberg, described AtekPC’s PMO’s purpose as a “methodology” for managing projects with standardized practices. As stated within the case, the main purpose of the PMO is to provide standardization in managing projects of large, complex scales as well as gain improvements in planning and performance of initiatives (Applegate Pg. 465). The case generalizes

• Past evidence to manage big projects:- In year 2000, conversion of order management AtekPC used project management approach. They got everyone together and got it done smoothly. Everyone appreciated it and said it was done well.