[Sigia-l] How the design process fits into the agile methodology, WAS Pricing the Design Process

[Adrian Howard]

On 14 Feb 2007, at 19:17, Ziya Oz wrote:

> Adrian Howard:
>
>> 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.
>
> Are you suggesting a new motto for XP: "We're no worse than any other
> process!" :-)

Nope. That's why I went on to say (in the very next sentence no less!):

"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.".

In fact, I'd remove that "slightly" ;-)

> I don't have a strongly held position on XP but I have some  
> observations:
>
> 1.  Virtually all XP projects are developer driven.

That's certainly not been my experience. Neither in the transition to  
an agile process, or in the way that they run.

> 2.  Virtually all waterfall projects of yesteryear were developer  
> driven.

That's also not been my experience. Possibly we have different  
definitions of developer?

> 3.  XP wasn't created specifically to solve design problems.

It certainly doesn't just address design (in the big "D" design  
sense) problems. However, as far as I am concerned, one of the major  
drivers for XP was to build better products and make happier  
customers. If that's not a design problem I don't know what is.

> 4.  Developers are not designers.

Some are. Some are not. Some just lack experience of the practices  
and techniques.

> Make of it what you will.

Ditto :-)

Cheers,

Adrian