In a previous article, Ophilia <OP@fake.mail> said:

We do it where I work, but we have a separate "Corporate Design and
Usability" department.

Sort of.  A lot of this stuff gets collapsed into a more informal
process in reality.  I bet a lot of people, including myself, at least
sketch "storyboards" in cooperation with concept designers and
representatives from the intended user base, before they begin writing
any code.  They just may not recognize the word "storyboard" as
describing what they do.  It's also not applied universally, but only in
a few places where the task is a bit tricky.

Hi,

I currently *have* to write stories in my project.
The background is coming from the UML mess, where every process and
use-case has to be defined and designed in front of anything else.

There is no magic and nothing special. You will define your processes
and the whole screen-design in front.
In the terms of the good old times it's just as writing specifications,
but now in more modern bold letters.

After more than 10 years of project experience I learned that the
buzz-words will change every week but the work behind the scenes is
still the exciting art of the good old stuff.

After having written all the storyboards , usecases and so on and
developing all the software, the client asked for several major changes.
So all the work with the stories was waste of time.

Upon my experiences it is the best to develop quick prototypes and ask
the client to let you know if he is happy with that. In most cases he
won't accept your first proposal.

regards
Maz Rashid - www.mazcity.de