List Info

Thread: How the design process fits into the agile methodology, WAS Pricing the Design Process




How the design process fits into the agile methodology, WAS Pricing the Design Process
user name
2007-02-13 07:58:23
Jamie said:
With agile it's the opposite. It's very light on
deliverables, the
focus switching to building a usable product at the end of
each
iteration. It's very user-centred in its approach as you can
build
user testing cycles into each iteration to feed into
requirements for
the next.

Probably a subject for a separate thread (if there hasn't
already been
one) is how the design process fits into the agile
methodology - which
has some big challenges. I'd be interested to hear other
people's
experiences with this.
END

Hi Jamie, You still need a 'big picture' and the more
clearly this is defined, the better the direction.  Adopting
an agile, iterative approach means that you can always
develop or change it if you want. Another advantage is that
by creating a clear specification of a possible solution at
the start, one can anticpate issues before they arrive e.g.
to prevent painting yourself into a corner.  I acknowledge
that an iterative approach doesn't mean that you don't map
out, even roughly, future iterations, I suppose I'm really
suggesting that it needs to be combined with a good
plan/specification.

As for user testing, before you start on a project, your
business case should give you a pretty clear definition of
what is required from the project.  Even if one route is
different to another, the ultimate solution should still
satisfy the need - which should be testable.  I agree that
from a standard usability perspective its important to test
the solution effectiveness of any features or distinct
processes in your design, but you are never going to be able
to evaluate the whole user experience without all the bits
tied up, which takes us back to the starting question 'what
are you trying to achieve?' and then 'how will you know when
you've got there?'.  These questions need to be asked at the
beginning if not least to help the project stay focussed and
on track.  If you come up with some wonderful solution or
opportunity mid-project, you can then always adapt your
project accordingly.

Ivor Tillier

------------
IA Summit 2007:  Enriching IA
Rich Information, Rich Interaction, Rich Relationships
March 22-26, 2007, Las Vegas, NV
www.iasummit.org
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.in
fo-arch.org/lists/sigia-l/




________________________________________
Sigia-l mailing list -- post to: Sigia-lasis.org
Changes to subscription: http://
mail.asis.org/mailman/listinfo/sigia-l

Re: How the design process fits into the agile methodology, WAS Pricing the Design Process
country flaguser name
United Kingdom
2007-02-14 05:15:10
> Jamie said:
> With agile it's the opposite. It's very light on
deliverables, the
> focus switching to building a usable product at the end
of each
> iteration. It's very user-centred in its approach as
you can build
> user testing cycles into each iteration to feed into
requirements for
> the next.
>
> Probably a subject for a separate thread (if there
hasn't already been
> one) is how the design process fits into the agile
methodology - which
> has some big challenges. I'd be interested to hear
other people's
> experiences with this.
> END
[snip]

There's a nice discussion on this very topic on the IxDA
list at the  
moment.

<ht
tp://listserver.dreamhost.com/pipermail/discuss- 
interactiondesigners.com/2007-February/014654.html>

If you're interested in the topic I'd recommend you join the
agile- 
usability list <http://tech.groups.yahoo.com/group/agile-usability/>

Cheers,

Adrian
------------
IA Summit 2007:  Enriching IA
Rich Information, Rich Interaction, Rich Relationships
March 22-26, 2007, Las Vegas, NV
www.iasummit.org
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.in
fo-arch.org/lists/sigia-l/




________________________________________
Sigia-l mailing list -- post to: Sigia-lasis.org
Changes to subscription: http://
mail.asis.org/mailman/listinfo/sigia-l

Re: How the design process fits into the agile methodology, WAS Pricing the Design Process
user name
2007-02-14 06:04:38
Austin Govella posted a couple weeks ago on agile and
design.
h
ttp://thinkingandmaking.com/lightpress/entries/232

Austin - "Agile development won't give you better
design. Design
models things to be made. Development makes things you've
modeled.
Agile development methods promise better model-making, but
don't
promise better models. Agile development can actually
devastate
design."

~ James


-- 
James Melzer
http://www.jamesmelzer.com

http://del.icio.us/jam
esmelzer

