I like something called "spiral methodology". It seems to fit actual process flow more than any other "methodology" I've worked with yet.

1: receive request from user community (report/ new system/ whatever)
2: mock up (potentially throw away/ better if reusable but can't count on it)
3: user comments/ changes
4: keep what worked, change what didn't

Repeat this process as quickly as possible, with releases of stable code at least monthly, and major releases at least quarterly.

Its helpful to have a spreadsheet or summat to keep track of user requests. Then a triage session weekly to include/push requirements into the next release is needed to keep the list and user expectations manageable.

In reply to Re: Process Model for Projects by poqui
in thread Process Model for Projects by gmpassos

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.