New development methodology

I would like your (jungian collective unconsciousness) opinion on this methodology:
I call it slow RAD (sexy its not)
This systems recognizes the following constraints: users make mistakes in what they want
developers make mistakes
things change (people, requirements, systems, os, tools,...) writing code is bad (more code = greater chance of error) user interface application
not much business logic in app
RAD prototyping tool
extremely high level of expertise in tools technical environment allows rapid deployment of design

Week one (gather requirements)
meet with focus group everyday for two hours, determine hard functionality based on business conceptual functionality (apologies to TurkBear).

Week two (bottom up)
meet with focus group everyday for two hours, build and refine prototype. everyday the focus group sees the prototype and makes suggestions. changes are made that day.
focus group signs off on prototype.

Week three (top down)
ERD and FHD creation ( no DSD,BPM,DFD,...)

Week four (staged delivery)
create the smallest portion of functionality which will be useful to the user

Week five and six (use)
Hype and sell system
two weeks of user production use
get suggestions then cycle again (probably take three iterations) Received on Thu Dec 23 1999 - 05:45:21 CST