I think it is the word "RISK" that could be alarming. That is if it is something you want your client to consider. Perhaps softer wording would be more appropriate, because when thinking about the three levels, it would help put the client in a frame of mind to realize the potential cost of development.
It would really help mindsets that think in terms of the cost of developing two or three static pages, but wants a user friendly, and easy to maintain, dynamically driven application with access to comprehensive reporting, and huge catalogs (databases) Doug, you did good! :-) Doug White ----- Original Message ----- From: "Douglas Smith" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, March 26, 2002 12:23 PM Subject: Re: Levels of Modeling Risks and FLiP Yes, I am thinking mostly in terms of giving ourselves (the developer/architect) a better heads-up as to what we are getting ourselves into, so the prototyping goes smoother, and how to better estimate the time/costs, so the client is prepared to pay. At 12:14 PM 3/26/02 -0500, you wrote: >I don't like talking about risk much with the client. It's good to >acknowledge risk, but not dwell on it. ==^================================================================ 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 ==^================================================================
