The software development cycle

New project:

 

Phase 1:

 

• Customer screams
• Someone in the company produces a      "time and effort estimate" with almost no "analysis" or development input.
• Customer screams some more.
• 20/30 pages of "design/storyboard/look and feel/etc paper" is created (again with no development input)
• Schedule/Deadline is set.

 

Phase 2:

• Development is asked for "time and effort estimate"
• Customer screams some more.
• There is no time for fixing the vast infrastructure problems, so "bad, patched code" is produced on top of already "bad, patched code" (also, known as the "ptest effect")
• Project shipped
• Customer is happy.
• 2 months later that exact shipped code does not work anymore.
• No one notices.

 

Yet Another New project:

Phase 1:

• Customer screams.
• ...