SlideShare a Scribd company logo
GROUP 3:
NORIZZA SYAFIQAH BAHRIN P65408
 NURUL LIYANA BT. RUSMAN p61498
         SARAH BT. ISMAIL P65378
Definition:
 Failure to meet one or more of the four primary
 project metrics (Performance, Cost, Time and Scope)
 that results in the failure of the entire projects as it
 pertains to the organizational goal.
Performance

When the deliverable does not
 meet the requirement:

Failure to address
 expectations
Poor training
Poor quality control
Subjective validation
Cost
When the project’s allocated
 budget is exceeded

Money is an issue for most
  companies and is one of the
  few measures that can be a
  big indicator or cause of
  failure

“You have a great product, but
  it cost too much to get it
  done!
Time
  When the project was not
  completed within the
  allocated time frame

Poor planning or impossible
 imposed deadline?
“How much longer must we
 wait on this?
Scope
When the costumers don’t get
 what they ask for..
Keys to failure : poor
 communication and
 interpretation

  Example
“I want a spoiler”

For any given project, scope can
  be used to determine
  whether a project is complete
“Those projects that do not meet the original
 time,cost and quality requirements criteria”
   (Dr John Mcmanus and Dr trevor Wood
                  Harper)
project is success if it
achieves all of the agreed
   “project objectives”

 a project must deliver to
   cost, to quality, and
          on time.

      a project must
    deliver the benefits
project succes
Why do projects fail?
... perhaps processes got worse rather than better,
 maybe they were cancelled because of cost overruns,
 or perhaps systems were launched with fundamental
 errors.
How do you know when – and why – a project has
 failed? In many cases, the reason for failure is obvious.
 However, the definition of failure isn't always clear:
 one project with a significant delay might be
 described as a failure; yet another, with a similar
 delay, might be seen as a stunning success.
Common Causes of Project Failure
1.Lack of clear links between the project and the
  organisation's key strategic priorities, including
  agreed measures of success.

2. Lack of clear senior management and Ministerial
  ownership and leadership.

3. Lack of effective engagement with stakeholders.
Common Causes of Project Failure
4. Lack of skills and proven approach to project
  management and risk management.

5. Too little attention to breaking development and
  implementation into manageable steps.

6. Evaluation of proposals driven by initial price rather
  than long-term value for money (especially securing
  delivery of business benefits).
Common Causes of Project Failure
7.Lack of understanding of, and contact with
the supply industry at senior levels in the organisation.

8.Lack of effective project team integration between
  clients, the supplier team and the supply chain.
Undefined
          objectives and
              goals
                           •Lack of management commitment
                                •Poorly defined roles and
                                     responsibilities
             Poorly               •Poor communication
PROJECT     managed                 •Team weakness
FAILURE                      •Lack of organizational support


            Stakeholder
              conflicts

            Insufficient     •Enterprise management of budget
                                          resources
             Resources      •Estimates for cost and schedule are
                                         erroneous
           (funding and               •Business politics
            personnel)             •Competing priorities
project succes
 Lack of agreements on goals
No written project
implementation plan
Rapidly growing project
Repeated contract modification
Project managed solely by
contractor
Major deliverables are late
PROJECT MANAGEMENT FAILURE
                   MARCH 2013




                          GROUP 3
Sydney Opera
   House




               GROUP 3/MARCH 2013
Sydney Opera House
Background




                     GROUP 3/MARCH 2013
Sydney Opera House
Background
Problems appeared from the start of the project:
   Utzon protested that he had not completed the designs for the structure,
      but the government insisted that the construction get underway.
     The government changed the requirements of the design after the
      construction was started, from two theatres to four, so plans and designs
      had to be modified during construction.
     Since the design created by Utzon had never been done , Utzon still
      altered the geometry of his design even after four years of construction.
     During the year of 1965 a new government was appointed in NSW and
      they withheld payments for Utzon’s plans as they opposed to his building
      methods.
     This forced Utzon to resign from the project in 1966 and a team of
      Australian architects were appointed to finish the construction.


                                                                GROUP 3/MARCH 2013
