In order to convince someone to upgrade, you need to convince them that there is a compelling reason to do so. Creating this argument is not a small task, and you may not be in a position in the company where it would be acceptable for you to even try to win this argument. That is, managers may feel that they should do the managing, and you should do the coding. If this is the case, you have several ways to be successful anyway:
  1. Convince one manager to advocate your approach, and have that manager do the business case and work on the office politics. This is the easy way.
  2. Become a manager. Ouch!
  3. Get a temporary assignment to look into this issue, create a project description, schedule, and work breakdown structure. Be sure that you use the same project management tools that the managers use. It will probably involve a suite of programs that all work together.

One way to get managers to change the way they look at things is to come up with a theme. For example, to ship the existing site, managers probably had a theme like "Get to market". You need to show that you understand that this was the idea, and how it should be changed to something like "Secure the site". Maybe your next theme would be "Improve customization" or "Reduce cost of new features". Only propose one theme, though, and keep the theme short and simple, such as one or two words.

These themes give the abilility to convince your audience of something that is not an implementation detail. At the level of the company above your department, the manager probably shouldn't care what version of perl you are using. This manager should care about functionality, usability, reliability, performace, and supportability. (If you memorize the previous sentence it will come in handy.) You will win when you convince a decision-maker that you can influence one or more of these important attributes. The decision-maker will understand the plan in terms of a simple theme, and will be convinced that you understand the implementation details needed to carry out the plan. Someone will have the specific assignment to make the plan happen, and will be held accountable if it fails.

This probably sounds like a lot of work, and it may be that so far no one has had the drive to carry it out.

It should work perfectly the first time! - toma

In reply to Re: de-inventing the wheel (discussion) by toma
in thread de-inventing the wheel (discussion) by deprecated

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.