On Wed, 21 Jul 2004 14:31:00 +1000, Scott Barnes <[EMAIL PROTECTED]> wrote: > I think its the holy grail and either you buy one off the shelf and > force yourself to adopt its methodology in the way you handle your > software development or you write on yourself.
Totally agree - we've tried all sorts of off-the-shelf solutions, but we don't want to change what we do to suit someone else's idea of a good process. I started down the slippery path of writing our own about four years ago. The cycle goes like this: 1. I take suggestions + write requirements. Much discussion and revision ensues. 2. I write specifications. I design a database (or modify the previous incarnation). 3. I mockop some html, once or twice even a little functionality was included. 4. We get insanely busy and the project gets shelved. By the time I have some spare time, the requirements have changed so much that we start fresh. I'm in the requirements stage at the moment. So far, we've started (and abandoned) ProjectTracker, Minitracker, UberTracker and TrackerTracker. Actually Minitracker is actually being used, despite living up to it's name as far as functionality is concerned. I'm going to call this new one SpackerTracker. I think the trick is extreme RAD, get it out there before step 4 catches me. Wish me luck :) -- Kay Smoljak http://kay.smoljak.com --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
