[Sigia-l] Agile, Scrum and UX?

[Matthew Hodgson]

I'd say that *delivery* is the measure of success. But you are right about
working software vs value in terms of its delivery to end-users. This is
where I see UX brings a much needed refocussing of how a team works to
deliver that value.

This is why I feel its important to think about Scrum's Increment in terms
of Lean principles. That is, to create value (not just working software).

On 22 March 2015 at 09:05, Jonathan Baker-Bates <jonathan at bakerbates.com>
wrote:

> @Skot - I wouldn't go as far to say it was antithetical. The Agile
> Principles say the delivery of working software should be "frequent"
> and that it should be the "primary measure of progress". But I know
> what you mean. Agile should be free to do what's appropriate, really.
>
> @Thomas: As you can probably tell, there are some difficulties with
> scrum orthodoxy when it comes to UX :-) I think this is because agile
> methods (not just scrum but most others as well) attempt to solve
> problems that UX designers don't really have - or at last don't have
> to nearly the same extent as developers have. UX isn't reducible in
> the way software is, and certainly the "founding fathers" of scrum
> weren't thinking about UX when they formulated their manifesto - the
> term "customer" is the 1980's meaning: somebody who pays for the
> software to be built. Here's the famous "principles" page:
> http://agilemanifesto.org/principles.html (the background photo
> texture - QED).
>
> I think there's a world of difference between writing code that runs
> on computers, and creating things that run in people's heads. Because
> of this, I think it's unfair on both designers and developers to adopt
> the same methods. Were I to join a development team who had adopted
> scrum, I would not discourage them, but equally I would not work
> exclusively on their terms. It wouldn't be worth us all paying the the
> price for that later if I did.
>
> Jonathan
>
>
>
> On 21 March 2015 at 19:54, Skot Nelson <skot at penguinstorm.com> wrote:
> > Yes.
> >
> > There notion that "every sprint results in production ready code" seems
> antithetical to agile itself.
> > --
> > Skot Nelson
> > http://www.penguinstorm.com/
> > twitter. penguinstorm
> >
> >> On Mar 21, 2015, at 12:35, Thomas Donehower <tdonehower at gmail.com>
> wrote:
> >>
> >> print yields production ready software?  Are you saying there could be
> sprints that are devoted to just prototyping for example
> >
> > ------------
> > 2015  IA Summit
> > April 22-26, 2015
> > Minneapolis, MN
> > -----
> > When replying, please *trim your post* as much as possible.
> > *Plain text, please; NO Attachments
> >
> > Searchable Archive at http://www.info-arch.org/lists/sigia-l/
> > ________________________________________
> > Sigia-l mailing list -- post to: Sigia-l at asis.org
> > Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
> >
> ------------
> 2015  IA Summit
> April 22-26, 2015
> Minneapolis, MN
> -----
> When replying, please *trim your post* as much as possible.
> *Plain text, please; NO Attachments
>
> Searchable Archive at http://www.info-arch.org/lists/sigia-l/
> ________________________________________
> Sigia-l mailing list -- post to: Sigia-l at asis.org
> Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
>