This has been a point of contention in our agile environment. UX work has been scheduled often within the same sprint, which is impractical, imo. UX work should be done in a previous sprint, or outside of the sprint, entirely. When a story reaches a sprint for developers, it should be ready to code. Otherwise, you are creating blockers that may take most of the sprint to resolve.
Subject: [ia-55] UX in Agile Sprints
From: [address removed]
To: [address removed]
Date: Mon, 11 Mar[masked]:14:56 -0400
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.
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]