Sydney Opera House
 If Utzon, in cooperation with the engineering team, would have had the
  chance to finish the design, the estimation of the project cost would probably
  been so high that the project would never have been implemented. The
  involvement of engineers and suppliers at an early stage in the process was a
  criteria for the successful outcome of the project.
 Utzon’s delay and withholding of the designs he created, caused a problem of
  learning for the next architect who took over. For these reasons, and more,
  Utzon was seen to be a dangerous stakeholder, and his power in the project
  led to erratic decisions and many re-designs.
 Utzon’s ability to oppose his will without having legitimacy was a direct
  consequence of SOHEC’s lack of urgency.




                                                                 GROUP 3/MARCH 2013
Sydney Opera House
 While the NSW government was absent in a lot of the management decisions,
  it was ultimately Utzon’s responsibility to monitor his own actions and focus
  on the goal in respect to the client. His lack of self control gave the definitive
  stakeholder, the NSW government, an opportunity to remove him from
  power.
 If stakeholders throughout this project were managed properly, cost over runs
  and re-designs could have been minimized. Through this analysis, it has
  shown the importance of identifying stakeholders, and how their influence
  can affect the outcome of the processes of such a project.




                                                                    GROUP 3/MARCH 2013
project succes
Spent the time to define the project objectives,
 scope, assumptions, risks, budget, timeline,
 organization, and overall approach.
Differences of opinion between the major
 stakeholders need to be resolved before the project
 starts
Project manager (PM)needs to create an overall
 project work plan before the project starts.
PM need to ensure he detailed work mapped out over
 the next few months to ensure that the project
 resources are assigned correctly once the project
 actually begins
project succes
project succes

More Related Content

PPTX
Sydney opera house
PPTX
Introduction to Project Management (workshop) - v.1
PDF
Definitions Of Project
PPT
2. characteristics of a projec
PPTX
Project initiation topic 2.7_the project manager
PPTX
Managing scope creep in IT projects
PPT
1 Definition of project
PPT
Architectural Professional Practice - Programming الممارسة المهنية المعمارية ...
Sydney opera house
Introduction to Project Management (workshop) - v.1
Definitions Of Project
2. characteristics of a projec
Project initiation topic 2.7_the project manager
Managing scope creep in IT projects
1 Definition of project
Architectural Professional Practice - Programming الممارسة المهنية المعمارية ...

What's hot (20)

PDF
Introduction to Project Management
PPT
Project Mng Basics Belarusian State University Final
PDF
How Do Product Development Projects Really Work?
PPTX
Critical Success Factors Affecting Project Performance in Turkish IT Sector -...
PDF
Dealing With Troubled Projects in 8 Simple Steps
PPTX
Introduction to project management
PDF
Introduction to Project Management
PDF
Identifying and Recovering Troubled Projects
PDF
What is PRINCE2 Project Managment
PPTX
Ppt for Real Estate Project
PPTX
Project management process and Project Management Knowledge areas
PDF
Seven Habits of a Highly Effective agile project manager
PPS
Managing Small Projects Introduction
PPTX
S11 Project Closure Controlling and Review
PPTX
Presentation of project management (907, scm. mir mohammed shorab hossein)
PPTX
Basics of project management - Week 1
PDF
The 25/10 Concept - Improving the Probability of Success
PDF
Project management
PPT
Project and use of project management tools and techniques
PPSX
Project Management Fundamentals
Introduction to Project Management
Project Mng Basics Belarusian State University Final
How Do Product Development Projects Really Work?
Critical Success Factors Affecting Project Performance in Turkish IT Sector -...
Dealing With Troubled Projects in 8 Simple Steps
Introduction to project management
Introduction to Project Management
Identifying and Recovering Troubled Projects
What is PRINCE2 Project Managment
Ppt for Real Estate Project
Project management process and Project Management Knowledge areas
Seven Habits of a Highly Effective agile project manager
Managing Small Projects Introduction
S11 Project Closure Controlling and Review
Presentation of project management (907, scm. mir mohammed shorab hossein)
Basics of project management - Week 1
The 25/10 Concept - Improving the Probability of Success
Project management
Project and use of project management tools and techniques
Project Management Fundamentals
Ad

