align-toparrow-leftarrow-rightbackbellblockcalendarcamerachatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditfacebookglobegoogleimagesinstagramlocation-pinmagnifying-glassmailmoremuplabelShape 3 + Rectangle 1outlookpersonplusImported LayersImported LayersImported Layersshieldstartwitteryahoo

Re: [ia-55] UX in Agile Sprints

From: Carlos (Charlie) S.
Sent on: Monday, March 11, 2013 11:50 AM
Hey Tom, Steven,
Here's the video from last week's event on Lean UX:
http://youtu.be/fotTozueXJ8

Charlie


Charlie Salazar
[address removed]


On Mon, Mar 11, 2013 at 11:37 AM, Stephen Ruiz <[address removed]> wrote:
Thomas,

Here have been my personal experiences, in red.

-----
Stephen Ruiz
Digital Media Expert
StephenRuiz.com
@stephenruiz


What is the role of UX in agile sprints? 

I would say it is to create rapid, usually sketch-based, prototypes with the designers. Also, to state the obvious, it is to interject UX thinking into the process as the rapid iterations are happening.
When does it take place? 

I would say it should take place anytime you're at the table with the team, or working with team members to create any iteration. 
What deliverables are you producing and which team members are using them? 
for me it's been sketches, mixed with standard artifacts (workflows, wireframes, site maps, etc.)


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. 
Ideally that's exactly how it should be.


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.
Unfortunately, that seems to be the case more often than not. I think the reality is that most teams simply do not know how to properly implement a true Agile Process, so what you end-up getting is an ad hoc and bastardized version of Agile. When I've encountered this situation, I've had to be flexible enough to deliver something that will truly make a difference.


 Which just doesn't feel right to me.

I agree completely. Sometimes it's a matter of educating your team. If they're open to it, I would attempt to have a frank discussion about what "deliverables" mean for the UX component of the project. That way, at worst, you can manage your own expectations of what you're doing. At best, you may be able to help your team understand UX in the context of Agile.

I would suggest you check these out. The LAUX group just had an amazing event on Lean UX, which was an incredibly valuable event to me personally.

Here's some info on Lean UX & Lean Design:


Also, isn't the video from the event up somewhere? Anyone?


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 Stephen Ruiz ([address removed]) from The Los Angeles User Experience Meetup.
To learn more about Stephen Ruiz, visit his/her member profile

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