Hi Linda,
One of the bigger issues that I see and read about is the 'How much
up-front design?' issue. UCD likes a lot of up-front design and
Scrum/Agile only wants the minimum done. I think it's a semantic
problem around the term 'design'.
I think when Scrum/Agile talk about up-front design they mean
designing an actual solution, ie. sketches, viso, UI code, etc. But
when UCD talks about up-front design, they really mean 'problem
definition'. The first stage in UCD is to really work out what
problem you're trying to solve and who you're solving it for. Once
you have that, then you can start on a solution. I think Agile call
this analysis rather than design (but I might be wrong on that as I'm
still learning about Agile).
So it's something i see people clash over, but I think it's just a
semantic problem.
Cheers,
Dan.
2009/3/4 linda.hellman <
linda.hellman@...>:
> Hi,
> I'm writing my Master's Thesis at the moment and in my Thesis I'm trying to
> find the biggest problems between the two methods and then to integrate
> Scrum and UCD and create new user-centered Scrum.
> My Thesis is based on literature about integrating user-centered design and
> agile methods. My Thesis is almost ready and at the moment I am starting to
> introduce my process to one software project where I am the UE designer.
>
> I would like hear from You, what kind of actual troubles and problems You
> have had when using both Scrum and User-Centered Design?
> And what advantages has the use of both methods brought to the project?
>
> Waiting for your opinions,
> Linda.
>
>