An interesting issue that keeps coming up is "incremental" vs
"iterative". As Alistair Cockburn concisely puts it, Incremental
adding stuff, while Iterative means to redo stuff.
When you say that the design is broken down and implemented in small
chunks, would you say that you are thinking more along the lines of
Incrementing or Iterating?
> -----Original Message-----
> From: agile-usability@
yahoogroups. com [mailto:agile-
ps.com] On Behalf Of mitchgrrt
> Sent: March 28, 2008 6:35 AM
> To: agile-usability@
> Subject: [agile-usability] Re: Story Cards?
> Interaction design needs to produce a design before engineers can
> code. This seems a little bit to be against the philosophy of agile,
> which is to do the work in little chunks rather than producing a big,
> complete design in advance.
> How do we resolve this problem? It's not that hard, and it goes in
> two steps. First, we make stories. For sprint 1, there is a story
> like "produce interaction design for feature X, and review it with
> whole team". The story is assigned to an interaction designer and the
> deliverables for the story are an agreed-upon design that is written
> in some form that everybody on the project can understand. Then for
> sprint 2, the story is "implement feature X using the design that was
> produced in sprint 1". This works as long as the interaction
> designers are always 1 sprint ahead of the engineers in the design
> Second, we break it up into chunks. It's the agile idea of small,
> deliverable, potentially shippable increments. So instead of one huge
> design for all the features of the product, the design is broken into
> smaller pieces. To do this the design team has to have a vision in
> mind, and understand that the little pieces are converging on a bigger
> vision. But the designs that are delivered to engineering are in
> small pieces that can be implemented one sprint at a time.
> - Mitch Gart
> ------------ --------- --------- ------
> Yahoo! Groups Links