The PRS (Performance Right Industry) is a non-profit organization in the United Kingdom that collects the royalties for the holder of the copyrights of music songs when they are performed at a concert or played at the radio. With the guardianship of the musical performance rights from over 750,000 copyright holders and a £155 million collected from 26,000 UK members each year the PRS has a complex role. It is controlled by the General Council, which is responsible for the administration and formulation of the policy. The management team consists of a CEO and his team of executive directors who are responsible for the day-to-day running of the business. For the complex administration processes several distinct applications are running on multiple mainframe computers.
The PROMS (Performance Rights On-Line Membership System) project was conceived in 1987 with its aim to get rid of the mainframe computers and replace them through several mini computers. The data and mainframe applications should be combined into one coherent database to reduce the redundant sets of identical information stored on different computer systems. The new system should allow 300 people to use the computers concurrently. Therefore a special OLTP application was needed to provide adequate response times for all users. Concerning this application, which required a high performance hard- and software environment, there was a heavy debate in the industry about the feasibility to use such a demanding software on minicomputers. For this reason the project required a careful design and planning. (The Performing Rights Society - Case Facts, no year)
Table of Contents
1 HISTORY OF THE PROJECT
2 MAJOR DECISIONS TAKEN DURING THE PROJECT
3 PROBLEMS ENCOUNTERED
4 ATTEMPTED SOLUTIONS
5 REPORTED EVALUATION
6 ANALYSIS OF THE PROJECT
6.1 Project Integration Management
6.2 Project Scope Management
6.3 Project Time Management
6.4 Project Cost Management
6.5 Project Quality Management
6.6 Project Human Resource Management
6.7 Project Communication Management
6.8 Project Risk Management
6.9 Project Procurement Management
7 MY APPROACH
8 REFERENCES
Objectives and Topics
The primary objective of this assignment is to conduct a critical analysis of a real-life IT project, specifically the PROMS project, to identify the management failures that led to its collapse. The work investigates how deficiencies in project management frameworks directly contributed to the project's inability to meet its objectives, focusing on the lack of control, poor planning, and communication breakdowns.
- Analysis of project management failures in the PROMS case study.
- Evaluation of the nine knowledge areas of project management according to standard frameworks.
- Assessment of the importance of project phases and progress control.
- Critique of stakeholder management and communication strategies.
- Development of a recommended approach for successful IT project execution.
Excerpt from the Book
6 Analysis of the project
Examining the project one will find a lot what actually went but should not go wrong in such a large project. The first obvious thing to mention is that they did not divide the project into different phases. They are essential to the project’s success since they provide better management control. Achieving its deliverables, followed by a thorough review (called phase exit or kill point) to determine whether the project should continue with the outcome of the phase or not, completes a phase. In that way errors can be identified and corrected more efficient. Since PRS did not split the project into phases and did not allocate deliverables to them they recognized the flaws at a point where there was no correction possible. Due to that the management did not have the basic control over the project’s development. (Duncan, 1996)
All processes within the project lacked one very important component, the controlling process. As stated above the missing kill points neglected the question whether the process was successful or not. So they could not ensure whether the project objectives are met since they did not monitor or measured progress properly. The PRS submitted reports to the General Council, but they were kept confidentially, so nobody was informed about the status of the project. The reports did not fulfil their intention and no flaws could be detected and corrected.
Summary of Chapters
HISTORY OF THE PROJECT: Outlines the background of the PRS organization and the conceptualization of the PROMS project aimed at modernizing IT infrastructure.
MAJOR DECISIONS TAKEN DURING THE PROJECT: Details the initial feasibility and requirements phases and the subsequent management actions that ultimately led to the project's suspension.
PROBLEMS ENCOUNTERED: Identifies specific operational failures, including database design flaws, performance issues, and the inability to meet deadlines.
ATTEMPTED SOLUTIONS: Describes the management's reaction to delays and the subsequent efforts to salvage the project through updated plans and external consultant assessments.
REPORTED EVALUATION: Analyzes the systemic failures in management and decision-making that characterized the project's lifecycle.
ANALYSIS OF THE PROJECT: Provides a comprehensive critique of the project based on nine distinct areas of project management, such as scope, time, cost, and risk.
MY APPROACH: Proposes a structured methodology for future projects, emphasizing proper planning, phase definition, and stakeholder communication.
REFERENCES: Lists the academic and professional sources used to support the critical analysis.
Keywords
Project Management, IT Project, PROMS, Performance Right Industry, Scope Management, Risk Management, Project Failure, Database Development, Stakeholder Analysis, Feasibility Study, Project Planning, Quality Management, System Integration, Business Case, Controlling Process.
Frequently Asked Questions
What is the primary focus of this work?
The work provides a critical analysis of the real-life PROMS IT project, examining the reasons behind its failure from a project management perspective.
What are the central themes discussed?
The central themes include the application of project management knowledge areas, the necessity of project phases, and the critical importance of effective stakeholder communication.
What is the primary research goal?
The goal is to identify specific management deficiencies and demonstrate how these flaws prevented the project from meeting its operational and financial goals.
Which methodology is used to evaluate the project?
The author uses a structured critique based on standard project management frameworks, breaking down the analysis into the nine recognized areas of project management.
What does the main body cover?
The main body systematically applies project management principles to the PROMS project, identifying failures in integration, scope, time, cost, quality, human resources, communication, risk, and procurement.
Which keywords characterize the analysis?
Key terms include project failure, scope management, risk assessment, and stakeholder communication.
Why was the PROMS project's database design considered inefficient?
The design suffered from insufficient input and vague requirements, leading the contractor to make erroneous assumptions that resulted in unacceptable response times.
What role did external consultants play in the project's outcome?
The report suggests that consultants were often biased or lacked the independence necessary to provide critical assessments, which hindered the project's ability to correct its course early on.
- Quote paper
- Thomas Kramer (Author), 2000, Critique of a real life IT Project, Munich, GRIN Verlag, https://www.grin.com/document/1897