Similar to project succes (20)

PPTX
PM3
PPTX
Case study 1 (zaileha,suryani,anis,ilyana) version 2
PPTX
Case study 1 (zaileha,suryani,anis,ilyana)
PDF
AICD Presentation - Project Management for Directors
PPTX
UNIT-1.pptx
DOCX
Drs 255 project management skills
DOC
Project failure reason 1
PPTX
Top 10 project mgt. problems
PDF
How to Avoid Project Train Wrecks
PDF
Impact of eLearning Scope Creep_ A Project Manager's Guide.pdf
PPT
TCCD PROJECT Failureeeeeeeeeeeeeeeee.ppt
DOCX
project management 1.docx
PDF
2. MID Note_ProMana_Chap 1-6okokokok.pdf
PPTX
10 reasons why projects fail or common mistakes to avoid
PDF
م.58-مبادرة#تواصل_تطوير-د.وليد محفوظ-إدارة مشاركة المعنيين في مشاريع وبرامج ا...
PDF
10 Project Management Mistakes
PPTX
PROJECT MANAGEMENT intro - Lecture 01.pptx
DOCX
Project management : Pert and Cpm
PPT
Project Management Tools and Techniques
PM3
Case study 1 (zaileha,suryani,anis,ilyana) version 2
Case study 1 (zaileha,suryani,anis,ilyana)
AICD Presentation - Project Management for Directors
UNIT-1.pptx
Drs 255 project management skills
Project failure reason 1
Top 10 project mgt. problems
How to Avoid Project Train Wrecks
Impact of eLearning Scope Creep_ A Project Manager's Guide.pdf
TCCD PROJECT Failureeeeeeeeeeeeeeeee.ppt
project management 1.docx
2. MID Note_ProMana_Chap 1-6okokokok.pdf
10 reasons why projects fail or common mistakes to avoid
م.58-مبادرة#تواصل_تطوير-د.وليد محفوظ-إدارة مشاركة المعنيين في مشاريع وبرامج ا...
10 Project Management Mistakes
PROJECT MANAGEMENT intro - Lecture 01.pptx
Project management : Pert and Cpm
Project Management Tools and Techniques
Ad

