Unfortunately, I think that most programmers wouldn't know what to do with a scenario. In an elevated organization where everyone "gets it", then the programmers would have been involved in the design from the beginning and would have a deep understanding of what/why they are building.
So, in most organizations, a functional spec is expected and you'll deliver what's expected. Can you give scenarios to the testers? Can you give both to the programmers and see which works better for them? ...Dan On Apr 23, 2008, at 3:53 AM, AJ Kock wrote: > So my questions are: Do you provide scenarios in your functional > spec or > does this get done afterwards? Should you be providing a list of > functions > or will a list of scenarios provide better results? ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
