[Sigia-l] Agile, Scrum and UX?

[Matthew Hodgson]

At the anniversary of the signing of the agile manifesto, they discussed
whether there was anything they would change. Overall, they agreed that it
was still relevant, but the phrase "working software" is still something
that some consider a barrier to its further adoption into disciplines other
than software development.

That said, much of "agile" is very old. Even Scrum was born out of product
development and the article in the Harvard Business Review 'The New New
Product Development Game".

Now there are dozens of agile methods. Some continue to evolve over time.
The important thing is to remember that agile isn't one thing. It's more
important to ensure that the right method is selected for the right team,
its environment and its needs.

This is one reason I changed from a primary focus in my professional life
from UX to Agile. There's a lot that the agile camp can learn from UX. I
think the community is better from that mix of perspectives.

M



On 22 March 2015 at 11:29, Thomas Donehower <tdonehower at gmail.com> wrote:

> Very helpful. I think the debate and exploration is worth it and encourage
> anyone to contribute to this discussion. I think the most interesting
> comment I've seen is the idea that when the agile manifesto was written
> they did not have UX in mind and over time it seems that looser definitions
> of agile and agile methods have been adopted to account for this. I also
> think this points to the idea that every sprint yielding production ready
> code may not actually yield the best product/software and that there is
> room for improving or evolving the original thinking. Agree?
> -Tom
>
>
>
> > On Mar 21, 2015, at 3:36 PM, Jonathan Baker-Bates <
> jonathan at bakerbates.com> wrote:
> >
> > As a one-time Agile Alliance Certified Scrum Master, I would say that
> > as long as both the pigs and the chickens all agree with the
> > definition of "done", then that's fine. However, the default in scrum
> > is always to produce production ready *code* (not wireframes or
> > personas) at the end of every sprint, and from the very first sprint.
> > See antipattern 16 (from the standard texts on the subject):
> >
> >
> http://www.agileadvice.com/2011/12/05/referenceinformation/24-common-scrum-pitfalls-summarized/
> >
> > ... and of course the endless debates that produces!
> >
> > https://www.scrum.org/Forums/aft/1273
> >
> > But we digress here.
> >
> > @Tom: are we helping at all, or should we just can it?
> >
> > Jonathan
> >
> >
> >
> >
> >> On 21 March 2015 at 22:21, magia3e at gmail.com <magia3e at gmail.com> wrote:
> >> Scrum's Sprints don't have to focus on software. It can be used to
> deliver anything that the Product Owner dedices is of value. A whole
> Sprint's Increment may just be dedicated to learning with 'knowledge
> products'.
> >>
> >> The idea behind 'production ready' is that what ever is created is
> fully complete within the confines of the Sprint to what ever standard the
> quality/satisfaction criteria (Definition of Done) specifies.
> >>
> >> Things that are not software have been delivered using Scrum
> >>
> >> * The SAAB Gripen fighter jet was made with Scrum.
> >>
> >> * The wikispeed car
> >>
> >> I've delivered UX consulting recommendations papers using Scrum whose
> tram was only ux people. Each Increment consisted of 'production ready'
> personas, tree structures and prototypes because that was the outcome
> sought by the Product Owner by the client. These would be used much later
> to help guide a web project.
> >>
> >> M
> >>
> >>
> >> Sent from my HTC
> >>
> >> ----- Reply message -----
> >> From: "Skot Nelson" <skot at penguinstorm.com>
> >> To: "SIG Information Architecture" <sigia-l at asis.org>
> >> Subject: [Sigia-l] Agile, Scrum and UX?
> >> Date: Sun, Mar 22, 2015 6:54 AM
> >>
> >> 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
> >
> > ------------
> > 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
>