What methodology I prefer and what methodology I am forced to abide by are very similar to yours.

Our management structure is uncomfortable with the "iterative" development methodologies because the business partners are remote from the developers, and they like giving thier requirements in the form of a quasi-design. For instance, instead of asking for data for a certain purpose, like a report, we will get a SAS query and they will ask us to reproduce the same results from our Oracle Data Warehouse. In addition, developers rarely have direct access to the business partners and have to communicate through a "Single Point of Contact" or SPOC. Many times, the SPOC for the business partners will communicate the need for a new project to the SPOC for the developers; a Project Request Document will be produced, then the SPOC for the developers will solicit the requirements from the Business SPOC, and a deadline will be set; all before the actual technical people get involved with the project. Then when the technical people have questions about the requirements, the developer's SPOC is the one to answer their questions, to insulate the Business from "interruptions" and "repeating themselves".

So what happens is a very Waterfall approach where we turn out what we think the Business Partners want, and it rarely meets their real requirements.

Oh, and we don't ever do it fast enough. ;-)

In reply to Re: What's your methodology? by poqui
in thread What's your methodology? by Mutant

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.