Optimizing to The Point of Failure and Managing Project Risk

The other day, I was on a flight to an airport whose approach is known to be unpredictable.

The other day, I was on a flight to an airport whose approach is known to be unpredictable. After we circled for a while (at least the scenery was nice), we had a smooth landing and taxied toward the gate. A few yards away from the gate, the engines flamed out, a sure sign that the fuel had run out. “Hmmm…,” I thought, but the plane rolled on its momentum and I felt the pilot slightly tap the brakes to stop precisely at the gate.

As I stood up to collect my luggage, the pilot excitedly announced over the intercom, “I just got this new app for my iPhone. It considers weather patterns, traffic patterns and dozens of other factors that I updated just before the flight. Then it calculates the exact amount of fuel needed for a trip. As you probably noticed, the app worked perfectly. We had just the right amount of fuel for the trip. Do you have any idea how much money we can save by not flying around with excess fuel? Is this not great?”

My “Hmmm…” suddenly morphed into a “Yikes!”  With that kind of optimization, I wondered, just exactly how many more airport circlings had been left in the tank?

As potentially scary as that scenario sounds, that’s often how we manage our IT projects. We often don’t want to know about risks or consider unpleasant surprises or contingencies. In times of tight budgets and short timelines, anything that increases the estimated budget can make the difference between go or no-go for a project. We pressure the people proposing a project for the bare-minimum numbers, which increases not only stress but also the likelihood of failure. Failed projects seldom provide a footnote referencing unreasonable demands placed on people or technology, and subsequent projects often suffer from legacy expectations that roll forward.

Even worse, this is how we approach our vendors: “We’re hiring you because you claim you know what you’re doing. So don’t talk to me about risk.” Actually, selecting the right vendor can make a huge difference in mitigating risk. It’s not as much about certainty as about awareness that the more the vendor knows, the more they know about what can go wrong—and we all know that Murphy was an optimist.

Proper risk management requires a project manager who has been there and done that. A good project manager provides a realistic perspective when determining what’s required to bring a project in for a safe landing, including examining hidden issues that might be uncomfortable to discuss. Only by carefully collecting and considering as many factors as possible that can affect success can the project manager recommend a strategy to mitigate risk. And so far, there’s no app for that.

Written by

Thomas Koehler

Thomas’s mission is to help the CA Technologies team of talented project and program managers…

Published in

View this topic
  • James Holland

    This is great. Hooray for Disney’s imagineers!

    become a new brand in the share market research with its accurate research. Proven
    itself always right whether market is bull or bear. Last week all paid clients
    booked handsome profit in NIFTY, BANKINIFTY & STOCKS. Now for the coming
    week we expect more correction can come in NIFTY as the IRAQ issue is getting
    more tense, If it happens more then you will see a sharp fall in all world marketNSE BSE, STOCK TIPSbecause as we know all world run on
    crude & most of the crude comes from IRAQ. So be ready for a sharp fall so
    sell will be the best strategy for next week also. Traders can make a sell
    position in NIFTY around 7600-7650 with stoploss 7750 for the target of
    7300-7200.One can also make a sell call NIFTY 50 stocks as per NIFTY levels. You
    can also take our two days free trial to check our accuracy. For further updates
    you can visit our website. http://goo.gl/sMgZ7n



  • king lear

    testing comment functionality, please do not publish this

  • Love the personal pic 🙂

    • CAHighlight

      Thank you!

  • Plutora Inc

    This is a good case study. 2.3 sec’s off a login transaction is big.

  • While the analysts were hyping DevOps, I posted the oversight of not including security as part of that discussion as you are highlighting here. Instead of just talking DevOps, it should be DOS (what’s old is new again 🙂 – DevOpsSec. As a previous AppDev person, it’s the app, who’s using it, why and where rather than the device and having the service available.

    As you rightly point, out Security should be baked into the solution.

    Nice Post and Timely!


    • CAHighlight

      Thank you for your feedback Michele. Agreed – security cannot be overlooked. Appreciate your input!

  • Mitesh

    I would love a printed copy

  • Lars Johansson

    I love the idea of BYOID! This makes me choose if I am almost anonymous (with my Hotmail Nicname) or official with identity from an official organisation. My Identity Provider will attach identity with right level of LoA according to the need of the Service provider.

    • CAHighlight

      Thank you for your comment. BYOID has tangible benefits for end users and relying parties but it also has to be weighed in the balance with potential risks and liability concerns. It will be interesting to see how BYOID plays out in the enterprise.