On 2/14/07, Adrian Howard <adrianhquietstars.com> wrote:
>
> > Jamie said:
> > With agile it's the opposite. It's very light on
deliverables, the
> > focus switching to building a usable product at
the end of each
> > iteration. It's very user-centred in its approach
as you can build
> > user testing cycles into each iteration to feed
into requirements for
> > the next.
> >
> > Probably a subject for a separate thread (if there
hasn't already been
> > one) is how the design process fits into the agile
methodology - which
> > has some big challenges. I'd be interested to hear
other people's
> > experiences with this.
> > END
> [snip]
>
> There's a nice discussion on this very topic on the
IxDA list at the
> moment.
>
> <ht
tp://listserver.dreamhost.com/pipermail/discuss-
> interactiondesigners.com/2007-February/014654.html>
>
> If you're interested in the topic I'd recommend you
join the agile-
> usability list <http://tech.groups.yahoo.com/group/agile-usability/>
>
> Cheers,
>
> Adrian
> ------------
> IA Summit 2007:  Enriching IA
> Rich Information, Rich Interaction, Rich Relationships
> March 22-26, 2007, Las Vegas, NV
> www.iasummit.org
> -----
> When replying, please *trim your post* as much as
possible.
> *Plain text, please; NO Attachments
>
> Searchable Archive at http://www.in
fo-arch.org/lists/sigia-l/
>
>
>
>
> ________________________________________
> Sigia-l mailing list -- post to: Sigia-lasis.org
> Changes to subscription: http://
mail.asis.org/mailman/listinfo/sigia-l
>
------------
IA Summit 2007:  Enriching IA
Rich Information, Rich Interaction, Rich Relationships
March 22-26, 2007, Las Vegas, NV
www.iasummit.org
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.in
fo-arch.org/lists/sigia-l/




________________________________________
Sigia-l mailing list -- post to: Sigia-lasis.org
Changes to subscription: http://
mail.asis.org/mailman/listinfo/sigia-l

Re: How the design process fits into the agile methodology, WAS Pricing the Design Process
country flaguser name
United Kingdom
2007-02-14 06:12:24
On 14 Feb 2007, at 12:04, James Melzer wrote:

> Austin Govella posted a couple weeks ago on agile and
design.
> h
ttp://thinkingandmaking.com/lightpress/entries/232
>
> Austin - "Agile development won't give you better
design. Design
> models things to be made. Development makes things
you've modeled.
> Agile development methods promise better model-making,
but don't
> promise better models. Agile development can actually
devastate
> design."

Any my response was (no comment since I couldn't get past
the spam  
filters  was:

---
There seems to be some confusion agile methods are purely a 

developmental process. That really doesn't gel with my
experiences.  
For example I've found the Planning Game in XP is a very
rich  
environment for doing exploratory design work.

For me agile is just as much about design as it is about  
implementation. Go read the agile manifesto again . Replace 

"software" by "product" and see how it
reads.

It's true that if you don't have people with design skills
involved  
in the team then you're less likely to get a decent product
out the  
other end - but this is true of any process.

Agile development doesn't devastate design any more than any
other  
process. In fact, I'd say that you're slightly more likely
to get  
things right even without input from Design (in the UX/IxD
sense)  
folk, because you're getting feedback far more frequently
and can  
spot problem areas.

When the developers aren't separated from the stakeholders
and users  
by N layers of management Chinese whispers it becomes a lot
easier  
for them to do a good job.

As for agile only working 2-4 people - there are a /whole/
bunch of  
people who seem to be doing pretty darn well with
considerably more  
than that  It's
certainly easier to get a small team up and  
running in an agile manner. That doesn't mean that you can't
get  
larger projects working that way.

---

Cheers,

Adrian
------------
IA Summit 2007:  Enriching IA
Rich Information, Rich Interaction, Rich Relationships
March 22-26, 2007, Las Vegas, NV
www.iasummit.org
-----
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable Archive at http://www.in
fo-arch.org/lists/sigia-l/




________________________________________
Sigia-l mailing list -- post to: Sigia-lasis.org
Changes to subscription: http://
mail.asis.org/mailman/listinfo/sigia-l

[1-4]

about | contact  Other archives ( Real Estate discussion Medical topics )