The Federation Square Project Senior Executive Report

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 Federation Square project had a very aggressive schedule in order to be complete by the

Melbourne’s Federation Square was a Victorian Government initiative that was announced in 1996, with support from Melbourne City Council and the Commonwealth Government. The initial projected cost of the structure was estimated at $110 million, with a completion date of December 2000 (Matters of Public Interest 2003). The final estimated cost was over $470 million, with the official opening occurring in October 2002, even though the construction was not complete (Misiak 2003) (ABC 2003). Being such a high profile, exposed, arduous project, there were many factors that contributed to the various shortfalls over the 6-year timeframe. This report aims to identify key knowledge areas within project management and discuss improvements that could have been made to streamline the task and improve overall continuity.

Projects are used today as a way of achieving a variety of outcomes in local or international locations for new constructions, new product development, product improvement, process design, process improvement, utility installation, theory and technology development, and many more. Bringing a project to a successful conclusion requires the integration of numerous management functions like controlling, directing, team building, communication and others. It also requires cost and schedule management, technical and risk management, conflict and stakeholder 's management, and life cycle management.

Table of Contents Section I. II. III. Executive Summary Introduction Project Organization Organization Chart Project Responsibilities Staffing Plans IV. Management Process Management Objectives Priorities Monitoring/Controlling Mechanisms V. Technical Process Plan Computing System Project Plan Modification Process Computer Usage Policies Construction Guideline Support Project Acceptance Process Lessons Learned Documentation VI. Work Packages, Dependencies, Schedules & Budgets Work Packages Dependencies

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

The purpose of this paper is to show provide a case study of the Enlarged Cotter Dam project in Canberra, Australia. This paper will use the 5 dimensions of project management as the guide and layout.

The Project Management Body of Knowledge (PMBOK) is a collection of processes and knowledge areas generally accepted as best practice within the project management discipline. PMBOK recognises 5 basic process groups and 9 knowledge areas typical of almost all projects. The basic concepts are applicable to projects, programs and operations. The five basic process groups are:

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

This document is an annotated outline for a Project Management Plan, adapted from the PMI Project Management Body of Knowledge (PMBOK) and IEEE Standard for Project Management Plans. The Project Management Plan is considered to be a “Best Practice” template by the ETS Enterprise Program Management Office (EPMO).

While projects can be similar in some instances, no two projects are ever the same. For this reason, management of projects requires the application of tools and techniques to meet the goals of the temporary endeavor. Project managers apply these tools and techniques to determine what is required for project delivery such as the list of activities to completed, the time required to complete the activities, resources needed and the various risks associated with the deliverable and efforts. A multitude of tools and techniques are employed by the project manager based on the need of the effort to organize, identify and communicate the various aspects of the project. While in contrast, the repetitive nature of operations activities

In this report, it will use Project Management Body of Knowledge (PMBOK) to analysis Shanghai Maglev Train Project Plan. PMBOK is an inclusive term that describes the sum of knowledge within the profession of Project Management; it involves project integration, scope, HR, cost, quality, communications, risk, procurement, and time management.

The stage of constructing Federation Square had seen some major challenges during the developments lifecycle; the project had seen a change in government in 2001 which inflicted changes to the proposed design of the complex to please heritage critics. As a result the projects final construction cost exceeded well above its estimated budget, the final total was approximately $467 million (AUS) which was over four times the original estimated budget.

1. Discuss the project management organization on the project. Strengths? Weaknessess? Recommendations. Parks Corporation used a matrix project management organization on the Blue Spider Project. It was a multi-disciplinary team where the members came from different functional units such as Research and Development, Engineering, Manufacturing, Quality Control, Purchasing, and Finance. Gary Anderson, the Project Manager, was responsible for the project but his responsibility for performance of the individual phases of the work to be accomplished on the project remained with the functional managers. Anderson assigned, monitored, and coordinated work among the project team. But, the functional managers had

This report was compiled by a team of professional project managers and gives an objective insight to the project in full.