|
Hi Andy,
This happens all the time. You get a highly detailed requirements document from the client. They say "It's all there in the 273 pages. Now, what's your ball-park estimate?" In any case where the client provides a detailed requirement, or a non-detailed requirement, a wireframe is a perfect, simple, formal method whereby you can document your understanding of the requirement, ie where you get to communicate with the client and ensure you are both heading in the same direction. In any case, as Steve so often says, the wireframe should take no more than a couple of hours. Given that you are going to spend many hours staring at the supplied requirements document, you can surely spend another couple turning all of that verbage into something formal and compact. To paraphrase a much-quoted truism: If you can't wireframe it, you can't build it. So take the extra couple of hours. It gives you a firm basis for mutual understanding, a consistent foundation for the ongoing development, and it's perfect for making a sensible estimation of timeframes and costs. Best of luck, ----- Original Message -----
==^================================================================ 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 ==^================================================================ |
- Have Funct. Spec. - Need Wireframes or Devnotes ? Andy
- Lee Borkman