project succes

  • 1. GROUP 3: NORIZZA SYAFIQAH BAHRIN P65408 NURUL LIYANA BT. RUSMAN p61498 SARAH BT. ISMAIL P65378
  • 2. Definition: Failure to meet one or more of the four primary project metrics (Performance, Cost, Time and Scope) that results in the failure of the entire projects as it pertains to the organizational goal.
  • 3. Performance When the deliverable does not meet the requirement: Failure to address expectations Poor training Poor quality control Subjective validation
  • 4. Cost When the project’s allocated budget is exceeded Money is an issue for most companies and is one of the few measures that can be a big indicator or cause of failure “You have a great product, but it cost too much to get it done!
  • 5. Time When the project was not completed within the allocated time frame Poor planning or impossible imposed deadline? “How much longer must we wait on this?
  • 6. Scope When the costumers don’t get what they ask for.. Keys to failure : poor communication and interpretation Example “I want a spoiler” For any given project, scope can be used to determine whether a project is complete
  • 7. “Those projects that do not meet the original time,cost and quality requirements criteria” (Dr John Mcmanus and Dr trevor Wood Harper)
  • 8. project is success if it achieves all of the agreed “project objectives” a project must deliver to cost, to quality, and on time. a project must deliver the benefits
  • 10. Why do projects fail? ... perhaps processes got worse rather than better, maybe they were cancelled because of cost overruns, or perhaps systems were launched with fundamental errors. How do you know when – and why – a project has failed? In many cases, the reason for failure is obvious. However, the definition of failure isn't always clear: one project with a significant delay might be described as a failure; yet another, with a similar delay, might be seen as a stunning success.
  • 11. Common Causes of Project Failure 1.Lack of clear links between the project and the organisation's key strategic priorities, including agreed measures of success. 2. Lack of clear senior management and Ministerial ownership and leadership. 3. Lack of effective engagement with stakeholders.
  • 12. Common Causes of Project Failure 4. Lack of skills and proven approach to project management and risk management. 5. Too little attention to breaking development and implementation into manageable steps. 6. Evaluation of proposals driven by initial price rather than long-term value for money (especially securing delivery of business benefits).
  • 13. Common Causes of Project Failure 7.Lack of understanding of, and contact with the supply industry at senior levels in the organisation. 8.Lack of effective project team integration between clients, the supplier team and the supply chain.
  • 14. Undefined objectives and goals •Lack of management commitment •Poorly defined roles and responsibilities Poorly •Poor communication PROJECT managed •Team weakness FAILURE •Lack of organizational support Stakeholder conflicts Insufficient •Enterprise management of budget resources Resources •Estimates for cost and schedule are erroneous (funding and •Business politics personnel) •Competing priorities
  • 16.  Lack of agreements on goals No written project implementation plan Rapidly growing project Repeated contract modification Project managed solely by contractor Major deliverables are late
  • 17. PROJECT MANAGEMENT FAILURE MARCH 2013 GROUP 3
  • 18. Sydney Opera House GROUP 3/MARCH 2013
  • 19. Sydney Opera House Background GROUP 3/MARCH 2013
  • 20. Sydney Opera House Background Problems appeared from the start of the project:  Utzon protested that he had not completed the designs for the structure, but the government insisted that the construction get underway.  The government changed the requirements of the design after the construction was started, from two theatres to four, so plans and designs had to be modified during construction.  Since the design created by Utzon had never been done , Utzon still altered the geometry of his design even after four years of construction.  During the year of 1965 a new government was appointed in NSW and they withheld payments for Utzon’s plans as they opposed to his building methods.  This forced Utzon to resign from the project in 1966 and a team of Australian architects were appointed to finish the construction. GROUP 3/MARCH 2013
  • 21. Sydney Opera House  If Utzon, in cooperation with the engineering team, would have had the chance to finish the design, the estimation of the project cost would probably been so high that the project would never have been implemented. The involvement of engineers and suppliers at an early stage in the process was a criteria for the successful outcome of the project.  Utzon’s delay and withholding of the designs he created, caused a problem of learning for the next architect who took over. For these reasons, and more, Utzon was seen to be a dangerous stakeholder, and his power in the project led to erratic decisions and many re-designs.  Utzon’s ability to oppose his will without having legitimacy was a direct consequence of SOHEC’s lack of urgency. GROUP 3/MARCH 2013
  • 22. Sydney Opera House  While the NSW government was absent in a lot of the management decisions, it was ultimately Utzon’s responsibility to monitor his own actions and focus on the goal in respect to the client. His lack of self control gave the definitive stakeholder, the NSW government, an opportunity to remove him from power.  If stakeholders throughout this project were managed properly, cost over runs and re-designs could have been minimized. Through this analysis, it has shown the importance of identifying stakeholders, and how their influence can affect the outcome of the processes of such a project. GROUP 3/MARCH 2013
  • 24. Spent the time to define the project objectives, scope, assumptions, risks, budget, timeline, organization, and overall approach. Differences of opinion between the major stakeholders need to be resolved before the project starts Project manager (PM)needs to create an overall project work plan before the project starts. PM need to ensure he detailed work mapped out over the next few months to ensure that the project resources are assigned correctly once the project actually begins