I have worked with a large international company in the past, and I was impressed by their software development approach. The development cycle is as follows:

The project tasks are divided in various stages. The project plan for each phase is further divided into 3 categories:
  • Must have
  • Should have
  • Nice to have

    The Must-have's are requirements that must be met for this project phase. The Should-have's are requirements that should be completed for the project phase, but ok if not completed. It will slip to the Must-have's in the next phase. And the Nice-to-have's are features that are not essential for the project phase, and would progress to Should-have's in the next phase if the project slips.

    If the project is going according to plan with time to spare, then items in the Must-have, Should-have and Nice-to-have categories will be promoted, ie., Must-have's add to the should-have's in the previous phase, and should-have's add to the must-have's, and so on...

    This approach is what I believe a simplified XP (Extreme Programming) in practice. And it seems to be quite successful too.

    In reply to Re: Process Model for Projects by Roger
    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.