Troy, Do you also indicate on the prototype which fields are required to indicate the front end validation as well as DB configuration?
Dan Prototyping I, like Jeff, have been working on a project since 1999. I was brought on to help with it, but due to poor project management, which looked good at the time, and failure to get a client to "agree" with the product in a "prototype" fashion, it still continues today in 2002. During that time I've been left holding the ball all myself on this project. For the past six months I've been reading and trying to apply the concepts of FLiP with this project. I currently have developed a prototype of what they client wants and am using the DevNotes that was modified by Lee to generate feedback on it. I was able to generate a prototype in about two months, working part-time with the knowledge I've accumulated over the past 3 years, and am nearing the "signoff" phase. What has taken me almost 3 years to do I have now done is approx. two months time which is just unreal to me. I firmly believe that this process is the best process that I've seen in developing ColdFusion applications. Having generated the COMPLETE site in HTML, CSS and JavaScript to show the client and then having them sign off on a screen-by-screen basis is the ONLY way to protect yourself, in my opinion. This forces the clients to give you the feedback you need and "controls" the "scope creep monster". Just my thoughts. -T -----Original Message----- From: Jeff Peters [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 08, 2002 2:10 PM To: [EMAIL PROTECTED] Subject: RE: FLiP and Prototyping War story time: My team is currently working on an application for a federal client. It's a fairly complex application, replacing a Windows-based client- server app. Due to other responsibilities, the signing authority (the person who would sign off on the prototype) was not available to us for most of last year, when we were doing the design stages of the app. As a result, we proceeded with a prototype that had not been signed by the client. I've been working with this client for 5 years now, so I know the arena quite well, but there are still many areas where we're having to rework the program concept. Same client, same environment, different (but related) system: With the client's other demands out of the way, I insisted on page-by-page signoff of the prototype (using a rubber stamp to put an approval block on each printed page). We just delivered the first of three phases, and are now ready to get signoff on the second phase. Because of the insistence on a tight, signed prototype, this second project proceeds much more smoothly than the first, even though all the players are the same, the environment is the same, the culture is the same, etc. - Jeff On 7 Jun 2002 at 23:50, hal helms wrote: > I highly recommend that the entire front end of an application be > created as part of the prototype process. I have seen many, many > failures occur when prototyping is either skipped entirely or (more > commonly) not treated seriously enough. > > -----Original Message----- > From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 07, 2002 11:27 PM > To: Fusebox List > Subject: FLiP and Prototyping > > > In FLiP when you refer to prototyping do you prototype the whole site > i.e. do html pages for practically the whole site or just 2 to 3 > templates? > > Is there any tools other then devnotes used for prototyping in this > community? > > Thanks. > > John Jonathan Kopanas > [EMAIL PROTECTED] > > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
