12 Best Practices for UX in an Agile Environment - Part 2
Part 1 of this article was published earlier ...
"7) Schedule continuous user research in a separate track from development
For many commercial Agile projects, I'm starting to see user research as something that's considered a separate and continuously running track. User research functions as an independent effort that keeps its activities and schedule transparent. User experience designers, working with the development team, can help steer future research (and even participate in it), in support of what they're currently working on in development. User research that's conducted is shared and communicated in lightweight ways with the rest of the team. I've seen some UX practitioners using comics to communicate the output of user research rather than dry reports. I commonly see presentations schedule to "share-out" -- communicate stories about users and research findings with the rest of the team.
8) Leverage user time for multiple activities
In talking with Lynn Miller and Desiree Sy about parallel track development (see figure) they describe visiting customers and using that time to do some contextual-inquiry-style observation and interviewing, to then sit down and review a prototype for something that may be built in a future iteration, then to review the working software testing features just built in a previous iteration. The trick here is to leverage that user face-time for research and validation. Don't segregate your work." (Continued via UIE, Jeff Patton) [Usability Resources]
"7) Schedule continuous user research in a separate track from development
For many commercial Agile projects, I'm starting to see user research as something that's considered a separate and continuously running track. User research functions as an independent effort that keeps its activities and schedule transparent. User experience designers, working with the development team, can help steer future research (and even participate in it), in support of what they're currently working on in development. User research that's conducted is shared and communicated in lightweight ways with the rest of the team. I've seen some UX practitioners using comics to communicate the output of user research rather than dry reports. I commonly see presentations schedule to "share-out" -- communicate stories about users and research findings with the rest of the team.
8) Leverage user time for multiple activities
In talking with Lynn Miller and Desiree Sy about parallel track development (see figure) they describe visiting customers and using that time to do some contextual-inquiry-style observation and interviewing, to then sit down and review a prototype for something that may be built in a future iteration, then to review the working software testing features just built in a previous iteration. The trick here is to leverage that user face-time for research and validation. Don't segregate your work." (Continued via UIE, Jeff Patton) [Usability Resources]
Parallel Track Development
0 Comments:
Post a Comment
<< Home