Case Upon
#1 in Business Subscribe Email Print

You are here: Home > Business > Management > It's NOT the Methodology, Stupid: Even the Best Methodology Can't Save an IT Project

Tags

  • overall
  • nuances
  • highly
  • strongly advocating
  • should provide
  • nearly identical

  • Links

  • Investing In Small Capitalization Companies
  • Just A Little Testa Mint
  • Ten Ways to Market Your Business by Doing What You Love To Do
  • Case Upon - It's NOT the Methodology, Stupid: Even the Best Methodology Can't Save an IT Project

    Business Valuation That Makes Sense
    Business-valuation is nothing simple. Every person out there will think that a business is worth more or less than what the next person will say. In fact, the only number that really does matter is the simple fact that it is worth what someone will pay for it and that number only occurs once the deal is done. But, there are ways of understanding what business-valuation could be. For that end, we will talk here.• Capitalized Earning. This is one approach to understanding the value of a business. Wh
    lp if you have no car, driver’s license or gas.

    So what is one to do when comparing methodologies? All of them will sound reasonable, since they all are derived from the time-tested SDLC, however there are some nuances to be aware of:

    • A huge advertised benefit of a large implementation company and its particular methodology is the “toolkit” component, with pre-delivered documentation to complement the steps outlined in the methodology. Ensure that this actually exists, and more importantly gets used on yo
      Business Process Management
      Business process management is the process of designing and maintaining an environment in which individuals, working together in groups, efficiently accomplish selected aims. This basic definition needs to be expanded as manager’s carry out the managerial functions of planning, organizing, staffing, leading and controlling. Management applies to any kind of organization. It applies to managers at all organizational levels. The aim of all managers is to create a surplus. Managing is concerned with productivity
      Methodologies are often presented as the stuff of legends. Sit in any presentation by one of the large implementation companies, and by the fiftieth PowerPoint slide you’ll likely be convinced that the methodology being presented will create a flawless implementation, nearly run itself and eventually bring about world peace in our time. Each company presents its methodology as unique and special. When questioned about the competition, although using slightly more flowery language images of six year olds fighting on the playground still come to mind: My methodology can beat up your methodology!

      Is there any method to all this methodology madness? On some level, a methodology plays an important part in any project. Similar to a road map, the methodology maps out what tasks should be completed during certain stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate for different tasks. Just as you would not take a highly detailed topographic map for a drive across the country, any company advocating a “one methodology fits all” approach should immediately be regarded with an element of suspicion.

      The dirty little secret in the implementation business is that all of these methodologies are nearly identical. Most are based on a standard Systems Development Lifecycle (SDLC) model, providing for well defined and demarcated phases from Planning and Analysis to Testing and Implementation. Again returning to our map analogy, endlessly debating methodologies, or strongly advocating one “brand” over the other is akin of arguing the merits of AAA versus Michelin road maps. While a methodology can provide a solid overall framework for a project, if you are not comfortable with the staff that will be provided for your project, or do not feel the implementation company has adequate skills, the best methodology can not make up for shortcomings in these more important areas. Again, if you’re embarking on a road trip, the best maps in the world will not help if you have no car, driver’s license or gas.

      So what is one to do when comparing methodologies? All of them will sound reasonable, since they all are derived from the time-tested SDLC, however there are some nuances to be aware of:

      • A huge advertised benefit of a large implementation company and its particular methodology is the “toolkit” component, with pre-delivered documentation to complement the steps outlined in the methodology. Ensure that this actually exists, and more importantly gets used on you
        A Serious Warning to Business Owners
        Over the past 19 years, I have worked with thousands of business owners in Africa, Canada and the United States. I foresee serious financial adversity looming for many entrepreneurs in the coming years, and perhaps a lot sooner than we may think. And before you conclude that this is mere speculation, let me share some reasons for my concern, and then allow me to offer you a solution.On a macro level, we all know that the dollar’s purchasing power has declined. The “world’s reserve currency” is in troubl
        d still come to mind: My methodology can beat up your methodology!

        Is there any method to all this methodology madness? On some level, a methodology plays an important part in any project. Similar to a road map, the methodology maps out what tasks should be completed during certain stages of the project’s lifecycle, and should provide a “toolkit” of ready-made templates and skeleton plans to save reinventing the wheel. Like maps however, different methods are more appropriate for different tasks. Just as you would not take a highly detailed topographic map for a drive across the country, any company advocating a “one methodology fits all” approach should immediately be regarded with an element of suspicion.

        The dirty little secret in the implementation business is that all of these methodologies are nearly identical. Most are based on a standard Systems Development Lifecycle (SDLC) model, providing for well defined and demarcated phases from Planning and Analysis to Testing and Implementation. Again returning to our map analogy, endlessly debating methodologies, or strongly advocating one “brand” over the other is akin of arguing the merits of AAA versus Michelin road maps. While a methodology can provide a solid overall framework for a project, if you are not comfortable with the staff that will be provided for your project, or do not feel the implementation company has adequate skills, the best methodology can not make up for shortcomings in these more important areas. Again, if you’re embarking on a road trip, the best maps in the world will not help if you have no car, driver’s license or gas.

        So what is one to do when comparing methodologies? All of them will sound reasonable, since they all are derived from the time-tested SDLC, however there are some nuances to be aware of:

        • A huge advertised benefit of a large implementation company and its particular methodology is the “toolkit” component, with pre-delivered documentation to complement the steps outlined in the methodology. Ensure that this actually exists, and more importantly gets used on yo
          Extended Stay Lodging-Satisfying the Long-Term Guest
          While extended stay guests have long been part of the hotel industry, the purpose-built segment has exploded in North America and particularly in the US within the last ten years. This has been a hotel developer's nirvana. Who wouldn't have been attracted to the segment?Depending on whose figures you rely on, extended stay guests make up about six to ten percent of the overall traveling public and a greater percentage of the industry's sold room nights. Yet even today, extended stay rooms make up about
          take a highly detailed topographic map for a drive across the country, any company advocating a “one methodology fits all” approach should immediately be regarded with an element of suspicion.

          The dirty little secret in the implementation business is that all of these methodologies are nearly identical. Most are based on a standard Systems Development Lifecycle (SDLC) model, providing for well defined and demarcated phases from Planning and Analysis to Testing and Implementation. Again returning to our map analogy, endlessly debating methodologies, or strongly advocating one “brand” over the other is akin of arguing the merits of AAA versus Michelin road maps. While a methodology can provide a solid overall framework for a project, if you are not comfortable with the staff that will be provided for your project, or do not feel the implementation company has adequate skills, the best methodology can not make up for shortcomings in these more important areas. Again, if you’re embarking on a road trip, the best maps in the world will not help if you have no car, driver’s license or gas.

          So what is one to do when comparing methodologies? All of them will sound reasonable, since they all are derived from the time-tested SDLC, however there are some nuances to be aware of:

          • A huge advertised benefit of a large implementation company and its particular methodology is the “toolkit” component, with pre-delivered documentation to complement the steps outlined in the methodology. Ensure that this actually exists, and more importantly gets used on yo
            Polarity Management
            Have you ever noticed that just when you think you may have found a solution to a problem another problem emerges? Then when you fix that problem, you find yourself back to your original issue? Well perhaps you never had a problem that could be solved in the first place. You may have been dealing with a dilemma or a "polarity" that simply needed to be managed!Dr. Barry Johnson has been working on the Polarity Management" Model and its set of principles since 1975 and this paper has been written to intr
            lessly debating methodologies, or strongly advocating one “brand” over the other is akin of arguing the merits of AAA versus Michelin road maps. While a methodology can provide a solid overall framework for a project, if you are not comfortable with the staff that will be provided for your project, or do not feel the implementation company has adequate skills, the best methodology can not make up for shortcomings in these more important areas. Again, if you’re embarking on a road trip, the best maps in the world will not help if you have no car, driver’s license or gas.

            So what is one to do when comparing methodologies? All of them will sound reasonable, since they all are derived from the time-tested SDLC, however there are some nuances to be aware of:

            • A huge advertised benefit of a large implementation company and its particular methodology is the “toolkit” component, with pre-delivered documentation to complement the steps outlined in the methodology. Ensure that this actually exists, and more importantly gets used on yo
              How To Get Started In Your Business
              Let's face it, starting your own business is no small task. People think owning their own business will make them rich and in control. On the contrary, owning your own business will be the hardest thing you've ever done. A business owner must be able to wear all the hats of the business, including taking out the trash and answering the phone. Being self-employed takes dedication and the desire to succeed. If you think you can get investors to give you tons of money and think you'll just hire people to
              lp if you have no car, driver’s license or gas.

              So what is one to do when comparing methodologies? All of them will sound reasonable, since they all are derived from the time-tested SDLC, however there are some nuances to be aware of:

              • A huge advertised benefit of a large implementation company and its particular methodology is the “toolkit” component, with pre-delivered documentation to complement the steps outlined in the methodology. Ensure that this actually exists, and more importantly gets used on your project. When firms are billing at an hourly rate, there is a large incentive to “reinvent the wheel” on every project for the sake of increased billings or resource requirements, even when the company has likely completed similar templates on many previous engagements.
              • Understand that the methodology alone probably contributes to about 3% of the success of a project. The quality of decision making, talent of the implementer, project and program management and a litany of other factors make far more difference. Do a little research and you will likely find no implementations that were successful based on methodology alone.
              • The other side of the coin is that if you find a vendor with particularly talented staff, extensive experience in your implementation area, and an excellent management team, do not let a weak methodology sales job weigh heavily on your decision. A sad fact of implementation life is that many of the components of a methodology will fall by the wayside when the going gets tough, and only excellent management and leadership will save the day.

              If a potential implementation partner spends hours trumpeting their “proprietary” methodology, while brushing aside questions around staffing or project experience, run quickly in the opposite direction. A methodology alone never makes for a successful implementation.

              Copyright 2006 Patrick Gray

    HTTP = HTML link (for blogs, profiles,phorums):
    <a href="http://www.answerupon.com/article/22932/answerupon-Its-NOT-the-Methodology-Stupid-Even-the-Best-Methodology-Cant-Save-an-IT-Project.html">It's NOT the Methodology, Stupid: Even the Best Methodology Can't Save an IT Project</a>

    BB link (for phorums):
    [url=http://www.answerupon.com/article/22932/answerupon-Its-NOT-the-Methodology-Stupid-Even-the-Best-Methodology-Cant-Save-an-IT-Project.html]It's NOT the Methodology, Stupid: Even the Best Methodology Can't Save an IT Project[/url]

    Related Articles:

    Boomers and Generation Y - The Computer Connection

    Overcoming Greater Odds Than Ever: The 2006 Best Bosses

    Market Research Is a Backwards-Facing Tool: It Won't Deliver Marketers the Next Big Idea

    Bookmark it: del.icio.us digg.com reddit.com netvouz.com google.com yahoo.com technorati.com furl.net bloglines.com socialdust.com ma.gnolia.com newsvine.com slashdot.org simpy.com shadows.com blinklist.com