Project Success/Failure

7,992 views
7,628 views

Published on

Presentation to ISACA Governance Event 11 Sept 2009 on factors affecting Project Success/Failure referencing ISO38500, Project Management, Standish and the CHAOS Report, also Sauer et all, Cadbury and drawing on Peter Salmon's varied and extnesive personal experience

Published in: Business, Health & Medicine
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
7,992
On SlideShare
0
From Embeds
0
Number of Embeds
268
Actions
Shares
0
Downloads
305
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • Peter Salmon - the principal of Manning Charles & Associates Ltd. A senior executive with strong operational management experience, Peter’s past experience includes leading the Systems Integration practice for a major vendor in the South Pacific as well heading the Project Quality Office for the same company in the region.
  • Insert the Project Lifecycle diagram
  • Man on Moon, RWC bid, relate purchase of vegetables and why it is a project and how we all do projects regularly, structures, plan shopping list and comply with the governance model, illustrate how everyday tasks can fit the model and causes of success failureUse another definition from PMBOKKeywords in the definition are: temporary & unique outcome.* Temporary – It has definite beginning and end time. * Unique Product, Services or Results – One other important inherent characteristic of Projects is progressive elaboration. Progressive elaboration means developing in steps, and continuing by increments.
  • People/leadership, thin line, resource, , unfortunately it would appear that in the IT world failure is more common than successGartner studies suggest that 75% of all US IT projects are considered to be failures by those responsible for initiating them. Standish Group 2009 report, US based, found that 31% of projects were cancelled outright and that the performance of 53% of the all projects was so worrying that they were challenged.Some questions that need to be answered in assessing whether a project is fundamentally a success or failure?Has the project satisfied the business requirements of the primary stakeholders?Were the deliverables produced on time and within budget (or as amended by agreed change control)?Do the business owners perceive the project to be successful?Has the project delivered the business value promised in the original case for doing it
  • Increasingly controversial Chaos Report
  • Sauer gives a completely different picture. Sauer used input from UK based PMs, Standish draws on US based executive perceptionsNevertheless it is not a pretty picture and why is it still happening
  • Amongst other matters these are some of the factors that impact on success or failureTo my mind the success factors tend to suggest that governance has an impactPoor suucees rate, need for an effective framework
  • The need for an overall frameworkThe foregoing fits within the ISO 38500 model.There is a need/pressureProjects along with operations fit within process, the whole requiring Principle 1: ResponsibilityIndividuals and groups within the organization understand and accept theirresponsibilities in respect of both supply of, and demand for IT. Those withresponsibility for actions also have the authority to perform those actions.Principle 2: StrategyThe organization’s business strategy takes into account the current and futurecapabilities of IT; the strategic plans for IT satisfy the current and ongoingneeds of the organization’s business strategy.Principle 3: AcquisitionIT acquisitions are made for valid reasons, on the basis of appropriate andongoing analysis, with clear and transparent decision making. There isappropriate balance between benefits, opportunities, costs, and risks, in boththe short term and the long term.Principle 4: PerformanceIT is fit for purpose in supporting the organization, providing the services, levelsof service and service quality required to meet current and future businessrequirements.Principle 5: ConformanceIT complies with all mandatory legislation and regulations. Policies andpractices are clearly defined, implemented and enforced.Principle 6: Human BehaviourIT policies, practices and decisions demonstrate respect for Human Behaviour,including the current and evolving needs of all the ‘people in the process’.Evaluate Direct MonitorNo framework perfect, but my experience suggests that it is likely to assist project/programme success and thus business success
  • The 6 principles are clear and when we look briefly at them we begin to see how when applied they will impact the probability of success , especially in the Planning & Initiation phases.
  • Underlying theme of values, people capability and experise in each of the principlesNot based on legal presciprion or one area, but all embracing
  • Demonstrates how the framework can be used to provide guidance and how it fits.Perhaps not perfect mapping Can map principles mapped against key factors noted earlierAbsence of such structure will increase likelihood of failure Sauer re leadership increases risk and probablity of failureSauer re lack of alignment
  • Research supports observations I have made over many years.
  • Finally let us turn to the Initiation and planning stagesThese common issues reflect situation arising when Governance is not present for one reason or anotherWhen we look at the Initiation and Planning Stages what do we seeScope leads to changesPM changesSo how will apply a governance framework assistEvidence Sauer + ????Val IT
  • Finally let us turn to the Initiation and planning stagesThese common issues reflect situation arising when Governance is not present for one reason or anotherWhen we look at the Initiation and Planning Stages what do we seeScope leads to changesPM changesSo how will apply a governance framework assistEvidence Sauer + ????Val IT
  • Project Success/Failure

    1. 1. PROJECTSKey Issues in Success/FailureISACA Wellington Chapter Sept 11, 2009<br />Peter Salmon, C.A.<br />Principal - Manning Charles & Associates Ltd.<br />
    2. 2. Important Notice – please make sure you read <br />This notice applies to all materials and information available in this presentation.<br />All information and materials are provided on an &apos;as is&apos; basis and are not intended in any way to be comprehensive. <br />Any reader making use of this material does so at his/her own risk and readers are advised to take independent professional advice before acting on any information or materials found here. <br />Neither Peter Salmon nor Manning Charles & Associates Limited accepts any responsibility for, nor do they give any representations or warranties, express or implied, that any of the information and materials contained in this document and presentation are complete, accurate or free from errors or omissions.<br />2<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    3. 3. About this session<br />We will consider:<br />project success rates<br />key issues associated with the success or failure of projects. <br />the impact of governance as a means of enhancing prospects of success. <br />in this regard the Initiation and Planning stages of the Project Lifecycle<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />3<br />
    4. 4. Nature of Projects<br />A project is a temporary endeavor undertaken to create a unique product, service, or result <br />Source:- PMBOK<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />4<br />
    5. 5. Project outcomes vary<br />Success<br />Failure<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />5<br />Source :- Getty Images / Stu Forster<br />Source:- Ian Mackley<br />DominionPost<br />
    6. 6. Success is rare?<br />6<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    7. 7. Or is it?<br />7<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />
    8. 8. Some key defining factors<br />Successful<br />Strong, visible executive support<br />Dedicated teams<br />Alignment with vision<br />Change impacts clear and known<br />Accountability/Responsibility<br />Change seen as an on-going process<br />Metrics and incentives used to drive desired behaviours<br />Undersell, over-deliver<br />Everyone gets a win is the approach<br />Unsuccessful<br />Uncertain leadership<br />Resource scarcity/competition<br />Unclear goals, vision or strategy<br />Opaque change impact<br />No Accountability/Responsibility<br />Change is episodic and event based<br />Metrics and incentives non-aligned with desired behaviours<br />Lots of “happy talk&quot;<br />Clear winners and losers <br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />8<br />
    9. 9. ISO 38500 Governance Model<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />9<br />Source:ISO38500 Standard<br />
    10. 10. Principles<br />Responsibility<br />Strategy<br />Acquisition<br />Performance<br />Conformance<br />Human Behavior<br />10<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />
    11. 11. Principles - defined<br />Principle 1: Responsibility<br />Individuals and groups within the organization understand and accept their responsibilities in respect of both supply of, and demand for IT. Those with responsibility for actions also have the authority to perform those actions.<br />Principle 2: Strategy<br />The organization’s business strategy takes into account the current and future capabilities of IT; the strategic plans for IT satisfy the current and ongoing needs of the organization’s business strategy.<br />Principle 3: Acquisition<br />IT acquisitions are made for valid reasons, on the basis of appropriate and ongoing analysis, with clear and transparent decision making. There is appropriate balance between benefits, opportunities, costs, and risks, in both the short term and the long term.<br />11<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    12. 12. Principles defined<br />Principle 4: Performance<br />IT is fit for purpose in supporting the organization, providing the services, levels of service and service quality required to meet current and future business requirements.<br />Principle 5: Conformance<br />IT complies with all mandatory legislation and regulations. Policies and practices are clearly defined, implemented and enforced.<br />Principle 6: Human Behaviour<br />IT policies, practices and decisions demonstrate respect for Human Behaviour, including the current and evolving needs of all the ‘people in the process’.<br />12<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    13. 13. Six Principles mapped to key project factors<br />13<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    14. 14. Impact of governance<br />14<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />Source:Sauer, Gemino and Reich<br />
    15. 15. Impact of governance<br />15<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />Source:Sauer, Gemino and Reich<br />
    16. 16. Project Initiation + Planning - Common Issues<br />16<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />
    17. 17. Project Initiation + Planning - Common Issues<br />17<br />Projects – Key Issues in Success/Failure © September 2009 <br />Peter M Salmon & Manning Charles & Associates Ltd<br />
    18. 18. OK, but what do we do?<br />Implement a framework which<br />Evaluates needs on an ongoing basis<br />Ensures IT meets business objectives<br />Monitors outcomes and adherence to policy, law etc<br />Intent being to:-<br />Reduce risk<br />Ensure the informed use and deployment of IT<br />Provide the information to enable objective evaluation of IT within the entity<br />18<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    19. 19. Key elements<br />Leadership<br />Entity<br />Sponsor<br />Project<br />Common values, e.g.<br />Integrity<br />Openness<br />Communication<br />Resourcing<br />People<br />Training<br />Time<br />19<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />
    20. 20. Desired outcome<br />20<br />Projects – Key Issues in Success/Failure © September 2009 Peter M Salmon & Manning Charles & Associates Ltd<br />Source: Ian Mackley/<br />Dominion Post<br />

    ×