addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [ia-55] UX in Agile Sprints

From: Alan D.
Sent on: Monday, March 11, 2013 4:11 PM
This is an interesting discussion. I like how the original question asked for experiences instead of the "one right way." I'd like to add a small point of philosophy that could help.

The further we remove our decisions from the point and time of delivery the lower the likelihood of delighting our customer. Decisions far distant from the moment of delivery are likely to suffer from:
- Invalid assumptions
- Disconnected or no relationship with the user/customer
- "Telephone game" effects
- Environments where the process become more important than the product
- Emphasis on output instead of outcomes

So, MUST the UX contribution of the work be done during the Sprint or iteration? No, but we need to keep in mind the risk that we may end up with merely satisfied users rather than delighted users. My general advise is to move UX and all other kinds of work as close to user delivery time as possible, making the feedback loop both closer and more timely. That way we have a higher chance of really making something that the users need, not what they asked for.

Alan



On Mon, Mar 11, 2013 at 12:46 PM, Sam Blake <[address removed]> wrote:
I haven't done UX in a formal agile environment, but Smashing Magazine did a piece on this which might be helpful to you: http://uxdesign.smashingmagazine.com/2012/11/06/design-spikes-fit-big-picture-ux-agile-development/


On Mon, Mar 11, 2013 at 1:15 PM, Thomas Donehower <[address removed]> wrote:
Hi All, 

Curious about your experience with UX in agile sprints. 

What is the role of UX in agile sprints? 

When does it take place? 

What deliverables are you producing and which team members are using them? 

I have this vision of the sprint team sitting around a table and talking about the user experience. Then whiteboarding, sketching, maybe low-fidelity wireframes and then development. 

This, however has not been my reality. My reality has been UX is running in a more traditional waterfall and then dev uses the pre-existing UX deliverables in their weekly sprints as they work through the backlog. Which just doesn't feel right to me.

Any shared experiences with UX in an agile environment are appreciated. 

--
-Tom





--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Thomas Donehower ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Thomas Donehower, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages

Meetup, POB 4668 #37895 NY NY USA 10163 | [address removed]





--
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Sam Blake ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Sam Blake, visit his/her member profile



--
Alan Dayley - Agile Coach
BigVisible Solutions - http://bigvisible.com
Skype: alandond

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy